doc-brd
doc-brd
Purpose
Create a Business Requirements Document (BRD) — Layer 1 of the SDD flow. A BRD captures business objectives, stakeholders, scope, and success criteria in business language, before any product or technical detail.
Layer: 1 (entry point, no upstream). Downstream: PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code.
One MVP iteration = 5–15 focused requirements total, spread across as many BRD
documents as that needs: a single BRD SHOULD carry at most 5 functional
requirements (GD-14), so a cycle needs at least ceil(N/5) documents — a floor, not
a ceiling. Beyond five, start BRD-02. New features also get a new BRD. Use
@depends: BRD-NN only for a genuine hard prerequisite; a document created because
the previous one hit the cap is a sibling, recorded in the BRD-00 index.