spec-kit

Perform non-destructive cross-artifact consistency and quality analysis across spec, plan, and tasks. Use when the user wants to analyze specifications, says "analyze spec", "check consistency", "quality check", "review artifacts", or wants to verify alignment between specification documents.

Check if the spec-kit plugin templates and methodology have been updated in the upstream github/spec-kit repository. Use when the user wants to sync with upstream, says "check for updates", "sync spec-kit", "update templates", or wants to ensure they are using the latest spec-kit methodology.

Create or manage quality checklists for feature development phases (UX, security, performance, testing). Use when the user wants to create a checklist, says "generate checklist", "quality gates", "create review checklist", or wants to define validation criteria for a feature.

Identify underspecified areas in a feature specification and interactively resolve them with up to 5 targeted questions. Use when the user wants to clarify requirements, says "clarify spec", "resolve ambiguities", "clarify requirements", or when a specification has [NEEDS CLARIFICATION] markers that need resolution.

Create or update the project constitution with core principles, governance rules, and version tracking. Use when the user wants to define project principles, says "create constitution", "update principles", "set project values", or needs to establish the foundational governance for their SDD project.

Execute implementation tasks phase-by-phase from the task list, following TDD and respecting dependencies. Use when the user wants to implement, says "start implementation", "execute tasks", "implement feature", "build it", or is ready to write code based on the task list.

Initialize a Spec-Driven Development project by creating the .speckit/ scaffold directory with templates and a specs/ directory. Use when the user wants to start using SDD methodology, says "init speckit", "initialize spec-kit", "setup SDD", or wants to create a new SDD project structure.

Generate a detailed technical implementation plan from a feature specification. Use when the user wants to plan implementation, says "create plan", "build plan", "technical plan", "implementation plan", or is ready to move from specification to technical design.

Create a feature specification from a natural language description. Use when the user wants to specify a feature, says "write spec", "create specification", "specify feature", "describe requirements", or provides a feature description to be structured into a formal specification.

Convert implementation tasks into GitHub Issues for project tracking. Use when the user wants to create GitHub issues from tasks, says "create issues", "track tasks in GitHub", "push tasks to issues", or wants to link spec tasks to a GitHub project.

Break down an implementation plan into an ordered, dependency-aware task list organized by user story. Use when the user wants to generate tasks, says "create tasks", "break down plan", "task list", "generate tasks", or is ready to move from planning to execution.