What problem does it solve?
Converts informal, natural-language feature descriptions into a structured, testable product specification so teams avoid ambiguous requirements and reduce planning delays.
Core Features & Use Cases
- Template-driven spec creation: Generates a spec.md inside a new feature directory using .specify/templates/spec-template.md and records the path in .specify/feature.json.
- Pre/post extension hook support: Detects and reports optional or mandatory hooks from .specify/extensions.yml and surfaces commands or automatic executions without evaluating hook conditions.
- Quality validation and checklists: Produces a requirements checklist, validates the spec against quality criteria, iterates fixes up to three times, and lists remaining clarifications via up to three [NEEDS CLARIFICATION] questions.
- Real-world example: Product managers can turn a short product idea into a ready spec folder (specs/003-new-checkout) with acceptance criteria and a validation checklist for planning.
Quick Start
Run the speckit-specify workflow with a clear feature description to create a spec.md and a quality checklist in the specs/ directory.