1---2name: breakdown-epic-pm-33description: 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<!-- Generated from harness/github-copilot/plugins/project-planning/skills/breakdown-epic-pm/SKILL.md by harness/claude-code/scripts/convert_from_copilot.py. Edit the source, not this file. -->78# Epic PRD910Transform 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.1112## When to invoke1314- "Create an Epic PRD for this idea."15- "Write `/docs/ways-of-work/plan/{epic-name}/epic.md`."16- "Turn this concept into an epic product requirements document."17- "Define personas, journeys, requirements, metrics, and scope for this epic."1819## Product context2021| Input | How to use it |22| --- | --- |23| Epic Idea | Convert the high-level description into a named epic, problem, solution, and impact. |24| Target Users | Use provided users; if absent, infer likely personas and label them as assumptions. |25| Large-scale SaaS platform | Consider multi-tenant behavior, self-service journeys, operations, security, and scale. |26| Architecture handoff | Write enough product detail for a technical architecture specification to be generated next. |2728If information is missing and no interaction is possible, include assumptions and open questions in the PRD rather than inventing certainty.2930## PRD structure3132| Section | Required content | Quality bar |33| --- | --- | --- |34| Epic Name | Clear, concise, descriptive epic name. | Names the business capability, not an implementation detail. |35| Goal | Problem, Solution, and Impact. | Problem is 3-5 sentences; Impact names expected outcomes such as user engagement, conversion rate, or revenue. |36| User Personas | Target users. | Includes goals, jobs-to-be-done, pain points, and permissions when known. |37| High-Level User Journeys | Key workflows enabled by the epic. | Covers primary happy paths and important alternate paths. |38| Business Requirements | Functional Requirements and Non-Functional Requirements. | Functional requirements describe what the epic must deliver from a business perspective. |39| Success Metrics | KPIs that measure success. | Metrics have directionality and, when known, target thresholds. |40| Out of Scope | Explicit exclusions. | Prevents scope creep and names deferred work. |41| Business Value | High, Medium, or Low with justification. | Ties value to users, revenue, risk reduction, efficiency, or strategic need. |4243## Requirement and metric rules4445| Artifact | Include | Avoid |46| --- | --- | --- |47| Functional Requirements | User capabilities, workflow outcomes, policy rules, reporting needs, integrations. | Implementation tasks such as table names or framework choices unless product-facing. |48| Non-Functional Requirements | Performance, security, accessibility, data privacy, reliability, compliance, supportability. | Generic statements such as "fast" or "secure" with no observable signal. |49| Success Metrics | Activation, adoption, conversion, retention, time saved, error reduction, revenue, support ticket reduction. | Metrics with no owner or no way to observe them. |50| Out of Scope | Features, platforms, personas, migrations, or integrations intentionally excluded. | Ambiguous "later" items that engineering may accidentally include. |5152## Output template5354```markdown55# <Epic Name> PRD5657## 1. Epic Name58<clear epic name>5960## 2. Goal61**Problem:** <3-5 sentences describing the user problem or business need>62**Solution:** <high-level solution>63**Impact:** <expected outcomes or metrics such as user engagement, conversion rate, or revenue>6465## 3. User Personas66- <persona>: <goal, context, and pain point>6768## 4. High-Level User Journeys69- <journey name>: <steps and outcome>7071## 5. Business Requirements72### Functional Requirements73- <business capability or behavior>7475### Non-Functional Requirements76- <performance, security, accessibility, data privacy, reliability, or compliance constraint>7778## 6. Success Metrics79| Metric | Direction | Target or signal |80| --- | --- | --- |81| <KPI> | increase/decrease/maintain | <target or observable signal> |8283## 7. Out of Scope84- <excluded work>8586## 8. Business Value87**Value:** High | Medium | Low88**Justification:** <business rationale>8990## Assumptions and open questions91- <only when needed>92```9394## Quality gate9596- [ ] The output is suitable for `/docs/ways-of-work/plan/{epic-name}/epic.md`.97- [ ] Epic Name, Goal, User Personas, High-Level User Journeys, Business Requirements, Success Metrics, Out of Scope, and Business Value are present.98- [ ] Problem, Solution, and Impact are all explicit.99- [ ] Functional and Non-Functional Requirements are business-focused, specific, and testable.100- [ ] Success Metrics are measurable KPIs with directionality.101- [ ] Out of Scope prevents scope creep.102- [ ] Business Value is High, Medium, or Low with justification.
paulasilvatech