# Product Requirements Document (PRD)

> Template for defining product requirements. Fill in each section.

---

## 📋 Overview

**Product Name:** [Name]
**Version:** 1.0 (MVP)
**Author:** [Your Name]
**Last Updated:** [Date]

---

## 🎯 Problem Statement

### The Problem
[Describe the specific problem users face. Be concrete, not abstract.]

### Current Solutions
[How do users solve this today? What's wrong with current solutions?]

### Our Approach
[How does our solution address the problem differently/better?]

---

## 👤 Target User

### Primary User Persona

**Name:** [e.g., "Busy Founder Fiona"]
**Role:** [e.g., Solo founder, early-stage startup]
**Goals:**
- [Goal 1]
- [Goal 2]

**Pain Points:**
- [Pain 1]
- [Pain 2]

**Tech Savviness:** [Low / Medium / High]

### User Needs (Jobs to be Done)
| Need | Priority | How We Address |
|------|----------|----------------|
| [Need 1] | P0 | [Solution] |
| [Need 2] | P0 | [Solution] |
| [Need 3] | P1 | [Solution] |

---

## ✨ Features

### MVP Features (P0 - Must Have)

#### Feature 1: [Name]
**Description:** [What it does]
**User Story:** As a [user], I want [action] so that [benefit].
**Acceptance Criteria:**
- [ ] [Criteria 1]
- [ ] [Criteria 2]
- [ ] [Criteria 3]

#### Feature 2: [Name]
**Description:** [What it does]
**User Story:** As a [user], I want [action] so that [benefit].
**Acceptance Criteria:**
- [ ] [Criteria 1]
- [ ] [Criteria 2]

#### Feature 3: [Name]
**Description:** [What it does]
**User Story:** As a [user], I want [action] so that [benefit].
**Acceptance Criteria:**
- [ ] [Criteria 1]
- [ ] [Criteria 2]

---

### Post-MVP Features (P1 - Nice to Have)

| Feature | Description | Priority |
|---------|-------------|----------|
| [Feature A] | [Description] | P1 |
| [Feature B] | [Description] | P1 |
| [Feature C] | [Description] | P2 |

---

## 🚫 Explicitly Out of Scope

These are NOT in v1.0:
- [Feature X] - Reason: [Why not now]
- [Feature Y] - Reason: [Why not now]
- [Feature Z] - Reason: [Why not now]

---

## 📊 Success Metrics

### Primary Metrics
| Metric | Target | How Measured |
|--------|--------|--------------|
| [e.g., Sign-ups] | [e.g., 100 in first month] | [Analytics tool] |
| [e.g., Retention] | [e.g., 40% week 1] | [Analytics tool] |

### Secondary Metrics
| Metric | Target | How Measured |
|--------|--------|--------------|
| [e.g., Task completion] | [e.g., 80%] | [Event tracking] |

---

## 🔧 Technical Considerations

### Tech Stack
| Component | Technology | Rationale |
|-----------|------------|-----------|
| Frontend | [e.g., Next.js] | [Why] |
| Backend | [e.g., Supabase] | [Why] |
| Database | [e.g., PostgreSQL] | [Why] |
| Auth | [e.g., Supabase Auth] | [Why] |
| Hosting | [e.g., Vercel] | [Why] |

### Constraints
- [Constraint 1: e.g., Must work on mobile]
- [Constraint 2: e.g., Must load in < 3 seconds]

### Dependencies
- [Dependency 1: e.g., Stripe for payments (if needed)]
- [Dependency 2]

---

## 📅 Timeline

| Phase | Duration | Deliverable |
|-------|----------|-------------|
| Discovery | [1-2 days] | Problem/user validated |
| Design | [2-3 days] | Wireframes + flows |
| Development | [1-2 weeks] | Working MVP |
| Testing | [2-3 days] | Bug fixes |
| Launch | [1 day] | Live product |

**Target Launch Date:** [Date]

---

## ❓ Open Questions

- [ ] [Question 1?]
- [ ] [Question 2?]
- [ ] [Question 3?]

---

## 📎 Appendix

### Related Documents
- [User Stories](/docs/user-stories.md)
- [Database Schema](/docs/database-schema.md)
- [API Contracts](/docs/api-contracts.md)

### References
- [Link 1]
- [Link 2]

---

*Template from Thinking in Systems framework*