Product Requirements Document (PRD) Generator

You are a senior product manager. Create a comprehensive Product Requirements Document (PRD) for the following feature/product.

**Product/Feature Overview:**
{product_overview}

**Target Users:**
{target_users}

**Business Goals:**
{business_goals}

**Constraints:**
- Timeline: {timeline}
- Resources: {resources}
- Technical limitations: {technical_constraints}

Create a complete PRD following this structure:

**1. Executive Summary**
- One-paragraph overview
- Key problem being solved
- Expected impact

**2. Problem Statement**
- Current pain points (backed by data/research)
- User stories (As a [user], I want [goal], so that [benefit])
- Success metrics (SMART goals)

**3. Goals and Non-Goals**
**Goals:**
- Primary objective
- Secondary objectives
- Success criteria

**Non-Goals** (what we're explicitly not solving):
- Out of scope items
- Future considerations

**4. User Personas**
For each persona:
- Name & demographics
- Pain points
- How they'll use the feature
- Success criteria for them

**5. User Experience**
- User flows (step-by-step)
- Wireframes/mockups description
- Key interactions
- Edge cases

**6. Functional Requirements**
List as P0 (must-have), P1 (should-have), P2 (nice-to-have):
- FR-001: [Requirement description] [Priority]
- FR-002: [Requirement description] [Priority]

**7. Non-Functional Requirements**
- Performance: [load time, response time, throughput]
- Security: [authentication, authorization, data protection]
- Scalability: [expected users, growth projections]
- Accessibility: [WCAG compliance, screen reader support]

**8. Technical Considerations**
- Architecture overview
- Integration points
- Data model
- API requirements
- Third-party dependencies

**9. Success Metrics**
| Metric | Current | Target | Measurement Method |
|--------|---------|--------|-------------------|
| Primary KPI | baseline | goal | how to track |
| Secondary KPI | baseline | goal | how to track |

**10. Launch Plan**
- Rollout strategy (phased, beta, full launch)
- Feature flags / kill switches
- Monitoring and alerts
- Rollback plan

**11. Risks and Mitigations**
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk description] | High/Med/Low | High/Med/Low | [Strategy] |

**12. Open Questions**
- Question 1: [Who needs to answer? By when?]
- Question 2: [Who needs to answer? By when?]

**13. Appendix**
- User research findings
- Competitive analysis
- Technical specs
- Design mockups