<!-- @template-name: Users/samhenry/tailwind-ai-workspace/roadcrew/templates/prd-example.md @version: 1.0.0 @release-date: 2025-10-25 -->
---
type: prd
feature: {{FEATURE_NAME}}
feature_id: {{FEATURE_ID}}
status: {{STATUS}}              # Draft | Review | Approved | Implemented
version: {{VERSION}}
created: {{CREATED_DATE}}
updated: {{UPDATED_DATE}}
related_spec: ../memory-bank/requirements/specs/{{FEATURE_ID}}-spec.md
epic: {{EPIC_LINK}}
approvers: [{{NAME}}, ...]
---

# 📝 {{FEATURE_NAME}} – Product Requirements Document {#prd-{{FEATURE_ID}}}

> This document defines **what** will be delivered and **why**. The technical implementation is documented in the spec.

## 1. Business & User Goals

### 1.1 Business Objectives (≤3, each ≤15 words)
- {{OBJECTIVE_1}}
- {{OBJECTIVE_2}}

### 1.2 User Goals (≤4, each ≤15 words)
- {{USER_GOAL_1}}
- {{USER_GOAL_2}}

### 1.3 Non-Goals / Out of Scope (≤3, each ≤12 words)
- {{NON_GOAL_1}}
- {{NON_GOAL_2}}

## 2. Problem Statement (≤40 words)
> Concise summary of the user/business need and context.

## 3. Success Metrics

### 3.1 User Metrics (1–2, ≤15 words each)
- {{USER_METRIC_1}}

### 3.2 Business Metrics (1–2, ≤15 words each)
- {{BUSINESS_METRIC_1}}

### 3.3 Technical Metrics (1–2, ≤15 words each)
- {{TECH_METRIC_1}}

## 4. Requirements

### 4.1 Functional Requirements (max 6, ≤15 words each)
- R1: {{REQUIREMENT_1}}
- R2: {{REQUIREMENT_2}}

### 4.2 Non-Functional Constraints (≤4, ≤15 words each)
- {{NFR_1}}
- {{NFR_2}}

### 4.3 Acceptance Criteria (for product validation, ≤12 words each)
- AC1: {{ACCEPTANCE_CRITERION_1}}
- AC2: {{ACCEPTANCE_CRITERION_2}}

## 5. User Stories

| ID  | As a   | I want to             | So that I can           |
|-----|--------|-----------------------|-------------------------|
| US1 | {{ROLE}} | {{ACTION}}            | {{BENEFIT}}             |
| US2 |        |                       |                         |
| ... |        |                       |                         |

## 6. User Journey (≤5 steps, ≤15 words each)

| Step | Action                       | Expected Result           |
|------|------------------------------|---------------------------|
| 1    | {{ACTION}}                   | {{RESULT}}                |
| 2    |                              |                           |

## 7. Non-Goals (Within This Release, ≤3)
- {{DELAYER_1}}
- {{DELAYER_2}}

## 8. Impact & Dependencies

- **Affected Systems:** {{AFFECTED_SYSTEMS}}
- **Dependencies:** {{DEPENDENCIES}}
- **Risks:** {{RISKS}}
- **Related Links:** {{RELATED_LINKS}}

## 9. Mapping to Spec

| Functional Requirement | Spec Section |
|-----------------------|--------------|
| R1                    | 2.1.1        |
| R2                    | 3.2          |
| ...                   | ...          |

---

**Editor Instructions:**  
- Use bullets and tables, never paragraphs, except for Problem Statement.  
- Each requirement must have a corresponding mapping to the spec.  
- Do not exceed section or line limits; AI and reviewers will reject oversize input.  
- No implementation details allowed—reference the spec for all "how".