# PRD — [Project name]

> The one file you paste into every AI session before asking for code.
> Template from [vibeprompt.tech](https://vibeprompt.tech) — keep it under 2 pages.

## Target user

One real person, one real situation.

> _Example: a freelance designer with 3–5 active clients who loses track of which
> feedback thread belongs to which project._

[Who is this for? Be specific. Avoid "developers" or "small businesses".]

## Goal

What the product does in one sentence.

> _Example: A minimal client portal where freelancers collect and track feedback
> from all clients in one place._

[One sentence. If you need two, you haven't decided yet.]

## Why

Why this matters to ship.

[Who benefits? What metric improves? What problem does it solve that nothing
else solves well?]

## What — MVP features (max 5)

If your list has 12, that's a roadmap. Cut to 5.

1. [Feature 1]
2. [Feature 2]
3. [Feature 3]
4. [Feature 4]
5. [Feature 5]

## Out of scope (at least 3 explicit exclusions)

Without this, every feature you didn't mention becomes a maybe.

- No [feature you might be tempted to add]
- No [another tempting one]
- No [a third]

## Success criteria

Testable conditions. Not "auth works", but specific enough that a new dev could
verify it on a fresh machine.

- A new user signs up, verifies email, and reaches the dashboard in under 60 seconds without errors
- [Criterion 2]
- [Criterion 3]

## Constraints

- Stack: [from your TechDesign.md]
- Time budget: [e.g. ship in 4 weeks]
- Quality bar: [e.g. zero `any`, all routes typed, secrets audited]

## Open questions

- [Anything you genuinely don't know yet — flag for next session]

---

_Save as `docs/PRD.md`. Reference from `AGENTS.md`. Paste the relevant section
into every AI session before asking for code._