Product Requirements Document (PRD) Writer

A complete PRD with problem statement, user stories, success metrics, and acceptance criteria, ready for engineering review.

Best For

•A product manager kicking off a new feature uses it to turn a rough idea into user stories with acceptance criteria the engineering team can estimate against
•A founder writing their first PRD without a formal product background uses the structure to make sure edge cases and dependencies are identified before a sprint starts
•A PM handing off a feature to a new engineering team uses the open questions section to flag unresolved decisions instead of letting engineers guess at intent

Prompt Template

Write a Product Requirements Document for the following feature or product: [FEATURE/PRODUCT NAME]. Context: [2-3 sentence description of what this is and why we're building it]. Write the PRD with these sections: (1) Problem Statement, what specific user problem does this solve, and what is the cost of not solving it, (2) Target Users, primary persona(s) with their context and current workaround, (3) Goals and Success Metrics, 2–3 measurable outcomes we will track to know this worked (include specific KPI targets), (4) Scope, what is in scope for v1 and what is explicitly out of scope, (5) User Stories, write the 5 most critical user stories in the format "As a [user], I want to [action] so that [outcome]" with acceptance criteria for each, (6) Edge Cases and Constraints, list 3–5 edge cases the engineering team must consider, (7) Dependencies, what does this feature depend on or block, (8) Open Questions, list unresolved decisions that need stakeholder input. Keep the tone precise and implementation-agnostic.

Pro Tip

State the cost of not solving the problem in concrete terms (lost revenue, support ticket volume, churn) rather than just describing the problem, since that framing is what makes the goals and success metrics section specific instead of aspirational.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Problem Statement: Users abandon the checkout flow at a 22% rate when asked to create an account before purchase, costing an estimated $40K in monthly lost revenue. User Story: As a first-time shopper, I want to check out as a guest so that I can complete my purchase without friction. Acceptance criteria: guest checkout captures email and shipping address only; account creation is offered post-purchase, not required. Edge case: guest orders must still be linkable to an account if the user registers later using the same email.