breakdown-epic-pm
github/awesome-copilot
Generate detailed Epic Product Requirements Documents to guide technical architecture and engineering planning.
What is breakdown-epic-pm?
This skill acts as an expert Product Manager to translate high-level epic ideas into comprehensive, structured PRDs. Use it when you need to define the scope, requirements, and success metrics for a major feature or initiative before engineering begins.
- Generates complete Epic PRDs in Markdown format with standardized structure
- Captures functional and non-functional requirements from business perspective
- Defines user personas, journeys, and workflows for the epic
- Establishes success metrics and KPIs to measure epic outcomes
- Identifies scope boundaries and out-of-scope items to prevent scope creep
- Produces PRDs formatted for use as input to technical architecture specifications
How to install breakdown-epic-pm
npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-pmHow to use breakdown-epic-pm
- 1.Provide a high-level description of your epic idea to the skill
- 2.Answer any clarifying questions the skill asks about target users, problems, and scope
- 3.Review the generated PRD structure covering goal, personas, journeys, and requirements
- 4.Save the output PRD to `/docs/ways-of-work/plan/{epic-name}/epic.md`
- 5.Use the PRD as input for generating technical architecture specifications
Use cases
- Planning a major new feature or product capability for a SaaS platform
- Documenting business requirements before handing off to engineering teams
- Creating a single source of truth for cross-functional alignment on an epic
- Generating structured input for technical architecture specification generation
- Defining success criteria and metrics for large-scale initiatives
- Product Managers planning new epics or features
- Engineering leads needing clear business context before architecture design
- Technical leads translating business requirements into technical specifications
- Teams using structured PRD processes for large initiatives
breakdown-epic-pm FAQ
The skill will ask clarifying questions to ensure all aspects of the epic are well-defined before generating the PRD. You don't need to have everything figured out upfront.
This skill is designed specifically for Epic-level PRDs. For smaller features, you may want a more lightweight requirements process.
The output is a complete PRD in Markdown format, structured with sections for goal, personas, journeys, requirements, metrics, and scope.
The PRD serves as the single source of truth for engineering teams and is used as input to generate comprehensive technical architecture specifications for the epic.
Full instructions (SKILL.md)
Source of truth, from github/awesome-copilot.
name: breakdown-epic-pm description: 'Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.'
Epic Product Requirements Document (PRD) Prompt
Goal
Act as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to translate high-level ideas into detailed Epic-level Product Requirements Documents (PRDs). These PRDs will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical architecture specification for the epic.
Review the user's request for a new epic and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the epic are well-defined.
Output Format
The output should be a complete Epic PRD in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/epic.md.
PRD Structure
1. Epic Name
- A clear, concise, and descriptive name for the epic.
2. Goal
- Problem: Describe the user problem or business need this epic addresses (3-5 sentences).
- Solution: Explain how this epic solves the problem at a high level.
- Impact: What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, revenue)?
3. User Personas
- Describe the target user(s) for this epic.
4. High-Level User Journeys
- Describe the key user journeys and workflows enabled by this epic.
5. Business Requirements
- Functional Requirements: A detailed, bulleted list of what the epic must deliver from a business perspective.
- Non-Functional Requirements: A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).
6. Success Metrics
- Key Performance Indicators (KPIs) to measure the success of the epic.
7. Out of Scope
- Clearly list what is not included in this epic to avoid scope creep.
8. Business Value
- Estimate the business value (e.g., High, Medium, Low) with a brief justification.
Context Template
- Epic Idea: [A high-level description of the epic from the user]
- Target Users: [Optional: Any initial thoughts on who this is for]
Related skills
More from github/awesome-copilot and the wider catalog.
breakdown-feature-implementation
Generate detailed feature implementation plans aligned with Epoch monorepo structure and SaaS best practices.
breakdown-feature-prd
Generate detailed Product Requirements Documents for new features based on an Epic.
breakdown-plan
Generate comprehensive GitHub project plans with Epic > Feature > Story hierarchy, dependencies, and automated issue tracking.
breakdown-test
Generate comprehensive test strategies, task breakdowns, and QA plans using ISTQB and ISO 25010 frameworks for GitHub projects.
centos-linux-triage
Diagnose and fix CentOS issues with RHEL-compatible commands, SELinux, and firewalld guidance.
chrome-devtools
Expert browser automation, debugging, and performance analysis via Chrome DevTools MCP.