spec-kit

Spec-driven development defines and organizes technical requirements using a phase-driven framework centered on governance and outcomes. It progresses through Constitution, Specify, Plan, Tasks, Analyze, and Implement phases to ensure architectural alignment.

To create executable technical specifications, invoke an interactive spec session and supply a feature name. The framework generates canonical artifacts like constitution.md, spec.md, plan.md, tasks.md, and analysis.md to guide implementation.

Spec-driven development supports AI-assisted iterative dialogue and enforces governance by aligning specifications with architecture and guardrails throughout each phase, ensuring technical requirements remain executable.

A phase-based specification framework generates canonical markdown artifacts including constitution.md, spec.md, plan.md, tasks.md, and analysis.md, which collectively define architecture, requirements, and implementation tasks.

To start defining technical specifications, you need a SKILL.md frontmatter containing a name and description. The framework also supports optional resources like scripts, references, and assets to assist the workflow.

You should avoid a phase-driven specification framework for rapid prototyping or unstructured exploration where strict architectural governance and canonical artifact generation would introduce unnecessary process overhead.