Product and project requirements: the problem, who has it, the success criteria, and the scope boundaries the system is built against.
- One file per product area or feature:
<topic>.md. - Start from
../templates/requirements.md. - Progress-neutral and tracker-neutral wording: no ticket IDs, no delivery status.
- Declare links: name the upstream docs this satisfies and the downstream docs it constrains.
- State what must be true and why, not how to build it — the how lives in
../design/.
Before starting a feature or changing scope — to confirm what the work has to achieve.