Stable3 min read
PRD
Specify product requirements with strategic context.
PRD phase produces product requirements anchored in strategic context — problem, scope, acceptance signals, non-goals.
PRDs written in a vacuum ship wrong things fast. Sculpt PRDs inherit personas, journeys, and OKRs.
When backlog top items need specification before build or vendor RFP.
- Select backlog item with outcome link.
- State problem and personas affected.
- Define acceptance criteria and metrics.
- List non-goals and dependencies.
- Review with engineering for feasibility flag.
- Acceptance criteria testable.
- Non-goals prevent scope creep.
- Links to persona/journey IDs.
- Solution spec only — no problem.
- Missing non-goals.
- PRD never updated after learning.
/prd phase. Prose + structured requirements referencing PER-, CJM-, OKR- IDs.
Sources & further reading
- Cohn, M. (2004). User Stories Applied. Addison-Wesley.