# PRD Template (Compass)

Use this template as the skeleton for any PRD generated by `/compass:prd`. Fill every section. **No code allowed anywhere in this document.**

---

```markdown
---
title: <Feature name>
version: v<X.Y>
status: <draft | review | approved>
po: <PO name>
team: <team>
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
target_release: <sprint / quarter>
related_idea: <path to IDEA file if any>
related_jira: <epic key if Jira enabled>
---

# PRD: <Feature name>

## 1. Summary

<2–3 sentences. What is this feature? Who is it for? Why now?>

## 2. Problem statement

### 2.1 What's the problem
<1 paragraph in plain language. Concrete enough that a stranger reading this would understand the user pain.>

### 2.2 Evidence
- <data point / quote / ticket count / NPS comment>
- <data point>
- <data point>

### 2.3 Cost of inaction
<What happens if we don't ship this? Be specific — lost revenue, churn, support burden, missed market window.>

## 3. Users

### 3.1 Primary user
- **Role / segment**: <description>
- **Context**: <when do they hit this problem?>
- **Frequency**: <daily / weekly / occasional>

### 3.2 Secondary users
<List or "none">

### 3.3 Out-of-scope users
<Who is NOT the target — to prevent scope creep>

## 4. Goals & Non-goals

### 4.1 Goals
1. <Measurable goal 1>
2. <Measurable goal 2>
3. <Measurable goal 3>

### 4.2 Non-goals
1. <Explicit non-goal 1>
2. <Explicit non-goal 2>
3. <Explicit non-goal 3>

## 5. Success metrics

### 5.1 Primary metric
**<Metric name>** — <definition>
- **Baseline today**: <value>
- **Target 30d**: <value>
- **Target 60d**: <value>
- **Target 90d**: <value>

### 5.2 Secondary metrics
- <Metric>: baseline <X> → target <Y>
- <Metric>: baseline <X> → target <Y>

### 5.3 Guardrail metrics (must NOT regress)
- <Metric>: must stay <above/below> <threshold>
- <Metric>: must stay <above/below> <threshold>

## 6. User experience

### 6.1 Happy path
1. User <action>
2. System <response>
3. User <action>
4. System <response>
5. <Continue until success state>

### 6.2 Edge cases
- **<Edge case 1>**: <expected behavior>
- **<Edge case 2>**: <expected behavior>

### 6.3 Error states
- **<Error 1>**: <message + recovery action>
- **<Error 2>**: <message + recovery action>

## 7. Scope

### 7.1 In scope (this release)
- <Capability 1>
- <Capability 2>
- <Capability 3>

### 7.2 Out of scope (defer to future)
- <Capability — reason for deferring>
- <Capability — reason for deferring>

## 8. Dependencies

- **<System / team / feature>**: <what we need from them>
- **<System / team / feature>**: <what we need from them>

## 9. Risks & mitigations

| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| <risk 1> | L/M/H | L/M/H | <how to reduce> |
| <risk 2> | L/M/H | L/M/H | <how to reduce> |

## 10. Open questions

| # | Question | Owner | Needed by |
|---|---|---|---|
| 1 | <question> | <stakeholder> | <date> |
| 2 | <question> | <stakeholder> | <date> |

## 11. Appendix

- **Related PRDs**: <links>
- **User research**: <links>
- **Competitor analysis**: <links>
- **Stakeholder feedback**: <summary>
```

---

## Rules for filling this template

1. **No code** — no `code blocks`, no SQL, no API signatures, no class names. Plain language only.
2. **No TBD without owner** — if a section needs data you don't have, write "TBD — needs <stakeholder>" not just "TBD".
3. **Measurable goals** — every goal must have a way to verify it's achieved.
4. **Symmetric goals/non-goals** — don't put the same item in both lists.
5. **Concrete user flows** — happy path should be 5–8 specific steps, not generic "user uses feature".