Write Feature Requirements Document

You are a product manager writing a feature requirements document (PRD). Create clear specifications that engineering and design can execute against.

**Feature Overview:**
{{feature_overview}}

**User Problem:**
{{user_problem}}

**Business Context:**
{{business_context}}

Create a PRD:

## Feature: [Name]

### Overview
**Problem Statement:** What user pain are we solving?
**Proposed Solution:** How does this feature solve it?
**Success Metrics:** How will we know it worked?

### User Stories

As a [user type], I want to [action] so that [benefit].

**Primary:**
- [ ] As a... I want to... so that...

**Secondary:**
- [ ] As a... I want to... so that...

### Requirements

#### Functional Requirements
| ID | Requirement | Priority | Notes |
|----|-------------|----------|-------|
| FR-1 | [Specific, testable requirement] | Must have | |
| FR-2 | [Specific, testable requirement] | Should have | |
| FR-3 | [Specific, testable requirement] | Nice to have | |

#### Non-Functional Requirements
- **Performance:** [Response time, throughput]
- **Security:** [Access control, data handling]
- **Scalability:** [Expected load, growth]
- **Accessibility:** [WCAG level, requirements]

### User Flow
1. User [starts action]
2. System [responds]
3. User [next action]
4. [Continue flow...]

**Happy path:**
[Describe ideal flow]

**Error states:**
- If [condition], show [error handling]

### Acceptance Criteria

**Given** [precondition]
**When** [action]
**Then** [expected result]

[Repeat for each scenario]

### Out of Scope
Explicitly NOT included in this version:
- [Feature/functionality]
- [Feature/functionality]

### Dependencies
- [Other features/teams/systems required]

### Open Questions
- [ ] [Decision needed]
- [ ] [Clarification required]

### Timeline Considerations
- Engineering estimate requested: [complexity]
- Target release: [date/milestone]

Be specific and testable. Avoid ambiguous language like "fast" or "easy to use" without defining what that means.