liveBook · Manning

Spec-as-source

As explained in Spec-Driven Development

A spec-as-source workflow treats the specification as the primary editable artifact from which an agent generates or updates the implementation.

Spec-as-source makes the specification the primary artifact humans edit; an agent generates or updates the implementation from it. Changes begin in the specification, not directly in code. section 3.5.3

The distinction from less prescriptive specification workflows is where ongoing changes begin:

  • Spec-first uses a specification to guide the initial build, but it may not remain central afterward. section 3.5.3
  • Spec-anchored keeps the specification in the feature lifecycle, though both specification and code may influence changes. section 3.5.3
  • Spec-as-source expects changes to start in the specification and disallows direct code changes. section 3.5.3

How Spec-Driven Development covers it

How deep it goes
Defines and contrasts three specification workflow levels, but does not detail implementation mechanics.
What you can do after
Apply it by routing changes through the specification and having an agent generate or update the implementation.
How it connects
Connects Spec-Driven Development with spec-first and spec-anchored 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.