breakdown-plan Skill for Claude: GitHub Project Plans and Issues

Makes Claude turn a feature spec into a GitHub project plan: epics, stories, priorities, dependencies and an issue checklist.

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

This skill makes Claude act as a project manager. It reads your feature PRD (/docs/ways-of-work/plan/{epic-name}/{feature-name}.md), technical breakdown and implementation plan, then writes two files in /docs/ways-of-work/plan/{epic-name}/{feature-name}/: project-plan.md and issues-checklist.md.

The plan covers an Epic > Feature > Story/Enabler > Test hierarchy, issue templates, a priority and value matrix, estimates, dependencies, sprint planning, a Kanban board layout and two sample GitHub Actions workflows. It bundles no scripts, and SKILL.md names no API key. It expects those input documents to exist, so write them first.

Good for

Project managers and tech leads planning a feature on GitHub
Teams that track work as GitHub issues and a project board
Developers who already have a PRD and technical breakdown on file

Install breakdown-plan

Claude Code

Copy this prompt.

Install the breakdown-plan skill in Claude Code. Run this command:

npx skills add https://github.com/github/awesome-copilot --skill breakdown-plan

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.

Sections in SKILL.md

Goal
GitHub Project Management Best Practices
Agile Work Item Hierarchy
Project Management Principles
Input Requirements
Core Feature Documents
Related Planning Prompts
Output Format
Project Plan Structure
Epic Description
Business Value
Epic Acceptance Criteria
Features in this Epic
Definition of Done
Labels
Milestone

Key facts

Listed in: github/awesome-copilot (the README says its contents come from third-party developers)
Repo: github/awesome-copilot
Installs on skills.sh: 9,300 (Nov 2, 2026)
GitHub stars: 40,666 (Nov 2, 2026)
License: MIT (repo license)
Last repo commit: Oct 30, 2026
What installs: 1 file: SKILL.md, no scripts
Writes: project-plan.md and issues-checklist.md in /docs/ways-of-work/plan/{epic-name}/{feature-name}/

What it includes

Feature PRD, technical breakdown and implementation plan under /docs/ways-of-work/plan
Three markdown files per feature. SKILL.md names the related prompts plan-feature-prd, plan-epic-arch and plan-test as places to get them.
Files · Inputs it expects
Project plan with hierarchy, issue templates, estimates, dependencies and board setup
Nine parts: overview, work item hierarchy, issue breakdown, priority and value matrix, estimation, dependencies, sprint planning, project board configuration and automation.
Write · project-plan.md
Checklist for creating epic, feature, story and enabler issues
Grouped by pre-creation preparation, epic-level, feature-level and story/enabler-level issues.
Write · issues-checklist.md
Four templates: Epic, Feature, User Story and Technical Enabler
Each has a description, acceptance criteria, a definition of done, labels and an estimate.
Issue templates
Six Kanban columns and two sample GitHub Actions workflows
Columns are Backlog, Sprint Ready, In Progress, In Review, Testing and Done. The workflows create feature issues on demand and move issues when pull requests open or close.
Board and automation

From the official docs

Questions

What does breakdown-plan do?

It turns your feature documents into a GitHub project plan and an issue checklist, with an Epic > Feature > Story/Enabler > Test hierarchy, priorities, estimates and dependencies.

How do I install it in Claude Code?

Use the install box at the top of the page. No plugin in the awesome-copilot repo lists this skill, so the box installs the skill folder on its own.

What do I need before I run it?

A feature PRD at /docs/ways-of-work/plan/{epic-name}/{feature-name}.md, plus technical-breakdown.md and implementation-plan.md in /docs/ways-of-work/plan/{epic-name}/{feature-name}/. SKILL.md points to the plan-feature-prd, plan-epic-arch and plan-test prompts for related planning.

Does it create GitHub issues for me?

It writes a project plan and a checklist of issues to create. It also includes two sample GitHub Actions workflows that create issues and move them across a board. Those are sample YAML inside the plan; adding them to your repository is up to you.

How does it relate to breakdown-test?

breakdown-test lists the project-plan.md that this skill writes as one of its inputs. Run breakdown-plan first, then breakdown-test.

Is it safe?

It bundles no scripts, only a SKILL.md. It writes two markdown files in /docs/ways-of-work/plan/{epic-name}/{feature-name}/, so work in a repository where that is fine. The plan includes sample workflow YAML; adding it to your repository is up to you. The awesome-copilot README asks you to inspect third-party items before installing.

Information

updated Nov 2, 2026

Repository: github/awesome-copilot
Folder: skills/breakdown-plan

github/awesome-copilot skills.sh

Sources

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

Show all 3

SKILL.md · github.com
awesome-copilot README · github.com
breakdown-test SKILL.md · github.com