liveBook · Manning

Specification organization

As explained in Spec-Driven Development

The arrangement of specifications across features, system state, or both.

Specification organization determines whether intent is captured around individual changes, the application’s current state, or both. The choice balances focused change-level reasoning against a coherent view of existing behavior. section 3.6.1

Common arrangements include:

  • Per-feature specifications keep the current change easier to reason about, but can obscure how the application works as a whole. section 3.6.1
  • A single evolving system specification gives a coherent current-state view, but can become cumbersome as the system grows. section 3.6.1
  • A hybrid pairs a change-level specification of feature intent with a current-state view of existing behavior. section 3.6.1

How Spec-Driven Development covers it

How deep it goes
Compares per-feature, evolving-system, and hybrid arrangements, explaining their clarity and maintenance tradeoffs.
Examples
Contrasts per-feature documents, a single evolving specification, and hybrid change-level/current-state views.
What you can do after
Evaluate specification arrangements by balancing focused change intent against a coherent current-state view.
How it connects
Connects feature specifications with evolving system specifications in hybrid approaches.

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.