spec-kit

Cross-artifact consistency analysis across spec.md, plan.md, and tasks.md after task generation

Generate a custom checklist for the current feature based on user requirements.

Ask targeted questions to resolve spec ambiguities

Create/update project constitution from principle inputs, syncing dependent templates

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create or update the feature specification from a natural language feature description.

Bootstrap spec-driven development workflow at the start of a session

Generate dependency-ordered tasks.md from design artifacts

Execute implementation tasks systematically following the task plan with TDD approach and progress tracking. Use when executing implementation tasks from tasks.md, continuing implementation, implementing specific phases, systematic code generation. Do not use when generating tasks - use task-generator agent first. analyzing specs - use spec-analyzer agent. Trigger proactively during /speckit-implement commands.

Analyze specification artifacts for consistency, coverage, and quality issues. Use when checking spec quality, validating spec/plan/tasks alignment, debugging missing requirements, detecting ambiguity or underspecification. Do not use when writing specifications - use spec-writing skill. generating tasks - use task-generator agent. Trigger proactively during /speckit-analyze commands.

Generate dependency-ordered implementation tasks from specification and planning artifacts. Use when generating tasks from spec and plan, breaking down implementation work, creating ordered task lists, starting implementation phase. Do not use when analyzing specifications - use spec-analyzer agent. executing tasks - use implementation-executor agent. Trigger proactively during /speckit-tasks commands.

Create clear, testable specifications with user stories and acceptance criteria. spec writing, feature specification, requirements, user stories Use when: creating new specifications or writing acceptance criteria DO NOT use when: converting specs to tasks - use task-planning.

Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.

Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specs - use spec-writing. Not for execution - use speckit-implement.