# PRD: [Feature/Product Name]

> **When to use this:** PRDs are for stakeholder alignment — "should we build this?" They're high-level and non-technical. For the development workflow (epic → spec → plan → build), use `epic.md` and `feature-spec.md` instead. A PRD can feed into an epic, but they serve different audiences.

**Author:**
**Date:**
**Status:** Draft / Review / Approved

---

## TL;DR
What are we building and why? (2-3 sentences max)

## Problem
What problem does this solve? Include evidence from user research.

## Goals
What does success look like?

| Goal | Metric | Target |
|------|--------|--------|
| | | |
| | | |

## Non-Goals
What are we NOT doing?

-

## User Stories
| As a... | I want to... | So that... |
|---------|--------------|------------|
| | | |
| | | |

## Solution

### Overview
How does it work? (simple explanation)

### User Flow
1. User does X
2. System shows Y
3. User clicks Z
4. ...

### Wireframes
(Link to designs or paste images)

## Technical Notes
Anything the dev team needs to know?

## Open Questions
| Question | Answer | Owner |
|----------|--------|-------|
| | | |

## Scope

### MVP (Must Have)
-

### Nice to Have
-

### Future
-

## Timeline
| Milestone | Target Date |
|-----------|-------------|
| Design complete | |
| Dev complete | |
| Launch | |

## Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| | | | |

## Success Criteria
How do we know this worked?

1.
2.
3.