CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.
$ npx skills add github/awesome-copilot --skill breakdown-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot breakdown-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/breakdown-plan .claude/skills/breakdown-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .claude/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/breakdown-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill breakdown-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot breakdown-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/breakdown-plan .agents/skills/breakdown-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .agents/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill breakdown-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot breakdown-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/breakdown-plan .cursor/skills/breakdown-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .cursor/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/breakdown-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill breakdown-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot breakdown-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/breakdown-plan .gemini/skills/breakdown-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .gemini/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot breakdown-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill breakdown-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/breakdown-plan .github/skills/breakdown-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .github/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill breakdown-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot breakdown-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/breakdown-plan .opencode/skills/breakdown-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "breakdown-plan" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/breakdown-plan into .opencode/skills/breakdown-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "breakdown-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
breakdown-planIssue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.
Breakdown Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management. It works with GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, mermaid and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Breakdown Plan loads about 3.8k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 921 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 921 words, ~3,763 tokens.
.claude/skills/breakdown-plan/SKILL.md (or your agent's skills folder).Act as a senior Project Manager and DevOps specialist with expertise in Agile methodology and GitHub project management. Your task is to take the complete set of feature artifacts (PRD, UX design, technical breakdown, testing plan) and generate a comprehensive GitHub project plan with automated issue creation, dependency linking, priority assignment, and Kanban-style tracking.
Before using this prompt, ensure you have the complete testing workflow artifacts:
/docs/ways-of-work/plan/{epic-name}/{feature-name}.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.mdplan-test prompt for comprehensive test strategy, quality assurance planning, and test issue creationplan-epic-arch prompt for system architecture and technical designplan-feature-prd prompt for detailed feature requirements and specificationsCreate two primary deliverables:
/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.mdgraph TD
A[Epic: {Epic Name}] --> B[Feature: {Feature Name}]
B --> C[Story 1: {User Story}]
B --> D[Story 2: {User Story}]
B --> E[Enabler 1: {Technical Work}]
B --> F[Enabler 2: {Infrastructure}]
C --> G[Task: Frontend Implementation]
C --> H[Task: API Integration]
C --> I[Test: E2E Scenarios]
D --> J[Task: Component Development]
D --> K[Task: State Management]
D --> L[Test: Unit Tests]
E --> M[Task: Database Schema]
E --> N[Task: Migration Scripts]
F --> O[Task: CI/CD Pipeline]
F --> P[Task: Monitoring Setup]# Epic: {Epic Name}
## Epic Description
{Epic summary from PRD}
## Business Value
- **Primary Goal**: {Main business objective}
- **Success Metrics**: {KPIs and measurable outcomes}
- **User Impact**: {How users will benefit}
## Epic Acceptance Criteria
- [ ] {High-level requirement 1}
- [ ] {High-level requirement 2}
- [ ] {High-level requirement 3}
## Features in this Epic
- [ ] #{feature-issue-number} - {Feature Name}
## Definition of Done
- [ ] All feature stories completed
- [ ] End-to-end testing passed
- [ ] Performance benchmarks met
- [ ] Documentation updated
- [ ] User acceptance testing completed
## Labels
`epic`, `{priority-level}`, `{value-tier}`
## Milestone
{Release version/date}
## Estimate
{Epic-level t-shirt size: XS, S, M, L, XL, XXL}# Feature: {Feature Name}
## Feature Description
{Feature summary from PRD}
## User Stories in this Feature
- [ ] #{story-issue-number} - {User Story Title}
- [ ] #{story-issue-number} - {User Story Title}
## Technical Enablers
- [ ] #{enabler-issue-number} - {Enabler Title}
- [ ] #{enabler-issue-number} - {Enabler Title}
## Dependencies
**Blocks**: {List of issues this feature blocks}
**Blocked by**: {List of issues blocking this feature}
## Acceptance Criteria
- [ ] {Feature-level requirement 1}
- [ ] {Feature-level requirement 2}
## Definition of Done
- [ ] All user stories delivered
- [ ] Technical enablers completed
- [ ] Integration testing passed
- [ ] UX review approved
- [ ] Performance testing completed
## Labels
`feature`, `{priority-level}`, `{value-tier}`, `{component-name}`
## Epic
#{epic-issue-number}
## Estimate
{Story points or t-shirt size}# User Story: {Story Title}
## Story Statement
As a **{user type}**, I want **{goal}** so that **{benefit}**.
## Acceptance Criteria
- [ ] {Specific testable requirement 1}
- [ ] {Specific testable requirement 2}
- [ ] {Specific testable requirement 3}
## Technical Tasks
- [ ] #{task-issue-number} - {Implementation task}
- [ ] #{task-issue-number} - {Integration task}
## Testing Requirements
- [ ] #{test-issue-number} - {Test implementation}
## Dependencies
**Blocked by**: {Dependencies that must be completed first}
## Definition of Done
- [ ] Acceptance criteria met
- [ ] Code review approved
- [ ] Unit tests written and passing
- [ ] Integration tests passing
- [ ] UX design implemented
- [ ] Accessibility requirements met
## Labels
`user-story`, `{priority-level}`, `frontend/backend/fullstack`, `{component-name}`
## Feature
#{feature-issue-number}
## Estimate
{Story points: 1, 2, 3, 5, 8}# Technical Enabler: {Enabler Title}
## Enabler Description
{Technical work required to support user stories}
## Technical Requirements
- [ ] {Technical requirement 1}
- [ ] {Technical requirement 2}
## Implementation Tasks
- [ ] #{task-issue-number} - {Implementation detail}
- [ ] #{task-issue-number} - {Infrastructure setup}
## User Stories Enabled
This enabler supports:
- #{story-issue-number} - {Story title}
- #{story-issue-number} - {Story title}
## Acceptance Criteria
- [ ] {Technical validation 1}
- [ ] {Technical validation 2}
- [ ] Performance benchmarks met
## Definition of Done
- [ ] Implementation completed
- [ ] Unit tests written
- [ ] Integration tests passing
- [ ] Documentation updated
- [ ] Code review approved
## Labels
`enabler`, `{priority-level}`, `infrastructure/api/database`, `{component-name}`
## Feature
#{feature-issue-number}
## Estimate
{Story points or effort estimate}| Priority | Value | Criteria | Labels |
|---|---|---|---|
| P0 | High | Critical path, blocking release | priority-critical, value-high |
| P1 | High | Core functionality, user-facing | priority-high, value-high |
| P1 | Medium | Core functionality, internal | priority-high, value-medium |
| P2 | Medium | Important but not blocking | priority-medium, value-medium |
| P3 | Low | Nice to have, technical debt | priority-low, value-low |
graph LR
A[Epic Planning] --> B[Feature Definition]
B --> C[Enabler Implementation]
C --> D[Story Development]
D --> E[Testing Execution]
E --> F[Feature Delivery]
G[Infrastructure Setup] --> C
H[API Design] --> D
I[Database Schema] --> C
J[Authentication] --> D## Sprint {N} Goal
**Primary Objective**: {Main deliverable for this sprint}
**Stories in Sprint**:
- #{issue} - {Story title} ({points} pts)
- #{issue} - {Story title} ({points} pts)
**Total Commitment**: {points} story points
**Success Criteria**: {Measurable outcomes}name: Create Feature Issues
on:
workflow_dispatch:
inputs:
feature_name:
description: 'Feature name'
required: true
epic_issue:
description: 'Epic issue number'
required: true
jobs:
create-issues:
runs-on: ubuntu-latest
steps:
- name: Create Feature Issue
uses: actions/github-script@v7
with:
script: |
const { data: epic } = await github.rest.issues.get({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: ${{ github.event.inputs.epic_issue }}
});
const featureIssue = await github.rest.issues.create({
owner: context.repo.owner,
repo: context.repo.repo,
title: `Feature: ${{ github.event.inputs.feature_name }}`,
body: `# Feature: ${{ github.event.inputs.feature_name }}\n\n...`,
labels: ['feature', 'priority-medium'],
milestone: epic.data.milestone?.number
});name: Update Issue Status
on:
pull_request:
types: [opened, closed]
jobs:
update-status:
runs-on: ubuntu-latest
steps:
- name: Move to In Review
if: github.event.action == 'opened'
uses: actions/github-script@v7
# Move related issues to "In Review" column
- name: Move to Done
if: github.event.action == 'closed' && github.event.pull_request.merged
uses: actions/github-script@v7
# Move related issues to "Done" columnepic, priority, value, and team labels/docs/ways-of-work/plan/{epic-name}/{feature-name}/issues-checklist.mdThis comprehensive GitHub project management approach ensures complete traceability from epic-level planning down to individual implementation tasks, with automated tracking and clear accountability for all team members.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/breakdown-plan of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Breakdown Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Breakdown Plan this skillgithub/awesome-copilot | 40k | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Project Managerpwrdrvr/openclaw-codex-app-server | 265 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Find Project Anomaliespenpot/penpot | 61k | — | ~1.2k | Automated safety check: Pass | MPL-2.0 | |
| PublishQ00/ouroboros | 6.2k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Gh Read Inspectoreclipse-rdf4j/rdf4j | 420 | — | ~950 | Automated safety check: Pass | BSD-3-Clause |
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
pwrdrvr/openclaw-codex-app-server
Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.
penpot/penpot
Check a GitHub milestone against the Main project board, report the five anomaly types to tmp/<MILESTONE-ANOMALIES.md, and fix missing milestone assignments on request.
Q00/ouroboros
Publish Seed specification as GitHub Issues for team-based project management
eclipse-rdf4j/rdf4j
Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.
ruvnet/agentic-flow
Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Works with
Categories
Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking. Breakdown Plan is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Issue Planning and Automation prompt that generates comprehensive project plans with Epic Feature Story/Enabler Test hierarchy, dependencies, priorities, and automated tracking.
Breakdown Plan fits situations like: tasks that involve Project management.
Run `npx skills add github/awesome-copilot --skill breakdown-plan -a claude-code`. Or copy the skill folder (skills/breakdown-plan in github/awesome-copilot) into .claude/skills/breakdown-plan in your project. Claude Code loads it when a task matches its description.
Run `npx skills add github/awesome-copilot --skill breakdown-plan -a codex`. Or copy the skill folder (skills/breakdown-plan in github/awesome-copilot) into .agents/skills/breakdown-plan in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill breakdown-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/breakdown-plan, .gemini/skills/breakdown-plan, .github/skills/breakdown-plan and .opencode/skills/breakdown-plan in your project.
SKILL.md names no scripts, command-line tools or credentials: Breakdown Plan is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Breakdown Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Breakdown Plan: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Manager (pwrdrvr/openclaw-codex-app-server, 265 stars), Find Project Anomalies (penpot/penpot, 61k stars) and Publish (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.