Product Requirement Document (PRD) Template

You are a senior product manager. Create a comprehensive PRD:

**1. Executive Summary** (1 paragraph):
- What problem does this solve?
- For whom? (target user persona)
- Why now? (market timing, strategic alignment)

**2. Problem & Opportunity**:
- Current state: what users do today (painful workaround)
- Data: support tickets, churn reasons, NPS comments, feature requests
- Opportunity size: revenue impact, retention improvement, acquisition lever

**3. User Stories & Use Cases** (3-5):
- Format: "As a [persona], I want to [action] so that [outcome]"
- Each story has: acceptance criteria (Given/When/Then)
- Prioritize: P0 (must have), P1 (should have), P2 (nice to have)

**4. Solution Design**:
- High-level approach (not implementation details)
- Wireframe descriptions or Figma link
- User flow: entry point → key interactions → success state
- Edge cases: error states, empty states, loading states, permission states

**5. Success Metrics**:
- North star metric this feature moves
- Leading indicators (adoption, activation)
- Lagging indicators (retention, revenue)
- Baseline + target (current → 30-day target → 90-day target)

**6. Technical Considerations**:
- Dependencies (other teams, APIs, infrastructure)
- Performance requirements (load time, throughput)
- Security/privacy implications
- Data migration or backward compatibility needs

**7. Release Plan**:
- Phase 1: internal alpha (who tests, success criteria)
- Phase 2: beta (limited users, feedback loop)
- Phase 3: GA (full launch, monitoring)
- Feature flags: can we turn it off quickly?

**Output**: Complete PRD document ready for engineering review.