# Product requirements document: [Feature or product]

**Product owner:** [Name]  
**Status:** Draft  
**Version:** 0.1  
**Last updated:** YYYY-MM-DD  
**Target release:** [Date or release]

## Summary

[Describe the user problem and proposed outcome without prescribing implementation.]

## Problem statement

**Who has the problem?** [User segment]  
**What happens today?** [Current behavior]  
**Why does it matter?** [User and business impact]  
**Evidence:** [Research, support tickets, analytics, or links]

## Goals

- [Measurable outcome]

## Non-goals

- [What this release will not solve]

## Users and use cases

| User | Situation | Need | Desired outcome |
|---|---|---|---|
| [Persona] | [Context] | [Need] | [Outcome] |

## Requirements

| ID | Requirement | Priority | Acceptance criteria |
|---|---|---|---|
| FR-01 | The user can [action]. | Must | Given [context], when [action], then [result]. |

## User flow

1. [Entry point]
2. [User action]
3. [System response]
4. [Completion state]

## Edge cases and error states

- [Condition] → [Expected behavior]

## Content and design requirements

- [Copy, accessibility, responsive, localization, or design-system requirement]

## Analytics and success measures

| Event or metric | Definition | Baseline | Target |
|---|---|---:|---:|
| [Metric] | [How it is calculated] | [Value] | [Value] |

## Dependencies and constraints

- [System, team, legal, security, or timeline constraint]

## Rollout and rollback

- **Rollout:** [Stages, feature flag, audience]
- **Rollback trigger:** [Condition]
- **Rollback method:** [Action]

## Open questions

- [ ] [Question] · **Owner:** [Name] · **Due:** YYYY-MM-DD

## Approval

| Role | Name | Status | Date |
|---|---|---|---|
| Product | [Name] | Pending | |
| Design | [Name] | Pending | |
| Engineering | [Name] | Pending | |