Feature PRD
01-planning/product-requirementsA living document, one per feature. Evolves as you build — never frozen.
What it is
The Feature PRD is the second tier of the Cascade. Unlike a traditional spec, it's a living document — it evolves as market, design, and engineering reality changes. A PRD that doesn't change is a PRD nobody is reading.
When to write it
When you pick up a feature. Fill in the problem and goals first; leave the rest for later. Status flows backlog → in-progress → review → done.
What goes in it
- The problem, and who has it
- Goals and explicit non-goals
- Status and a completion rationale
- Links to the Prompt Briefs against it
How it fits
Governed by two guardrails: a PRD needs at least one Prompt Brief before it can go in-progress, and no more than five PRDs may be in-progress at once.
Get the templatestarter/docs/01-planning/product-requirements/feature-prd.md