Specification-driven development
Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software.
Spec-Driven Development
A software development approach in which specifications produced through human–AI dialogue guide implementation.
- How it is used
- Uses durable specifications to align coding-agent implementation and validation with intent established through human–AI dialogue.
- How deep it goes
- Elaborates Discover, Design, and Task conversations, then follows implementation gaps into specification repair rather than prescribing one fixed artifact format.
- Examples
- Contrasts two URL-shortener builds and uses a link-expiry change to expose the risk of bypassing an existing specification.
- What you can do after
- Practice/perform specification-first feature delivery, revising the specification when implementation or testing exposes a gap.
Read how Spec-Driven Development explains specification-driven development →
Vibe Engineering
A development approach in which an authoritative specification drives implementation plans, tasks, tests, and delivery controls.
- How it is used
- Uses an authoritative specification to move from exploratory AI-assisted coding to production implementation and ownership.
- How deep it goes
- Explains the specify–implement–verify rhythm, executable contract scope, human oversight, task slicing, and CI/CD gates.
- Examples
- Uses a refund policy with expiry and partial-refund limits to illustrate executable examples.
- What you can do after
- Practice a verification-first workflow that derives tasks and gates from a specification and audits agent-generated results.
Read how Vibe Engineering explains specification-driven development →
Context Engineering
Spec-driven development is a software development approach in which a specification guides planning, task breakdown, and implementation.
- How it is used
- Organizes AI-assisted development around a specification that supplies stable context across planning, implementation, testing, review, and change.
- How deep it goes
- Distinguishes three specification–code relationships and walks through a staged workflow from captured intent to implementation.
- Examples
- Uses an API endpoint specification and a backlog-scoring feature to illustrate constraints, plans, and executable tasks.
- What you can do after
- Apply it via GitHub Spec Kit using staged commands for specification, clarification, planning, tasks, analysis, and implementation.
Read how Context Engineering explains specification-driven development →
Designing AI Agents
A software-development approach in which structured specifications guide implementation and define intended behavior.
- How it is used
- Guides model-assisted implementation by defining acceptable behavior, constraints, and evaluation before agents generate code.
- How deep it goes
- Defines proposals, designs, and task lists, and distinguishes durable project constraints from change-specific specifications.
- Examples
- Uses a rollout change to distinguish a durable specification for the authoritative utility from a change-specific plan.
- What you can do after
- Apply it by organizing a change into a proposal, design, and ordered tasks, then constraining and evaluating implementation.
Read how Designing AI Agents explains specification-driven development →
Also covered in
- Build High Value Software SystemsIn early access (MEAP)
- Effective Behavior-Driven DevelopmentIn early access (MEAP)
What to know first
- AI agentAn AI agent is a computational system that uses artificial intelligence to interpret information and select or perform actions toward goals while interacting with an environment.
- artificial intelligenceArtificial intelligence is the field of computing concerned with creating systems that perform tasks associated with intelligence, such as learning, reasoning, perception, and decision-making.
- behavior-driven developmentBehavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
Related concepts
- behavior-driven developmentcontrasts with · Behavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
- waterfall modelcontrasts with · The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them.
- specificationuses · A specification is a description of the requirements, expected behavior, properties, interfaces, or constraints that a system or component is expected to satisfy.
- autonomous iteration workflowcontrasts with · An autonomous iteration workflow is a repeated execution process steered by governing constraints toward learning and convergence.
- featureuses · A feature is a distinct capability, behavior, or characteristic provided by a product, service, or software system.
- GSDimplemented by · GSD is a structured, spec-driven software development workflow that coordinates tasks and maintains project context or state.
Questions about specification-driven development
What is specification-driven development?
Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software.
Which Manning books explain specification-driven development?
Spec-Driven Development, Vibe Engineering, Context Engineering and Designing AI Agents.
What should I know before learning specification-driven development?
Manning books that teach specification-driven development usually introduce AI agent, artificial intelligence, behavior-driven development and language model first.
What is the difference between specification-driven development and behavior-driven development?
Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software. Behavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
What is specification-driven development also called?
Specification-driven development is also called SDD or spec-driven development.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.



