feat: Oracle CRM Page, Synthetic Client Data and Live Snapshot when hitting emotion hotpoint
This commit is contained in:
105
.Agent Context/Sprint 1/Templates/02 - PRD Template.md
Normal file
105
.Agent Context/Sprint 1/Templates/02 - PRD Template.md
Normal file
@@ -0,0 +1,105 @@
|
||||
# Product Requirements Document (PRD)_ [System or Workstream Name]
|
||||
|
||||
**Date:** [YYYY-MM-DD]
|
||||
**Status:** [Draft | In Review | Approved]
|
||||
**Owner:** [Name]
|
||||
**Reviewers:** [Names]
|
||||
**Scope:** [Product slice or release boundary]
|
||||
**Purpose:** Define the product intent, value, scope, and release criteria for the target system.
|
||||
|
||||
## 1. Purpose
|
||||
|
||||
State what product problem this work solves and why it exists now.
|
||||
|
||||
## 2. Background
|
||||
|
||||
Describe:
|
||||
|
||||
- current product state
|
||||
- why existing flows are insufficient
|
||||
- what changed to make this work necessary
|
||||
|
||||
## 3. Problem Statement
|
||||
|
||||
Define the concrete product and operator pain points.
|
||||
|
||||
## 4. Product Goal
|
||||
|
||||
Define the primary product goal in one paragraph.
|
||||
|
||||
## 5. Target Users and Stakeholders
|
||||
|
||||
List:
|
||||
|
||||
- primary users
|
||||
- internal operators
|
||||
- reviewers or approvers
|
||||
- sales or demo stakeholders
|
||||
|
||||
## 6. In-Scope Outcomes
|
||||
|
||||
State the capabilities that must exist in the release.
|
||||
|
||||
## 7. Out-of-Scope Items
|
||||
|
||||
State what this release will explicitly not solve.
|
||||
|
||||
## 8. Product Experience
|
||||
|
||||
Describe what the user or operator should see and do from start to finish.
|
||||
|
||||
## 9. Functional Requirements
|
||||
|
||||
For each functional requirement, state:
|
||||
|
||||
- requirement ID
|
||||
- description
|
||||
- rationale
|
||||
- acceptance signal
|
||||
|
||||
## 10. System Behavior
|
||||
|
||||
Describe:
|
||||
|
||||
- happy path
|
||||
- failure path
|
||||
- approval path
|
||||
- audit path
|
||||
|
||||
## 11. Success Metrics
|
||||
|
||||
Define measurable product outcomes such as:
|
||||
|
||||
- completion rate
|
||||
- operator effort reduction
|
||||
- citation coverage
|
||||
- mission latency
|
||||
- demo success rate
|
||||
|
||||
## 12. Risks
|
||||
|
||||
List product, technical, governance, and adoption risks.
|
||||
|
||||
## 13. Release Plan
|
||||
|
||||
Describe:
|
||||
|
||||
- release phases
|
||||
- feature gating
|
||||
- assisted mode vs autonomous mode
|
||||
|
||||
## 14. Sales Readiness
|
||||
|
||||
Define what must be true for this work to be demo-safe and commercially useful.
|
||||
|
||||
## 15. Dependencies
|
||||
|
||||
List upstream systems, teams, or documents this PRD depends on.
|
||||
|
||||
## 16. Acceptance Criteria
|
||||
|
||||
State the release-level acceptance criteria.
|
||||
|
||||
## 17. Bottom Line
|
||||
|
||||
Summarize the product decision in plain language.
|
||||
Reference in New Issue
Block a user