liveBook · Manning

Specification-driven development

As explained in Spec-Driven Development

A software development approach in which specifications produced through human–AI dialogue guide implementation.

Specification-driven development (SDD) turns an idea into a reviewed specification before a coding agent implements it. The specification is a durable statement of intent: it gives the agent a target for implementation and validation, then remains available when the next feature is specified. A direct prompt may produce code sooner, but leaves more decisions to agent assumptions and session memory. section 2.2 section 2.3

Work through one feature slice at a time:

  • Discover the what: discuss the business purpose, scope, and behavior the feature needs. section 2.2.1
  • Design the how: decide the technical approach against that business intent. section 2.2.1
  • Task the work: turn the agreed intent and design into execution work, then let the agent implement and validate against the specification. section 2.2.1 section 2.2

Changing URL expiry without losing an earlier decision

Suppose a URL shortener initially keeps links permanently and forbids reassigning an issued shortcode. Permanently stored mappings may enforce the reassignment rule without explicit code for it. A direct code edit to expire links can therefore miss that rule. Specify the expiry change—including its effect on existing mappings—before applying it, then preserve the updated specification for later slices. section 3.1 section 2.4.6

When review or testing finds a gap, ask where intent was lost: in the dialogue, its capture in the specification, implementation, or validation. Repair the specification and regenerate misaligned work rather than letting an ad hoc code fix make it stale. The phases are revisitable, not a requirement to specify the whole application upfront. section 3.2 section 3.1 section 2.5.1

The artifact is a shared decision surface, not a Markdown quota. Product, architecture, engineering, and quality perspectives help make it accurate enough for both people and agents to use. Give a small feature only the detail needed to verify its behavior; use richer constraints and verification criteria when the change warrants them. section 2.5.2 section 2.5.4

How Spec-Driven Development covers it

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 it assumes
Assumes familiarity with feature development and coding agents while developing specification authoring through a URL-shortener example.
What you can do after
Practice/perform specification-first feature delivery, revising the specification when implementation or testing exposes a gap.
How it connects
Connects intent-driven development, coding agents, acceptance criteria, behavior-driven development, and test-driven development.

Also explained in

Compare how 4 books explain specification-driven development →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.