Skills github awesome-copilot Epic breakdown workflow
breakdown-epic-pm
- Use it when:
- You have a high-level idea for an epic and want it written up as a product requirements document before any architecture or code.
- You get:
- A Markdown PRD saved at /docs/ways-of-work/plan/{epic-name}/epic.md.
- It does:
- Plays a SaaS product manager, asks clarifying questions when details are missing, and fills an eight-section template.
- Unlike prd:
- That one interviews you for a five-section feature PRD; this one works at epic level and starts the breakdown chain.
- Next step:
- breakdown-epic-arch turns the PRD into a technical architecture spec.
Skill 1 of 6 in the Epic breakdown workflow bundle, before breakdown-epic-arch.
TL;DR
The first step of the repo's breakdown workflow, which takes a product idea from epic down to tests. The agent acts as the product manager of a large SaaS platform: it reads your epic idea and, optionally, who it's for, asks clarifying questions if something is missing, and writes a PRD in eight sections. They are the epic's name; its goal, as the problem in three to five sentences, the solution and the expected impact on metrics; user personas; high-level user journeys; functional and non-functional business requirements; KPIs; what's out of scope; and a business value of high, medium or low with a justification. The file goes in a folder named after the epic, which the later breakdown skills write into: breakdown-epic-arch puts arch.md next to it, and breakdown-feature-prd writes each feature's PRD in a subfolder.
Summarizes the skill at 797337f.
npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-pm skills.sh pageSource on GitHubAll skills from github/awesome-copilot
- Total Downloads
- 9,100 on skills.sh, Nov 9, 2026
- Repo stars
- 40,943 github/awesome-copilot
- First seen
- Feb 25, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 12 |
| Sep 28 | 18 |
| Oct 5 | 17 |
| Oct 12 | 1 |
| Oct 19 | 6 |
| Oct 26 | 5 |
| Nov 2 | 2 |
| Nov 9 | 9 |
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics |
SKILL.md
From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.
Frontmatter
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]