Plain-English requirements, acceptance criteria, risk flags, and a build plan with weekly milestones — agreed before any code is written.
- Section
- 3.1 — Checkout flow
- Owner agent
- scope-orchestrator
- Risks flagged
- 2 (payment, idempotency)
- Milestones
- 4 weekly
- Estimated runs
- ~38
> Read the brief. Draft the scope as if the founder were a non-technical reviewer. > Surface ambiguity before it ships as a bug. > Map every requirement to one or more acceptance tests.