# [Your App Name]

<!-- PRD Template by Sinter (https://getsinter.dev)
     Ship your next SaaS without rebuilding auth, payments, and infrastructure
     from scratch. Sinter is a production-ready Next.js starter designed for
     Claude Code. Go from idea to live product with confidence.

     How to use this template:
     1. Co-create your product spec with your AI tool of choice.
        Ask it to walk you through each section and shape the plan together.
     2. If using Sinter + Claude Code, save this to docs/prd/ and run /bootstrap
        to auto-generate a roadmap and GitHub issues from your answers. -->

## Problem Statement

<!-- What problem are you solving? Be specific about who has it and why it matters. -->

### The Problem

### Who Has This Problem

### Why It Matters Now

---

## Target Users

<!-- Who is this for? Specific enough to make decisions. -->

### Primary User

**Who:**
**Context:** <!-- When/where do they experience the problem? -->
**Current solution:** <!-- How do they solve it today? -->

### Secondary Users (optional)

### Anti-Personas (optional)

<!-- Explicitly exclude users to prevent scope creep. -->

---

## Vision

<!-- One paragraph: what are you building and why? If using Sinter's /bootstrap command,
     this becomes the opening of your GitHub Epic. Make it clear and compelling. -->

---

## Features

<!-- List each feature with a name and 1-2 sentence description.
     Each feature should be a buildable unit of work.

     Format: ### Feature name, then description underneath.
     Include acceptance criteria as checkboxes when you can. -->

### [Feature Name]

[What this feature does and why it matters.]

**Acceptance Criteria:**

- [ ] [Specific, testable criterion]
- [ ] [Another criterion]

### [Another Feature Name]

[Description]

**Acceptance Criteria:**

- [ ] [Criterion]

---

## Scope and Constraints

### In Scope (MVP)

<!-- What you ARE building in the first version. -->

-
-

### Out of Scope (Not MVP)

<!-- What you are NOT building yet. Prevents scope creep. -->

-
-

### Hard Constraints

<!-- Non-negotiable technical or business requirements. -->

| Constraint | Reason |
| ---------- | ------ |
|            |        |

---

## Phases

<!-- Group features into build phases. Name each phase and list which features belong to it. -->

### Phase 1: [Name]

<!-- What goes first and why. Usually the data model and core infrastructure. -->

Features in this phase:

-
-

### Phase 2: [Name]

<!-- The main build. Core UI and business logic. -->

Features in this phase:

-
-

### Phase 3: [Name]

<!-- Polish, edge cases, deployment. -->

Features in this phase:

-
-

---

## Success Criteria

### Ship When

<!-- What must be true before you can deploy? -->

- [ ]
- [ ]

### Success Metrics (optional)

| Metric | Target | How to Measure |
| ------ | ------ | -------------- |
|        |        |                |

---

## Technical Requirements (optional)

<!-- Include this when you have specific technical decisions or constraints. -->

### Tech Stack

- **Additional services:**
- **External APIs:**

### Data Model

<!-- Key entities and their relationships. Even a rough sketch helps. -->

```text
Entity: [Name]
- field_name: type
- field_name: type
- relationship: belongs_to [Other Entity]
```

### API Endpoints (optional)

| Endpoint | Method | Purpose |
| -------- | ------ | ------- |
|          |        |         |

---

## Dependencies (optional)

<!-- External services, setup steps, or prerequisites that must be in place before building. -->

-
-

---

## Design Direction (optional)

<!-- Visual and interaction guidelines. -->

-
-

---

## Risks and Mitigations (optional)

| Risk | Likelihood | Impact | Mitigation |
| ---- | ---------- | ------ | ---------- |
|      | Low/Med/High | Low/Med/High | |

---

## Open Questions (optional)

<!-- Unresolved decisions. Track them here, resolve before or during build. -->

| Question | Options | Decision | Date |
| -------- | ------- | -------- | ---- |
|          |         | Pending  |      |