liveBook · Manning

Spec-first

As explained in Spec-Driven Development

A spec-first workflow creates a specification before implementation to guide an initial build without necessarily keeping the specification central afterward.

Spec-first change routes implementation through a specification, giving it control authority. But if the specification omits intent, agents must fill gaps, and results can vary despite the disciplined workflow. section 3.5.3

Regeneration test

Discard the implementation and ask an agent to regenerate it from the same specification. If the behavior changes, improve the specification’s fidelity through dialogue, richer intent capture, construction constraints, and deterministic verification—not by simply documenting the generated result. section 3.5.3

How Spec-Driven Development covers it

How deep it goes
Distinguishes specification authority from fidelity and gives a regeneration test, but does not detail a complete specification workflow.
Examples
Tests fidelity by discarding an implementation and regenerating it from the same specification.
What you can do after
Evaluate specification fidelity by checking whether regeneration preserves behavior, then strengthen captured intent and verification.
How it connects
Connects specifications with agent-driven implementation changes and codebase context.

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.