curl -fsSL https://api.cheatcodehq.com/install.sh | sh -s -- ccpm --to allCopies 1 skill into each app's skills folder (Claude Code: ~/.claude/skills), after checking every file against automazeio/ccpm at commit 7d7e462. Nothing else on your computer changes. To undo it, run the terminal command with --uninstall at the end; that also removes what the app added.
Then start a new session in your AI app and ask for the work in plain words; it picks the skill from its description. In Claude Code you can also type /ccpm:ccpm.
See it in use
After installing, start a new session and say: Use the ccpm skill to write a PRD for this feature from my meeting notes.
What else it can do, and its limits
- One skill for the whole path: PRD, technical epic, task breakdown, GitHub issues, standups and status
- Keeps PRDs and epics as files in a .claude folder of your project; in this recording it saved to prds/ because that folder could not be written
- Syncing to GitHub issues needs the GitHub CLI and your GitHub account
- Running work in parallel uses git worktrees and several agents, which needs a code project and a terminal
- Status, standup and what is blocked come from bash scripts in the package
Sample input Recorded Oct 26, 2026 in Claude Code 2.1.308 with Sonnet 5.5. The video replays that session; nothing in it was acted or edited.
What's inside 1 skill
ccpmCCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.
CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.
About
Something wrong with this listing, or it did not install? Tell us