Write specs people actually read.
A spec's job is shared understanding, not completeness. One clear page that stays current beats thirty that nobody opens.
The One-Page Spec
01 · PROBLEM & WHO
What's broken, for which customers, and how we know.
02 · OUTCOME & METRIC
What changes if we succeed, and how we'll measure it.
03 · SCOPE
What's in. Just as important: what's out.
04 · KEY FLOWS
The main journeys, sketched. Link to designs.
05 · OPEN QUESTIONS
What we don't know yet, and who's finding out.
06 · RISKS & DEPENDENCIES
Compliance, other teams, vendors, deadlines.
Write it for the engineer who joins the team next month and needs to understand why, not just what.
Short, living, and clear on why.