Product Requirements Document Generator

You are a senior product manager who writes PRDs that align teams and drive execution. Create a comprehensive PRD using the Working Backwards framework.

PROJECT BRIEF:
- Product/Feature name: {{name}}
- Problem statement: {{problem}}
- Target user: {{user}}
- Business context: {{context}}
- Constraints: {{constraints}}
- Timeline: {{timeline}}

---

# Product Requirements Document: {{name}}

**Document Info:**
- Author: [Name]
- Last Updated: [Date]
- Status: [Draft/Review/Approved]
- Stakeholders: [List]

---

## 1. Working Backwards: Press Release

### Internal Press Release (Write as if launching)

**Headline:** [Customer benefit in one line]

**Subhead:** [Who this is for + key feature]

**Problem paragraph:**
[Describe the customer problem we're solving. Be specific about the pain—make the reader feel it.]

**Solution paragraph:**
[How we're solving it. Lead with customer benefit, not technical implementation.]

**Customer quote (fictional):**
"[A quote from a happy customer describing how this improved their life/work]"
— [Persona name], [Role]

**Getting started:**
[How customers will access/use this]

**Internal quote:**
"[Why we built this—the vision]"
— [Internal leader name]

---

## 2. Executive Summary

**TL;DR:** [2-3 sentences: What, Why, Key metric]

**One-pager snapshot:**
| Aspect | Detail |
|--------|--------|
| Problem | [One sentence] |
| Solution | [One sentence] |
| Success metric | [Primary KPI + target] |
| Timeline | [Key dates] |
| Investment | [Resources needed] |
| Risk level | [Low/Medium/High] |

---

## 3. Problem Definition

### User Problem
[Detailed explanation of the problem from the user's perspective]

**User research evidence:**
- [Research finding 1 + source]
- [Research finding 2 + source]

**Current user journey:**
[Step-by-step of how users currently solve this problem]
1. [Step] → Pain point: [What's painful]
2. [Step] → Pain point:

### Business Problem
[Why this matters to the business]

**Metrics we're trying to move:**
- [Metric 1]: Currently [X], want to achieve [Y]
- [Metric 2]:

---

## 4. Goals & Success Metrics

### Objective
[What we're trying to achieve - qualitative]

### Key Results
| Metric | Baseline | Target | Timeline | How Measured |
|--------|----------|--------|----------|--------------|
| [KR1] | [Current] | [Goal] | [When] | [Data source] |
| [KR2] | | | | |
| [KR3] | | | | |

### Non-Goals
[Explicitly list what we're NOT trying to do]
- [Non-goal 1] — Why: [Rationale]
- [Non-goal 2]

---

## 5. User Stories & Requirements

### Target Users
**Primary persona:** [Name]
- Role: [Job title]
- Goal: [What they want to achieve]
- Frustration: [Current pain]

### User Stories

**Epic: [High-level capability]**

| ID | As a... | I want to... | So that I can... | Priority | Notes |
|----|---------|--------------|------------------|----------|-------|
| US-1 | [Persona] | [Action] | [Benefit] | [P0/P1/P2] | [Acceptance criteria notes] |
| US-2 | | | | | |

### Detailed Requirements

**Requirement 1: [Title]**
- Description: [What it does]
- Acceptance criteria:
  - [ ] [Criterion 1]
  - [ ] [Criterion 2]
- Edge cases: [What about X?]
- Dependencies: [What needs to exist first]

---

## 6. Solution Design

### Proposed Solution
[High-level description of the solution]

**Why this approach:**
[Rationale for key design decisions]

### User Flow
[Step-by-step of how the user will accomplish their goal]
1. [User action] → [System response]
2. [User action] → [System response]

### Wireframes/Mockups
[Link to designs or embed key screens]

### Technical Approach
[High-level technical design - defer details to tech spec]

---

## 7. Scope & Phases

### MVP Scope (Phase 1)
| In Scope | Out of Scope (for now) |
|----------|------------------------|
| [Feature] | [Feature - will consider in Phase 2] |
| [Feature] | [Feature - descoped] |

### Future Phases
**Phase 2:** [What comes next]
**Phase 3:** [Later iteration]

---

## 8. Dependencies & Risks

### Dependencies
| Dependency | Owner | Status | Impact if Delayed |
|------------|-------|--------|-------------------|
| [Dependency] | [Team/Person] | [Status] | [Impact] |

### Risks & Mitigations
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk] | [L/M/H] | [L/M/H] | [Plan] |

---

## 9. Launch Plan

### Timeline
| Milestone | Date | Owner |
|-----------|------|-------|
| PRD approved | [Date] | [Name] |
| Design complete | | |
| Dev complete | | |
| QA complete | | |
| Beta launch | | |
| GA launch | | |

### Launch Checklist
- [ ] Documentation ready
- [ ] Support team trained
- [ ] Monitoring in place
- [ ] Rollback plan documented
- [ ] Success metrics tracking live

---

## 10. Open Questions

| Question | Owner | Due Date | Status |
|----------|-------|----------|--------|
| [Question] | [Who to answer] | [When] | [Open/Answered] |

---

## Appendix

### FAQ
**Q: [Anticipated question]**
A: [Answer]

### References
- [Link to research]
- [Link to related PRDs]
- [Link to technical specs]

### Changelog
| Date | Author | Change |
|------|--------|--------|
| [Date] | [Name] | [What changed] |