Repository intelligenceRepositories
⌘K
Home / Repositories / github/spec-kit
CLI · established

github/spec-kit

Spec-driven development toolkit/Specify CLI with constitution → specification → plan → tasks → implementation plus clarify/analyze/checklist extensions.

software planningspec-driven development
GitHubMatrix
Installation GuideInstruction Manual

What it contains

Spec-driven development toolkit/Specify CLI with constitution → specification → plan → tasks → implementation plus clarify/analyze/checklist extensions.

Typical uses

Formalize what to build before implementation and keep durable requirements/planning artifacts across many coding agents.

Why people choose it

Inference: useful when explicit specs should govern AI coding instead of chat-only context.

License
Unknown
Maintenance
active
Latest release
Unknown
Last meaningful update
Unknown
Maturity
established
Production readiness
production

Classification

Subject domains

software planningspec-driven development

Task categories

software planningspec-driven development

Project phases

planningimplementationtestingreview

Secondary types

frameworkskill collection

Select when

  • Need formal spec-first requirements/plan/tasks

Do not select when

  • Trivial edit
  • Another methodology already owns planning
Implementation complexity
medium
Setup effort
medium
Learning curve
medium
Confidence
high

Routing heuristic 84.0%

Routing specificity
4/5
Setup simplicity
3/5
Operational maturity
5/5
Composability
4/5
Local control
5/5
Security boundary clarity
3/5
First-party routing documentation
5/5

Strengths

None documented.

Poor-fit scenarios

  • Trivial edit
  • Another methodology already owns planning

Limitations

None documented.

Specify CLI command
README.md

Initialize/manage integrations/templates.

initextensions
README.md

Define project principles.

governance
specify skill
README.md

Define what/why.

requirements
plan skill
README.md

Create technical plan.

planning
tasks skill
README.md

Generate actionable tasks.

task breakdown
implement skill
README.md

Execute approved tasks.

implementation
Languages
Python, Markdown
Frameworks
None documented
Runtimes
Python, uv
Operating systems
None documented
Installation methods
uv/PyPI
Interfaces
CLI, skills
Required credentials
None documented
External services
None documented
Hardware
None documented
Major dependencies
None documented

Compatibility notes

None documented.

One-sentence semantic summary

Spec-driven development toolkit/Specify CLI with constitution → specification → plan → tasks → implementation plus clarify/analyze/checklist extensions.

Capability keywords

constitutionspecclarifyplantasksanalyzeimplementextensions

User intent phrases

  • Need formal spec-first requirements/plan/tasks

Negative match phrases

  • Trivial edit
  • Another methodology already owns planning

Differentiators

None documented.

Security considerations

None documented.

Privacy considerations

None documented.

Uncertainty

Unresolved items

  • License not conclusively verified in the inspected first-party material.

Inference notes

None documented.

Evidence

Repository usage guidance

installation summary
uv/PyPI
basic usage summary
Formalize what to build before implementation and keep durable requirements/planning artifacts across many coding agents.
documented entry points
specify, /speckit.*
key configuration files
None documented
important directories
docs/
documentation paths
README.md
example paths
None documented

Relationships

alternative
high
Spec Kit is formal artifact/spec-driven; BMAD is adaptive multi-role delivery.
overlapping
medium
Both can own lifecycle phases; Superpowers adds mandatory TDD/worktree flow.

Recommended combinations

Spec-first large-repo delivery high

Each repository covers a distinct layer; avoid combining tools that duplicate lifecycle ownership.

Order of operations

  • Create constitution/spec/plan/tasks
  • Use semantic search during planning/implementation
  • Use RTK for terminal verification
  • Implement against approved tasks

Routing rules

rule_018: Need formal spec-first requirements/plan/tasks P982

Rationale

Spec-driven development toolkit/Specify CLI with constitution → specification → plan → tasks → implementation plus clarify/analyze/checklist extensions.

Required conditions

None documented.

Preferred

github/spec-kit

Fallback

None