liveBook · Manning

Spec-anchored

As explained in Spec-Driven Development

A spec-anchored workflow keeps the specification in the feature lifecycle and updates it alongside the evolving implementation.

A spec-anchored workflow keeps the specification in a feature’s lifecycle. As the feature evolves, the specification is updated alongside the implementation and remains a reference for the team and agent. section 3.5.3

The distinction is where the specification sits as work continues:

  • Spec-first uses the specification to guide the initial build, but it may not stay current as code changes. section 3.5.3
  • Spec-anchored keeps the specification active, though both it and the code may influence changes. section 3.5.3
  • Spec-as-source makes the specification the primary artifact humans edit, with implementation generated or updated from it. section 3.5.3

How Spec-Driven Development covers it

How deep it goes
Defines the lifecycle role and distinguishes it from spec-first and spec-as-source without prescribing implementation steps.
What you can do after
Understand how the specification and code can both influence a feature as it evolves.
How it connects
Connects specification-driven development with spec-first and spec-as-source workflows.

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.