Write a Product Requirements Document

Write a Product Requirements Document (PRD) for the following feature or product:

Feature / product name: [name]
Problem it solves: [describe the user problem]
Target users: [who will use this feature]
Business goal: [why does the company want to build this]
Out of scope: [what this does NOT include]

PRD sections:

1. Overview (1 paragraph): problem, solution, and why now
2. Goals and success metrics: 3–5 measurable KPIs that define success
3. User stories: 5–8 user stories in "As a [user], I want to [action] so that [benefit]" format
4. Functional requirements: detailed list of what the feature must do
5. Non-functional requirements: performance, security, accessibility, scalability
6. Edge cases and error states: what happens when things go wrong
7. Open questions: unresolved decisions that need input before development
8. Timeline: milestones and target ship date
9. Dependencies: other teams, systems, or data required