skill GitHub Copilot
official · GitHub
Open on GitHub
breakdown-epic-pm — GitHub Copilot skill for Epic PRDs
Creates an Epic PRD for a new initiative and saves it as Markdown. Use it when a product idea needs clear requirements before technical architecture work.
Install into GitHub Copilot · Skills CLI (Vercel)
All methods and platforms ↓
npx skills add github/awesome-copilot --skill breakdown-epic-pmWhat breakdown-epic-pm does
This skill reviews a request for a new epic from a product manager’s perspective. When the brief lacks detail, it asks follow-up questions before drafting the Epic PRD.
The document covers the problem, proposed solution, expected impact, user personas, journeys, business requirements, quality constraints, KPIs, scope exclusions and business value. It writes the result to /docs/ways-of-work/plan/{epic-name}/epic.md.
Install it if your team wants PRDs in this structure before creating an architecture specification. It is too heavyweight for a small task without an epic.
What it helps with
- turn a new epic idea into a PRD
- ask for missing product context
- define personas and user journeys
- list functional and non-functional requirements
- record scope exclusions and success metrics
Example prompts for the agent
- "Create an Epic PRD for an epic where users manage their subscription."
- "Ask what context is missing for this new epic, then write the PRD."
- "Define user journeys, KPIs, and Out of Scope for this epic."
How to install breakdown-epic-pm
1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill breakdown-epic-pm2GitHub CLI
gh skill install github/awesome-copilot breakdown-epic-pm3Manually: put the files in place
.github/skills/breakdown-epic-pm/SKILL.md1Skills CLI (Vercel)
npx skills add github/awesome-copilot --skill breakdown-epic-pm -a claude-code2Manually: put the files in place
~/.claude/skills/breakdown-epic-pm/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/breakdown-epic-pm/
Manually: put the files in place
.agents/skills/breakdown-epic-pm/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/breakdown-epic-pm/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
Platform CLI
gemini skills install https://github.com/github/awesome-copilot --path skills/breakdown-epic-pmManually: put the files in place
.devin/skills/breakdown-epic-pm/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set554
The whole set →
git-commit
official This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits.
GitHub Copilot
47,165installs
excalidraw-diagram-generator
official Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities.
GitHub Copilot
31,639installs
multi-stage-dockerfile
official This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies.
GitHub Copilot
29,688installs
documentation-writer
official Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing.
GitHub Copilot
27,757installs
prd
official Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one.
GitHub Copilot
24,035installs
refactor
official This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells.
GitHub Copilot
22,321installs
java-springboot
official Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code.
GitHub Copilot
21,272installs
create-readme
official This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code.
GitHub Copilot
19,081installs
Similar
define-goal
official Shapes vague requests into concrete, measurable goals with explicit pass criteria before an agent starts working.
Claude Code CX Codex Cursor +1
2,800installs
standup
official Generates daily standup updates by pulling recent commits and ticket changes, or by formatting rough notes into yesterday, today, and blockers.
Claude Code CX Codex Cursor +1
5,200installs
configure
official Checks iMessage channel setup in Claude Code and audits access rules. Use it when messages fail to reach the assistant or to see which contacts are allowed.
Claude Code
3,861installs
find-skills Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project.
Claude Code CX Codex Cursor +1
4,000,000installs
grill-me grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts.
Claude Code
1,424,476installs
grill-with-docs This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition.
Claude Code
1,219,756installs
handoff Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent.
Claude Code
1,038,491installs
grilling Stress-test a plan, decision, or idea through structured rounds of questions. Use it when you need to expose assumptions before acting.
Claude Code
979,543installs
Questions about breakdown-epic-pm
How do I install breakdown-epic-pm in GitHub Copilot?
Run npx skills add github/awesome-copilot --skill breakdown-epic-pm. You can also use gh skill install github/awesome-copilot breakdown-epic-pm.
What does breakdown-epic-pm do?
It turns a new epic request into a structured Epic PRD. The skill asks clarifying questions when needed and writes the result in Markdown.
Where does breakdown-epic-pm save the PRD?
It saves the document at /docs/ways-of-work/plan/{epic-name}/epic.md. The PRD includes requirements, metrics, user journeys, and scope boundaries.
Source text
SKILL.md · MIT
---
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]
© github · MIT · github/awesome-copilot
