# Spec-Driven Development: Making the Spec the Single Source of Truth in the AI Era
SDD isn't a new concept, but it takes on structural significance in the AI4SE era — when code is generated by agents, the spec replaces code as the only human-readable source of truth.
Why Now
Martin Fowler re-popularized the SDD framework in 2025. But the real driving force comes from reality:
- The volume of agent-generated code has exploded: when 80% of code comes from AI, understanding it line by line through code review is no longer realistic
- Code is no longer the source of truth: an agent might generate one version today and refactor an entirely different one tomorrow — the only stable thing is the spec a human wrote
- Acceptance needs an anchor: without a spec, how do you judge whether a task the agent completed is right or wrong?
The Core Principles of SDD
| Principle | Explanation |
|---|---|
| Spec first | Write the spec before letting the agent generate code |
| Spec as gate | If a spec hasn’t passed review, the agent shouldn’t start executing |
| Changes go through the spec | Requirement changes → update the spec → agent regenerates |
| AI-readable | The spec’s format must work for both human and agent comprehension |
The Operational Flow
Human writes the spec -> review passes -> agent generates code -> verify against the spec -> mergeThe key isn’t “making the agent make fewer mistakes” — it’s “deciding when the human makes the decision.”
References
- Prezi Engineering: “We Tried Spec-Driven Development So You Don’t Have To” (2025)
- codæ: Contract-Driven Agentic Engineering (Vibeloom, 2026)
- Martin Fowler: SDD framework