1---2name: breakdown-epic-pm-23description: Create an Epic Product Requirements Document (PRD) from a high-level epic idea, including goal, personas, journeys, business requirements, success metrics, scope boundaries, and business value. Use when asked to write an epic PRD or docs/ways-of-work epic.md.4---56# Epic PRD78Transform a high-level product idea into a well-defined Epic-level Product Requirements Document for a large-scale SaaS platform that becomes the source of truth for engineering and the input for the technical architecture specification.910## When to invoke1112- "Create an Epic PRD for this idea."13- "Write `/docs/ways-of-work/plan/{epic-name}/epic.md`."14- "Turn this concept into an epic product requirements document."15- "Define personas, journeys, requirements, metrics, and scope for this epic."1617## Product context1819| Input | How to use it |20| --- | --- |21| Epic Idea | Convert the high-level description into a named epic, problem, solution, and impact. |22| Target Users | Use provided users; if absent, infer likely personas and label them as assumptions. |23| Large-scale SaaS platform | Consider multi-tenant behavior, self-service journeys, operations, security, and scale. |24| Architecture handoff | Write enough product detail for a technical architecture specification to be generated next. |2526If information is missing and no interaction is possible, include assumptions and open questions in the PRD rather than inventing certainty.2728## PRD structure2930| Section | Required content | Quality bar |31| --- | --- | --- |32| Epic Name | Clear, concise, descriptive epic name. | Names the business capability, not an implementation detail. |33| Goal | Problem, Solution, and Impact. | Problem is 3-5 sentences; Impact names expected outcomes such as user engagement, conversion rate, or revenue. |34| User Personas | Target users. | Includes goals, jobs-to-be-done, pain points, and permissions when known. |35| High-Level User Journeys | Key workflows enabled by the epic. | Covers primary happy paths and important alternate paths. |36| Business Requirements | Functional Requirements and Non-Functional Requirements. | Functional requirements describe what the epic must deliver from a business perspective. |37| Success Metrics | KPIs that measure success. | Metrics have directionality and, when known, target thresholds. |38| Out of Scope | Explicit exclusions. | Prevents scope creep and names deferred work. |39| Business Value | High, Medium, or Low with justification. | Ties value to users, revenue, risk reduction, efficiency, or strategic need. |4041## Requirement and metric rules4243| Artifact | Include | Avoid |44| --- | --- | --- |45| Functional Requirements | User capabilities, workflow outcomes, policy rules, reporting needs, integrations. | Implementation tasks such as table names or framework choices unless product-facing. |46| Non-Functional Requirements | Performance, security, accessibility, data privacy, reliability, compliance, supportability. | Generic statements such as "fast" or "secure" with no observable signal. |47| Success Metrics | Activation, adoption, conversion, retention, time saved, error reduction, revenue, support ticket reduction. | Metrics with no owner or no way to observe them. |48| Out of Scope | Features, platforms, personas, migrations, or integrations intentionally excluded. | Ambiguous "later" items that engineering may accidentally include. |4950## Output template5152```markdown53# <Epic Name> PRD5455## 1. Epic Name56<clear epic name>5758## 2. Goal59**Problem:** <3-5 sentences describing the user problem or business need>60**Solution:** <high-level solution>61**Impact:** <expected outcomes or metrics such as user engagement, conversion rate, or revenue>6263## 3. User Personas64- <persona>: <goal, context, and pain point>6566## 4. High-Level User Journeys67- <journey name>: <steps and outcome>6869## 5. Business Requirements70### Functional Requirements71- <business capability or behavior>7273### Non-Functional Requirements74- <performance, security, accessibility, data privacy, reliability, or compliance constraint>7576## 6. Success Metrics77| Metric | Direction | Target or signal |78| --- | --- | --- |79| <KPI> | increase/decrease/maintain | <target or observable signal> |8081## 7. Out of Scope82- <excluded work>8384## 8. Business Value85**Value:** High | Medium | Low86**Justification:** <business rationale>8788## Assumptions and open questions89- <only when needed>90```9192## Quality gate9394- [ ] The output is suitable for `/docs/ways-of-work/plan/{epic-name}/epic.md`.95- [ ] Epic Name, Goal, User Personas, High-Level User Journeys, Business Requirements, Success Metrics, Out of Scope, and Business Value are present.96- [ ] Problem, Solution, and Impact are all explicit.97- [ ] Functional and Non-Functional Requirements are business-focused, specific, and testable.98- [ ] Success Metrics are measurable KPIs with directionality.99- [ ] Out of Scope prevents scope creep.100- [ ] Business Value is High, Medium, or Low with justification.
paulasilvatech