SkillHub

Skills github awesome-copilot

Epic breakdown workflow Bundle of 6 skills

Use it when:
You want a product idea taken through requirements, architecture and planning documents before anyone writes code.
It does:
Runs six prompts in order, each written for a role: epic PRD, epic architecture, feature PRD, implementation plan, GitHub project plan, test plan.
You get:
Markdown files under /docs/ways-of-work/plan/{epic-name}/: epic.md and arch.md, then a folder per feature for its PRD, plans and test documents.
Gaps:
The last two steps look for the feature PRD at {feature-name}.md rather than the prd.md the PRD step writes, and for a technical-breakdown.md no step writes.
Assumes:
TypeScript, Next.js, Turborepo, tRPC, Stack Auth, shadcn/ui and Docker, in the architecture and implementation steps.
Output:
Documents only: GitHub issues are drafted in the project and test plans, not filed.

TL;DR

Six prompts that hand documents down a chain, each played by a role from product manager to QA engineer, all saved under /docs/ways-of-work/plan/{epic-name}/. breakdown-epic-pm turns an epic idea into epic.md: problem, personas, user journeys, requirements, KPIs, what's out of scope and business value, asking questions when the idea is thin. breakdown-epic-arch writes arch.md beside it: a layered Mermaid system diagram, the features and technical enablers, the stack, technical value and a T-shirt size. breakdown-feature-prd takes one feature or enabler of the epic and writes its PRD, with user stories and acceptance criteria, in the feature's own folder. breakdown-feature-implementation turns that PRD into implementation-plan.md: architecture and entity-relationship diagrams, API design and a frontend component tree. breakdown-plan then drafts the GitHub work, an Epic > Feature > Story/Enabler > Task hierarchy with issue templates, priorities, estimates and dependencies, in project-plan.md and issues-checklist.md, and breakdown-test adds a test strategy, test issue checklist and QA plan built on ISTQB test techniques and the ISO 25010 quality model. Those last two expect files the earlier steps don't write at those paths, so point them at yours. The first four also work alone, from an idea or a PRD you supply.

Summarizes the repo at 797337f.

Any agent, with the skills CLI

npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-pm --skill breakdown-epic-arch --skill breakdown-feature-prd --skill breakdown-feature-implementation --skill breakdown-plan --skill breakdown-test

GitHub CLI 2.90.0 or later, one skill per command, as the repo's skills list gives them

gh skills install github/awesome-copilot breakdown-epic-pm && gh skills install github/awesome-copilot breakdown-epic-arch && gh skills install github/awesome-copilot breakdown-feature-prd && gh skills install github/awesome-copilot breakdown-feature-implementation && gh skills install github/awesome-copilot breakdown-plan && gh skills install github/awesome-copilot breakdown-test

GitHub Copilot CLI plugin: only the first four steps, with 4 more of the repo's planning skills and 7 agents

copilot plugin install project-planning@awesome-copilot

Source on GitHubAll skills from github/awesome-copilot

Total Downloads
10,100 of breakdown-feature-prd, its most installed skill, on skills.sh, Nov 9, 2026
Repo stars
40,943 github/awesome-copilot
First seen
Feb 25, 2026 on skills.sh, its first skill

Its skills, in the order they're used

The ones marked “Only in the bundle” need the rest of it. The others also work alone.

  1. breakdown-epic-pm

    9.1K total downloads

    Writes an Epic product requirements document from your idea: problem, personas, user journeys, requirements, success metrics, out-of-scope items and business value.

  2. breakdown-epic-arch

    9K total downloads

    Turns an Epic PRD into an architecture spec: a Mermaid system diagram, features and technical enablers, stack, technical value and a T-shirt size estimate.

  3. breakdown-feature-prd

    10.1K total downloads

    Writes a product requirements document for one feature of an epic: problem, personas, user stories, requirements, acceptance criteria and what's out of scope.

  4. breakdown-feature-implementation

    9.2K total downloads

    Writes a technical implementation plan for a feature from its PRD: Mermaid architecture and database diagrams, API design, frontend components and state.

  5. breakdown-plan

    Only in the bundle 9.3K total downloads

    Turns a feature's PRD and implementation plan into a GitHub project plan: issue drafts for epics, features, stories and enablers, with estimates and dependencies.

    Reads the implementation-plan.md that breakdown-feature-implementation writes, with the feature PRD and a technical-breakdown.md, from /docs/ways-of-work/plan/. It looks for the PRD at {epic-name}/{feature-name}.md, not the {feature-name}/prd.md breakdown-feature-prd writes, and no step writes technical-breakdown.md.

  6. breakdown-test

    Only in the bundle 9.3K total downloads

    Writes a feature's test strategy, test issue checklist and QA plan, applying ISTQB test design techniques and the ISO 25010 quality model.

    Reads the project-plan.md that breakdown-plan writes, plus the same feature PRD, technical breakdown and implementation plan, with the same two path gaps: the PRD at {feature-name}.md and a technical-breakdown.md no step writes.