# PRD: [Feature name]

| Field | Detail |
| --- | --- |
| Status | Draft / In review / Approved / Shipped |
| Product owner | [Name] |
| Engineering lead | [Name] |
| Design lead | [Name] |
| Target release | [Date or milestone; mark estimates] |
| Last updated | [YYYY-MM-DD] |
| Related work | [Jira epic URL] |

## 1. Problem and evidence

[Describe who has the problem, what happens today, and why it matters.]

- Target users: [Role, segment, or workflow]
- Current workaround: [What users do now]
- Evidence: [Research link, support theme, or baseline data]
- Unknowns: [What still needs validation]

## 2. Goals and success measures

[Describe the user outcome this release should achieve.]

| Outcome | Metric definition | Baseline | Target | Measurement owner |
| --- | --- | --- | --- | --- |
| [Outcome] | [Event, denominator, time window] | [Known value or unknown] | [Agreed target] | [Name] |

## 3. Scope and non-goals

### In scope

- [Capability required for the first release]
- [Supported user group or platform]

### Out of scope

- [Deferred capability and reason]
- [Explicit limitation]

## 4. User journey

As a [user], I want to [action], so that I can [outcome].

1. [Entry point and prerequisite]
2. [Main action]
3. [Feedback and successful outcome]
4. [Failure path and recovery]

Design reference: [Link to reviewed wireframes or prototype]

## 5. Functional requirements

| ID | Requirement | Priority | Acceptance criteria |
| --- | --- | --- | --- |
| R1 | [Observable behavior] | Must | [Given a state, when an action occurs, then a result follows] |
| R2 | [Observable behavior] | Should | [Specific, testable result] |

## 6. Edge cases and quality requirements

- Empty state: [What appears before there is data?]
- Invalid input: [How is the problem explained and corrected?]
- Permissions: [Who may view, create, change, or delete?]
- Interrupted action: [Retry, cancellation, or recovery behavior]
- Accessibility: [Keyboard, labels, focus, and announcements to verify]
- Performance: [Agreed threshold, workload, and test conditions]
- Data handling: [Data collected, access, retention, and deletion]

## 7. Dependencies, risks, and assumptions

| Item | Impact | Owner | Validation or mitigation | Due |
| --- | --- | --- | --- | --- |
| [Dependency, risk, or assumption] | [What it affects] | [Name] | [Next step] | [Date] |

## 8. Open questions and decisions

| Question | Owner | Decision needed by | Resolution |
| --- | --- | --- | --- |
| [Unresolved question] | [Name] | [Date] | [Decision and rationale, or pending] |

## 9. Release and measurement plan

- Release owner: [Name]
- Rollout: [Audience, stages, and readiness checks]
- Rollback or disable criteria: [Signal and responsible person]
- Support readiness: [Help content, known limitations, escalation]
- Measurement review: [Date, owner, and dashboard link]

## 10. Review checklist

- [ ] The problem has supporting evidence or is labeled an assumption.
- [ ] Scope and non-goals are explicit.
- [ ] Each must-have requirement has testable acceptance criteria.
- [ ] Design, engineering, and relevant stakeholders have reviewed the draft.
- [ ] Open questions have owners and decision dates.
- [ ] Release and measurement owners are assigned.

## Change log

| Date | Change | Reason | Owner |
| --- | --- | --- | --- |
| [YYYY-MM-DD] | [Summary] | [Why it changed] | [Name] |