PRD Writer

Goal

Convert a rough feature idea into a complete PRD with clear objectives, user stories, requirements, and success metrics.

Trigger

When a product manager or team member has a new feature idea or initiative that needs to be formalized for engineering and design handoff.

Steps

1. 1

   Analyze the feature idea provided below and extract core intent, target users, and the problem being solved: $feature_idea

   • □Core problem is clearly identified
   • □Target user segment is defined
   • □Key value proposition is apparent

   Analyze the feature idea provided below and extract core intent, target users, and the problem being solved:
   
   $feature_idea

2. 2

   Write the PRD header section: include a one-line feature summary, problem statement (2–3 sentences), goals, and explicitly list what is out of scope.

   • □Problem statement is user-centric, not solution-centric
   • □Goals are measurable or at least directional
   • □At least 2 out-of-scope items are listed
3. 3

   Generate 3–5 user stories in 'As a [user], I want to [action] so that [outcome]' format. Cover the primary happy path and at least one edge case or secondary persona.

   • □Each story has a clear actor, action, and outcome
   • □At least one edge case or non-primary user is covered
4. 4

   List functional requirements as numbered acceptance criteria (what the system must do) and non-functional requirements (performance, security, accessibility). Be specific and testable.

   • □Each requirement is independently verifiable
   • □Non-functional requirements include at least one accessibility or performance item
5. 5

   Define success metrics: list 2–4 KPIs or measurable outcomes that indicate the feature is working, and describe how each would be tracked (e.g., event logging, surveys, funnel analysis).

   • □Each metric is quantifiable
   • □Tracking method is specified for each metric
6. 6

   Add an open questions and dependencies section: surface any unresolved decisions, technical unknowns, cross-team dependencies, or stakeholder approvals needed before build can begin.

   • □At least 2 open questions are raised
   • □Any external team dependencies are named

Output format

Return the PRD as a structured document with clearly labeled sections: Summary, Problem Statement, Goals & Non-Goals, User Stories, Functional & Non-Functional Requirements, Success Metrics, and Open Questions & Dependencies. Use headers, numbered lists, and bullet points for scannability.