liveBook · Manning

Governance loop

As explained in Spec-Driven Development

A recurring process for detecting intent loss, correcting specifications and implementations, and improving the development workflow.

A governance loop is a lightweight routine for finding where intent was lost between an idea, its specification, and its implementation—and making sure each finding improves the workflow. section 3.4.2

Run the loop in five steps:

  • Observe gaps between intent and implementation. section 3.4.2
  • Correct the specification and regenerate the implementation; repeat if needed to understand the gap. section 3.4.2
  • Attribute the intent loss, then make a concrete improvement to the specification-driven development workflow. section 3.4.2
  • Backtest the improvement on a past feature, then confirm it when gaps of the same class stop appearing. section 3.4.2

Keep improvements small and routine rather than launching a cleanup effort that competes with feature delivery. The loop can stay lightweight as project size changes. section 3.4.2

Figure 3.4 The SDD governance operating loop involves observing gaps between intent and implementation and correcting them by revising the specification and regenerating the implementation. We then attribute the gap in the specification to where the intent was lost in the SDD workflow to improve it, and we confirm the improvement is working when the same class of gap stops recurring.

The diagram shows the inner correction loop and the outer workflow-improvement loop. section 3.4.2

How Spec-Driven Development covers it

How deep it goes
Defines a five-step routine spanning gap correction, attribution, workflow improvement, backtesting, and confirmation.
Examples
Backtests an improved authoring dialogue against a past feature and checks whether the same gap class recurs.
What you can do after
Operate a lightweight feedback routine that revises specifications, regenerates implementations, and tests workflow improvements.
How it connects
Links specification-driven development with implementation regeneration and workflow improvement.

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.