# Product Requirements Document

> Filled out by `/requirements` in Init Mode, or manually before the first `/requirements` run. Keep every section concrete enough that a stranger could read it and know what NOT to build.

## Vision
_2-3 sentences: what is this product, who is it for, why does it need to exist. Not a feature list — the problem it solves._

## Target Users
_Name the actual user type(s), not "everyone". For each: their concrete pain point today, and what they're using instead of this product._

## Core Features (Roadmap)

| Priority | Feature | Status |
|----------|---------|--------|
| P0 (MVP) | _Feature 1_ | Planned |
| P0 (MVP) | _Feature 2_ | Planned |
| P1 | _Feature 3_ | Planned |
| P2 | _Feature 4_ | Planned |

P0 = cannot ship without it. P1 = next after MVP validates. P2 = explicitly deferred, not "maybe never."

## Success Metrics
_Concrete, measurable, with a number or threshold — not "users are happy". E.g. "50 signups in first month", "task completion rate > 80%"._

## Constraints
_Real limits that shape decisions: timeline, budget, team size, must-run-on-existing-server, no third-party SaaS dependencies, etc._

## Non-Goals
_Explicitly out of scope for this version — the things people will ask for that you're deliberately not building yet, and why._

---

Use `/requirements` to create detailed feature specifications for each item in the roadmap above.