breakdown-epic-pm Skill for Claude Code: Write an Epic Product Requirements Document

Turns a high-level epic idea into a full product requirements document, saved as a markdown file in your repo.

Installs: 9.1K; on skills.sh
Stars: 40.7K; on GitHub
Updated: Oct 2026; last repo commit

breakdown-epic-pm makes the agent act as a product manager for a large SaaS platform. You describe an epic, and it writes an Epic PRD with 8 sections and saves it to /docs/ways-of-work/plan/{epic-name}/epic.md.

If your request lacks detail, the agent asks clarifying questions first. The PRD is meant to feed a technical architecture specification, and the same project-planning plugin lists a breakdown-epic-arch skill. The skill is one text file and bundles no scripts.

Good for

Product managers turning an epic idea into a PRD
Engineering leads who need a PRD as input for an architecture spec
Founders scoping a large feature before work is split up

Install breakdown-epic-pm

Claude Code

1
Download the skill folder from https://github.com/github/awesome-copilot/tree/HEAD/skills/breakdown-epic-pm.
2
Put it at ~/.claude/skills/breakdown-epic-pm/ so that SKILL.md sits directly inside.
3
Start a new session; the skill loads when its description matches the task.

Built from the package data we hold. Not yet tested by us.

What's in the skill

When it loads

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.

Sections in SKILL.md

Goal
Output Format
PRD Structure
Context Template

Key facts

Author: Awesome Copilot Community (project-planning plugin.json author)
License: MIT (repo LICENSE, Copyright GitHub, Inc.)
Installs on skills.sh: 9,080 (Nov 2, 2026)
GitHub stars: 40,666 for the github/awesome-copilot repo (Nov 2, 2026)
Last commit: Oct 30, 2026
Files: 1 file: SKILL.md; no scripts
Output: /docs/ways-of-work/plan/{epic-name}/epic.md
Plugin: Part of the project-planning Copilot plugin (8 skills, 7 agents)

What it includes

Takes your epic idea and optional target users; asks if details are missing
The context template has two inputs, Epic Idea and Target Users (optional).
Try: “Write an epic PRD for in-app team invitations”
Gather the epic idea
A clear, concise name for the epic
First of the 8 PRD sections.
1. Epic Name
Problem, solution and expected impact
The problem takes 3 to 5 sentences; impact names outcomes or metrics to improve.
2. Goal
Target users and the key user journeys the epic enables
Sections 3 and 4 of the PRD.
3 to 4. Personas and journeys
Functional and non-functional requirements
Non-functional examples: performance, security, accessibility and data privacy.
5. Business requirements
KPIs, out-of-scope list and a High, Medium or Low business value with reason
Out of Scope exists to prevent scope creep.
6 to 8. Metrics, scope, value
Writes epic.md under /docs/ways-of-work/plan/{epic-name}/
The output path is set in SKILL.md.
Write · Save the PRD

From the official docs

Permissions

Low risk

The skill writes one markdown file in your repository. The Copilot plugin route adds 7 agents, some of which can create GitHub issues and run terminal commands, so inspect them before installing.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

The plugin route adds agents that can edit and post
project-planning lists 7 agents. The prd agent lists create_issue, update_issue and add_issue_comment among its tools, and implementation-plan lists terminal and editing tools. Install only the skill if you do not want agents. github.com
It writes a file in your docs folder
The PRD goes to /docs/ways-of-work/plan/{epic-name}/epic.md. Check the path before you let it save. github.com

Technical details

Scopes	Writes /docs/ways-of-work/plan/{epic-name}/epic.md

Questions

What does breakdown-epic-pm do?

It writes an Epic Product Requirements Document from your epic idea. The PRD has 8 sections, from the name and goal to success metrics, scope limits and business value.

Where does it save the file?

SKILL.md says to save it to /docs/ways-of-work/plan/{epic-name}/epic.md in your repository.

How do I install breakdown-epic-pm?

Use the install box above. For Claude Code, copy the skill folder or use the skills CLI. The Copilot CLI tab installs the project-planning plugin, which has 8 skills and 7 agents.

What comes after the PRD?

SKILL.md says the PRD is input for a technical architecture specification. The project-planning plugin lists a breakdown-epic-arch skill for that, which is a separate skill.

Will it ask me questions?

Yes, if the request lacks information. SKILL.md says to ask clarifying questions so every aspect of the epic is defined.

Is it safe?

The skill bundles no scripts and writes one markdown file in your repo. The plugin route is bigger: its 7 agents list tools such as creating GitHub issues, editing files and running terminal commands, so inspect them first.

Information

updated Nov 2, 2026

Repository: github/awesome-copilot
Folder: skills/breakdown-epic-pm

github/awesome-copilot skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 4

github.com · github.com
github.com · github.com
github.com · github.com
github.com · github.com