specs before codeRev 2.0.0
Vague idea in.
Checked design spec out.
Describe what you want to build. The workshop tells you where the description is too vague to act on, asks only about those parts, then writes a design spec from a plan whose numbers and decisions are checked in code.
Title block
- Subject
- One sentence describing what you want built
- Method
- Clarify, choose a direction, then a checked plan and one writer
- Output
- A design spec: requirements, estimates, the core decision and its cost, architecture, APIs, data, failure modes and tests
The run4 stages
- 01
Draft
Describe the idea in a sentence. It gets scored for vagueness before anything is generated.
- 02
Discovery
Answer only the questions your description left open. Clear ideas skip straight past this.
- 03
Direction
Pick which version of the system to build. The choice goes into the brief the plan is written from.
- 04
Spec
One plan of the numbers and decisions, checked in code and revised until it holds; then one writer turns it into the design spec, which is checked against the plan.