spec-kit-skill

Constitution-driven specification uses a seven-phase workflow—Constitution, Specify, Clarify, Plan, Tasks, Analyze, Implement—to guide feature development systematically. Each phase builds on the previous one, with artifacts stored in `.specify/specs/NNN-feature-name/` directories, ensuring specifications are complete before implementation begins.

Yes. The spec-kit CLI orchestrates constitution-driven development by automating phase detection, managing artifact storage, and guiding you through each step. It integrates with `.specify/` directories to maintain structured specifications aligned with your project's constitution.

A seven-phase workflow closes specification gaps that lead to unclear requirements, rework, and implementation misalignment. By separating constitution definition, clarification, planning, and task breakdown before implementation, it reduces ambiguity and ensures teams build the right feature correctly.

Initialize a new spec-kit project using the CLI, which sets up the `.specify/` directory structure and prepares your repository for constitution-driven development. The Constitution phase begins immediately, establishing the foundational principles guiding all subsequent specification and implementation work.

Yes. Spec-kit integrates with GitHub projects by using `.specify/` directories and the spec-kit CLI. You can adopt the constitution-driven workflow in existing repositories by initializing spec-kit and following the seven phases for new or refactored features.

Constitution-driven workflows add upfront structure and documentation phases before coding begins. For teams prioritizing speed over specification rigor, the initial overhead may slow time-to-first-code, though it typically reduces rework and clarification cycles downstream.