# PRD: Feature name

| Field | Value |
|-------|-------|
| Status | Draft / In review / Approved / Shipped |
| Author | @pm |
| Stakeholders | @eng-lead, @design, @data |
| Target release | vX.Y / YYYY-MM |

## Problem statement

What user problem are we solving? Evidence: support tickets, user
interviews, metrics. One paragraph.

## Goals & success metrics

| Goal | Metric | Target |
|------|--------|--------|
| Increase activation | % new users reaching "aha" | +15% |
| Reduce time-to-value | Median minutes to first export | <3 min |

## Non-goals

- What this project explicitly does NOT cover

## Users & use cases

- **Persona A** – needs X because Y
- **Persona B** – needs Z

## Requirements

### Must have (P0)

1. Requirement – acceptance criteria
2. Requirement – acceptance criteria

### Should have (P1)

1. Requirement

### Nice to have (P2)

1. Requirement

## User flow

```mermaid
flowchart TD
    A[User opens app] --> B{Has document?}
    B -->|No| C[Create from template]
    B -->|Yes| D[Open existing]
    C --> E[Edit + preview]
    D --> E
    E --> F[Export]
```

## Design

Links to mockups/prototypes. Key screens described.

## Technical considerations

Performance budget, storage implications, browser compatibility, privacy.

## Risks & mitigations

| Risk | Likelihood | Mitigation |
|------|-----------|------------|
| Risk one | Medium | Mitigation plan |

## Launch plan

- [ ] Feature flag rollout 10% → 50% → 100%
- [ ] Docs + changelog updated
- [ ] Announcement prepared

## Open questions

- [ ] Unresolved question and who owns it