Spec-Driven Development (SDD)
An engineering methodology that uses strict, machine-readable specifications to guide and validate code generated by AI agents.
“Specifications are the deterministic contracts that bind probabilistic coding agents to reality.”
Conversational coding works for simple scripts but fails catastrophically at enterprise scale. When developers rely on vague natural language to direct AI, they invite semantic drift, subtle bugs, and unmaintainable architectures. By enforcing Spec-Driven Development, organizations establish rigorous validation gates that prevent AI coding agents from going off-track. It restores engineering discipline to the AI era, ensuring that code generated by machines is governed by contracts written and verified by humans.
Richard Ewing’s Research Thesis
Do not converse with your coding agent; constrain it with executable specifications.
Why This Specification Exists
Vibe coding produces unreliable and unmaintainable enterprise code.
Conversational prompt iteration with coding assistants.
Lack of deterministic boundaries for AI-generated code.
Machine-readable specifications serving as validation gates.
What Changes If You Believe This?
Developers write strict schemas and contracts instead of boilerplate syntax.
Reduces the Debugging Tax by preventing structural errors early.
Faster reliable feature delivery.
API boundaries are strictly enforced.
Recommended Action by Role
Make executable specifications mandatory for any AI code generation in CI/CD.
Latest Publications & Research Activity
Why Your CFO Hates Your Agile Transformation
The Innovation Tax Audit: Is Your R&D Actually Just OpEx?
In the Vibe Coding Era, What Does a Software Engineer Even Do?
Frequently Asked Questions
Q:Is SDD just TDD for AI?
It shares DNA with TDD, but SDD focuses on defining the structural schema and API boundaries before generation.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
| Evidence Item | Publisher | Evidence Type | Strength | Role | Action |
|---|---|---|---|---|---|
| The Subprime Code Crisis | Beehiiv | Industry Analysis | ★★★★★ | Origin | Inspect ↗ |
| In the Vibe Coding Era, What Does a Software Engineer Even Do? | Built In | Executive Essay | ★★★★ | Supports | Inspect ↗ |
| GitHub Copilot Is Generating More Code Than Your Team Can Review | CIO.com | Industry Analysis | ★★★★★ | Extends | Inspect ↗ |
Recommended Citation
Ewing, R. (2026). "Spec-Driven Development (SDD)." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/spec-driven-development
@article{ewing_spec_driven_development,
author = {Ewing, Richard},
title = {Spec-Driven Development (SDD)},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/spec-driven-development}
}