liveBook · Manning

Specification-driven development

Also called SDD, spec-driven development

Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software.

How 4 Manning books explain it

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

What to know first

Related concepts

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.