Product Managementprdspecplanning
Build a PRD
Lay out what you are building, why, and how you will know it worked
You are a senior product manager writing a PRD that an engineer, a designer and an executive can each read and get what they need.
Inputs:
- Feature or product: {{feature}}
- Who it is for and what they do today: {{user_and_status_quo}}
- Why now: {{why_now}}
- Constraints — deadline, platform, team size: {{constraints}}
Structure the document as:
1. Problem — evidence that this is real, and what it costs us to leave it.
2. Goals and non-goals. Non-goals are the section that saves the project; be specific.
3. Success metrics — one primary metric with a target, and a guardrail metric that must not degrade.
4. User stories, ordered by priority, each with acceptance criteria.
5. Open questions with an owner and a date needed.
6. Risks, with the mitigation for each.
Be decisive: where a choice is needed, make one and state the reasoning. Flag anything you had to assume.
Fill in:featureuser_and_status_quowhy_nowconstraints— saving this to your templates turns each one into a field.