LOOK UP WHEN NEEDED
Design document
Records interface, structure, and key implementation decisions.
An everyday example
A building plan shows rooms and pipe connections.
See how these concepts connect
- Improve a homeProject brief
- Agree rooms and usesRequirements
- Order the workDevelopment plan
- Inspect against criteriaAcceptance criteria
A brief explains purpose, requirements define scope, a plan orders work, and acceptance criteria define success. Names vary; the information still matters.
Where this term is useful
These are related contexts, not prerequisites.
Back in the project
When it comes up: When handing an idea to AI and agreeing on tasks.
What to do next: Save decisions in project files and check features, acceptance criteria, and exclusions.
Open the related method and stepsWhat can this analogy leave out?
Length does not guarantee clarity; related documents must agree.
Everyday examples explain roles and relationships; actual behavior follows the tool, language, or platform.