lockstep

Spec-Driven Development

Spec-driven development is building with AI coding agents from a written spec: define what to build and why, then turn it into a plan, tasks, and code.

Spec-driven development (SDD) is a way of building software with AI coding agents where a written spec comes before any code. GitHub's Spec Kit puts it in one line: define what to build and why, then turn the specification into a plan, tasks, and working code.

The usual shape

StepSpec KitKiro
What and whyspec.mdrequirements.md
Howplan.mddesign.md
Work breakdowntasks.mdtasks.md

The first row is product work, and a product manager is often the right owner. The rest is engineering and the agent. A guide for that split is in spec-driven development for product managers, with a template in the PRD template for AI coding agents.

The catch

Birgitta Böckeler's analysis on martinfowler.com separates spec-first, where the spec guides one build and is discarded, from spec-anchored, where it evolves with the code. Most teams end up spec-first by default. The spec goes stale, and the next agent builds from rules that changed weeks ago: spec drift. More in spec-driven development problems. For the tools side by side, see Spec Kit vs Kiro vs OpenSpec vs BMAD.

What is spec-driven development?
A way of building with AI coding agents where a written spec comes first. GitHub's Spec Kit describes it as defining what to build and why, then turning the specification into a plan, tasks, and working code.
What tools support spec-driven development?
GitHub's Spec Kit, with separate specify, plan, tasks, and implement steps, and the Kiro editor, which uses requirements, design, and tasks files. Both keep the spec as markdown next to the code.
What is the main problem with spec-driven development?
Specs usually guide the first build and are then left unchanged, so the next agent reads rules that are no longer true. Critics also point to large volumes of markdown to review and agents that still ignore parts of the spec.

Related