Spec-Driven Delivery
How a unit of work becomes a written specification before anything is created in a workspace.
Principle
If it isn't specified, it isn't started.
A spec names the inputs, the outputs, the owner and the acceptance criteria. Anything created in a workspace without one is undocumented by construction, and undocumented platforms are the ones that cannot be handed over.
Structure
Define
Build
Accept
From request to merged, verified change.
Procedure
- 01
Write the specification
Scope, inputs, outputs, owner and acceptance criteria in one document. Placeholder body copy to be completed.
- 02
Review before build
A second engineer reviews the spec against the architecture standards. Placeholder body copy to be completed.
- 03
Branch from the spec
The branch name carries the spec identifier so the change is traceable. Placeholder body copy to be completed.
- 04
Close the spec on acceptance
Acceptance criteria are checked explicitly before the spec is closed. Placeholder body copy to be completed.
Verification
- Every merged change traces to a specification.
- Acceptance criteria were written before the build started.
- The spec records an owner.
- Closed specs are retained as platform documentation.