---
roadcrew_template_name: "prd.template.md"
roadcrew_template_type: "template"
roadcrew_template_version: "v1.0"
roadcrew_last_updated: "2025-01-25"
roadcrew_min_version: "1.5.0"
roadcrew_license: "Apache-2.0"
roadcrew_copyright: "Copyright (c) 2025 North Star Holdings, LLC"
spdx_license_identifier: "Apache-2.0"
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: ../specs/{{FEATURE_ID}}-spec.md
epic: {{EPIC_LINK}}
approvers: [{{APPROVER_1}}, {{APPROVER_2}}]
---
# 📝 {{FEATURE_NAME}} – Product Requirements Document {#prd-{{FEATURE_ID}}}

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

## 1. Business & User Goals

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

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

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

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

{{PROBLEM_STATEMENT}}

## 3. Success Metrics

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

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

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

## 4. Requirements

### 4.1 Functional Requirements (max 6, ≤15 words each)
- R1: {{REQUIREMENT_1}}
- R2: {{REQUIREMENT_2}}
- R3: {{REQUIREMENT_3}}
- R4: {{REQUIREMENT_4}}
- R5: {{REQUIREMENT_5}}
- R6: {{REQUIREMENT_6}}

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

### 4.3 Acceptance Criteria (product validation, ≤5, each ≤12 words)
- AC1: {{ACCEPTANCE_CRITERION_1}}
- AC2: {{ACCEPTANCE_CRITERION_2}}
- AC3: {{ACCEPTANCE_CRITERION_3}}
- AC4: {{ACCEPTANCE_CRITERION_4}}
- AC5: {{ACCEPTANCE_CRITERION_5}}

## 5. User Stories

| ID  | As a        | I want to          | So that I can         |
|-----|-------------|--------------------|-----------------------|
| US1 | {{ROLE_1}}  | {{ACTION_1}}       | {{BENEFIT_1}}         |
| US2 | {{ROLE_2}}  | {{ACTION_2}}       | {{BENEFIT_2}}         |
| US3 | {{ROLE_3}}  | {{ACTION_3}}       | {{BENEFIT_3}}         |

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

| Step | Action                       | Expected Result           |
|------|------------------------------|---------------------------|
| 1    | {{ACTION_1}}                 | {{RESULT_1}}              |
| 2    | {{ACTION_2}}                 | {{RESULT_2}}              |
| 3    | {{ACTION_3}}                 | {{RESULT_3}}              |
| 4    | {{ACTION_4}}                 | {{RESULT_4}}              |
| 5    | {{ACTION_5}}                 | {{RESULT_5}}              |

## 7. Non-Goals (within this release, ≤3, each ≤12 words)
- {{DEFERRED_1}}
- {{DEFERRED_2}}
- {{DEFERRED_3}}

## 8. Impact & Dependencies

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

## 9. Mapping to Spec

| Functional Requirement | Spec Section |
|-----------------------|--------------|
| R1: {{REQ_1_BRIEF}}   | 2.1.1        |
| R2: {{REQ_2_BRIEF}}   | 3.2          |
| R3: {{REQ_3_BRIEF}}   | 4.1          |
| R4: {{REQ_4_BRIEF}}   | 5.1          |
| R5: {{REQ_5_BRIEF}}   | 5.2          |
| R6: {{REQ_6_BRIEF}}   | 6.1          |

---

## Editor Instructions:
- Use bullets and tables exclusively; paragraphs only for Problem Statement (≤50 words).
- Each functional requirement (4.1) must map to spec section (9).
- Do not exceed length limits; AI and reviewers will reject oversized content.
- No implementation details—reference spec for all "how" questions.
- PRD answers "what/why", Spec answers "how".
- User stories and journeys provide context for spec issue breakdown.

<!--
DOWNSTREAM TEMPLATE MAPPING:

spec.template.md requirements:
- Section 1 (PRD → Spec Mapping) uses this PRD's section 9
- Functional requirements map 1:1 to spec section 2.1
- Non-functional constraints map to spec section 2.2
- User stories guide spec issue breakdown (section 8)
- Acceptance criteria inform spec acceptance criteria

release.template.md requirements:
- Business objectives → Release overview (Target State)
- Success metrics → Release criteria

epic.template.md requirements:
- User goals → Epic overview and key goals
- User journey → Epic child issue sequencing
-->