ai-ad-spec-kit

Spec-driven workflow orchestrates development through five phases—Constitution, Specify, Plan, Tasks, Implement—ensuring specifications, plans, and task lists align with governance documents before code generation. Start by providing a mission description to initiate the SPECIFY phase, then proceed through planning and implementation with built-in verification checkpoints.

SoT (Source of Truth) alignment enforces constraints from governance documents like STATE_MACHINE.md, API_SOT.md, and BUSINESS_RULES.md across all development phases. This ensures consistent feature delivery and prevents fragmented, unverified workflows by governing specification generation, planning, and task creation from a single authoritative source.

Phase-based workflows establish governance checkpoints at Constitution, Specify, Plan, Tasks, and Implement stages, producing structured artifacts—specification documents, implementation plans, and task lists—that enforce standards. This scales consistency across multi-phase, team-driven projects by integrating verification steps before code generation.

Provide governance documents and project constraints; the workflow extracts requirements, generates verifiable specification documents and task lists, then produces structured implementation plans. Each artifact is validated against governance before progression, integrating with code-generation and verification skills.

Spec-driven development formalizes requirements into verified specifications and plans before implementation, preventing rework and misalignment. Traditional code-first skips this layer; spec-driven governance ensures all code changes trace back to documented constraints and pass verification before tasks are assigned.