# PRD — [Product / Feature Name]

> Template by Philip Scheer — philipscheer.github.io
> A PRD aligns product, engineering, design and business before anything is built. Keep it short enough to be read, complete enough to be argued with.

## 1. Problem & opportunity

What user/business problem are we solving? Evidence: data, research, support tickets, revenue impact. If you cannot quantify the problem, you are not ready to write the PRD.

## 2. Goals & success metrics

| Goal | Metric | Baseline | Target | When to evaluate |
|---|---|---|---|---|
| ... | ... | ... | ... | ... |

North-star connection: how does this move the product's core metric?

## 3. Users & jobs to be done

Who is this for? What job are they hiring the product to do? Include the anti-persona (who this is NOT for).

## 4. Scope

**In:** the smallest version that tests the hypothesis.
**Out (explicitly):** everything cut to ship sooner — with the reason.

## 5. User flows & requirements

For each flow: trigger → steps → outcome. Requirements as user stories with acceptance criteria (Given/When/Then). Mark each as Must / Should / Could.

## 6. Non-functional requirements

Performance, security, privacy/LGPD, accessibility, observability, cost. Link to the engineering `design.md` once it exists.

## 7. Dependencies & risks

Teams, systems, vendors, legal. For each risk: likelihood, impact, mitigation, owner.

## 8. Launch plan

Rollout strategy (flags, cohorts, %), communication, support readiness, kill criteria.

## 9. Measurement plan

Events to instrument BEFORE launch, dashboards, experiment design if A/B.

---

*Owner: ___ · Engineering counterpart: ___ · Design counterpart: ___ · Status: draft / review / approved · Last updated: ___*