| name | analyst-prd-template |
| description | PRD (Product Requirements Document) template for the temper-analyst agent. Contains the full 10-section PRD structure generated during Phase 1.7, including header metadata, all required sections, and the scope rule note. Load when generating or validating Docs/Functional-Analysis/PRD.md files.
|
PRD Template
Use this exact structure when generating Docs/Functional-Analysis/PRD.md in Phase 1.7.
# Product Requirements Document — [Project Name]
> Generated by TemperAI — temper-analyst (Phase 1: Functional Analysis)
> Date: [YYYY-MM-DD]
> Version: [YYYYMMDD-HHMM]
> Status: Pending approval
---
## 1. Project Summary
[2–3 paragraphs. What the system is, the context in which it operates,
and the value it delivers to its users.]
## 2. Problem Statement
[The specific problem this system solves. Not the solution — the problem.
Who is affected, how, and what the consequence of not solving it is.]
## 3. User Roles and Personas
[Every role that interacts with the system.]
- **[Role name]**: [Who they are, what they need, what success looks like for them]
## 4. Functional Scope
**Users should be able to:**
- [Role]: [Functional capability — action + object + context if needed]
**Functional constraints (what users explicitly cannot do):**
- [Role]: [Cannot do X — functional reason, e.g., "cannot delete products, only deactivate them"]
> **Scope rule:** Only the capabilities listed above will be implemented.
> Anything not listed is OUT OF SCOPE for this version.
## 5. Business Rules
- BR-001: [Rule description]
- BR-002: [Rule description]
## 6. Status Workflows
[Entities with lifecycle states. If none, state "None."]
**[Entity name]:**
[Status A] → [Status B] → [Status C]
- Transition rules: [e.g., "Only Pending orders can be cancelled"]
## 7. External Integrations
[Third-party systems from a functional perspective. If none, state "None."]
- [Service name]: [What it does from the user's perspective]
## 8. Future Scope
[Entire features or modules explicitly deferred to future versions.
Not functional constraints — those belong in Section 4.]
- [Feature or module]: [Reason for deferral or target version]
## 9. Open Questions
[Only include items the stakeholder explicitly confirmed as unknown for now or explicitly deferred.]
- **[Business uncertainty]**: [Question — stakeholder explicitly said they genuinely do not know yet]
- **[Deferred decision]**: [Question — stakeholder explicitly said it will be decided later and is out of current scope]
> No blocking functional ambiguity may remain in this section at Phase 1 completion.
## 10. Analyst Sign-off
Analysis completed by: temper-analyst (Phase 1: Functional Analysis)
Completeness checklist: [All items validated ✓]
PRD version: [YYYYMMDD-HHMM]
Scope rule
Scope rule: Only the capabilities in Section 4 (Functional Scope) will be implemented.
Anything not listed is OUT OF SCOPE for this version. This applies to all downstream agents
(architect, tasks, backend, frontend, tester).
