SkillsAdd

smithery/neversight

github-spec-kit

Expert guidance for Spec-Driven Development using the GitHub Spec Kit.

Installation

$ npx skills add smithery/neversight --skill github-spec-kit
View on skills.sh ↗ Website ↗

Summary

  • Expert guidance for Spec-Driven Development using the GitHub Spec Kit.
  • Use when the user wants to initialize a project, create specifications, plan implementations, or execute tasks based on the Spec Kit workflow.
  • Triggers on "spec kit", "specify", "create spec", "spec-driven development".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from smithery/neversight · top by installs.

npx skills add smithery/neversight
zoom-meeting 0 ziwei-doushu 0 zimage-skill 0 zig 0 zhimeng-agent 0 zfc 0 zenbin 0 zeberg-salomon-rotator 0 zdev 0 youtube-transcript 0

Browse all from smithery/neversight

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,988 B
  • docs SUMMARY.md 313 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Github Spec Kit

Overview

This skill guides the Spec-Driven Development (SDD) process using the GitHub Spec Kit. It helps you shift from code-first to specification-first development, ensuring high-quality software by focusing on product scenarios and predictable outcomes.

Workflow

The Github Spec Kit workflow consists of the following key stages. Follow them sequentially for new features or projects.

  1. Initialize: Set up the project structure.
  2. Constitution: Define project principles.
  3. Specify: Create a functional specification.
  4. Plan: Design the technical implementation.
  5. Tasks: Break down the plan into actionable tasks.
  6. Implement: Execute the tasks.

For detailed instructions on each step, see [WORKFLOW.md](references/workflow.md).

Usage Guide

1. Initialization

  • Goal: Bootstrap a new project.
  • Action: Use uvx --from specify-cli specify init . --here --ai [MODEL].
  • Git Check: Before execution, check if the directory is already a git repository (e.g., git rev-parse --is-inside-work-tree). Use the --no-git flag only if a git repository is already initialized to avoid conflicts.
  • Check: Ensure specify-cli is accessible; uvx is preferred for consistency.

2. Principles (Constitution)

  • Goal: Establish governing principles.
  • Trigger: Respond to /speckit.constitution.
  • Action: Create or update .specify/memory/constitution.md.
  • Focus: Define core values like code quality, testing standards, and performance.

3. Specification

  • Goal: Describe "what" and "why".
  • Trigger: Respond to /speckit.specify.
  • Action: Create specs/<feature>/spec.md using the template in .specify/templates/spec-template.md.
  • Focus: User scenarios, outcomes, functional requirements. Avoid implementation details.

4. Planning

  • Goal: Define "how".
  • Trigger: Respond to /speckit.plan.
  • Action: Create specs/<feature>/plan.md (and optional data-model.md, research.md).
  • Focus: Architecture, tech stack, data structures, algorithms.

5. Tasks

  • Goal: Create a checklist.
  • Trigger: Respond to /speckit.tasks.
  • Action: Create specs/<feature>/tasks.md based on the plan and specification.
  • Focus: Small, verifiable steps grouped by user story.

6. Implementation

  • Goal: Write code.
  • Trigger: Respond to /speckit.implement.
  • Action: Execute tasks from tasks.md sequentially.
  • Behavior: Read the current task, implement, verify, and mark as completed.

Resources

  • Workflow Details: [WORKFLOW.md](references/workflow.md)