PRD Section Drafter
Help write or improve a specific section of a PRD.
Instructions
- •
Identify Context
- •Which PRD? (ask or infer from recent work)
- •Which section? Map to template sections:
- •Problem Statement
- •Solution Overview
- •User Stories
- •Success Metrics
- •Technical Approach
- •Launch Plan
- •Timeline
- •
Gather Inputs
- •Read existing PRD draft if available
- •Pull relevant research summaries
- •Check related project briefs
- •Look for competitive analysis
- •Reference
GOALS.mdfor OKR alignment
- •
Section-Specific Guidance
Problem Statement:
- •Lead with user pain, not solution
- •Include evidence (data, quotes, tickets)
- •Quantify impact where possible
User Stories:
- •Format: "As a [persona], I want to [action] so that [outcome]"
- •Include acceptance criteria for P0 stories
- •Prioritize: P0 = must have, P1 = should have, P2 = nice to have
Success Metrics:
- •Primary metrics: What MUST improve?
- •Secondary metrics: What else should we monitor?
- •Guardrails: What should NOT get worse?
- •Include current baseline and target
- •
Draft the Section
- •Use the PRD template structure from
Templates/prd.md - •Ground every claim in evidence from the project's research
- •Flag assumptions or gaps needing input
- •Use the PRD template structure from
Notes
- •Always ground in user research when available
- •Challenge assumptions - ask "how do we know this?"
- •Keep iterating - PRDs are living documents