spec-kit-skill

Spec-driven development structures feature work through seven phases: Constitution, Specify, Clarify, Plan, Tasks, Analyze, and Implement. Use Spec-Kit CLI to automate this workflow, storing specs in `.specify/specs/NNN-feature-name/` directories. This ensures all development aligns with your project's established principles and requirements.

A constitution is a `constitution.md` document that establishes your project's governing principles and core values. It informs all design and implementation decisions throughout the seven-phase workflow, reducing scope creep and rework by ensuring every feature adheres to documented principles.

Initialize your project with Spec-Kit, define your `constitution.md`, then use the CLI to create a new feature specification. The tool scaffolds the seven-phase workflow, detects your current phase, tracks progress, and stores all specs under `.specify/specs/` with automatic phase detection.

Yes. Spec-driven development works with any GitHub-based project. Define or update your `constitution.md`, then use Spec-Kit CLI to initialize the workflow for new features. Existing projects adopt the structured phases incrementally as new features are added.

Spec-driven development prioritizes rigor and structured planning over speed. The seven-phase workflow is designed for projects where clear requirements, principle alignment, and reduced rework justify the upfront specification effort. It suits established projects more than experimental prototypes.

Spec-Kit CLI depends on `specify-cli` and `uv` (a Python package manager). These tools orchestrate the workflow phases, provide scaffolding, and manage spec storage. Ensure both dependencies are installed before initializing your project.