CCPM skill
A spec-driven delivery skill: PRDs, epics, tasks, GitHub Issues sync and parallel agents in git worktrees
- 8,445 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Creates, comments on and closes GitHub issues via the gh CLI
- Makes commits, sets up git worktrees and runs bash scripts
- Launches parallel agents that modify the project's code
Install
- Works in
Manual install
git clone https://github.com/automazeio/ccpm.git
ln -s /path/to/ccpm/skill/ccpm .claude/skills/ccpmReplace /path/to/ccpm with the path to the cloned repository.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Creates, comments on and closes GitHub issues via the gh CLI
- Makes commits, sets up git worktrees and runs bash scripts
- Launches parallel agents that modify the project's code
This is third-party code. Review the repository files before installing.
What it does
CCPM gives the agent a spec-to-code discipline. An idea becomes a PRD through guided questioning, the PRD becomes a technical epic, and the epic decomposes into numbered tasks with dependencies and parallel flags. Tasks sync to GitHub Issues, where comments become the progress log, and each epic gets its own git worktree in which several agents run independent work streams. For standups, status, next and blocked items the skill runs ready bash scripts instead of gathering data by hand. It activates on natural phrases such as plan this, break down the epic, sync to GitHub or start issue N, with no special syntax.
Who it is for. For developers and leads who run spec-driven development and want task traceability in GitHub.
Good fit when
- You need to turn a feature idea into a PRD and a technical epic
- You need to split an epic into tasks and open them as GitHub Issues
- You need to run several work streams in parallel in a separate worktree
- You need a standup or status summary straight from project files
Not a fit when
- You need a one-off fix or debugging without tracking tasks and specs
- The project is not on GitHub and you do not plan to open issues there
Example request
Draft a PRD for a notification system, then break the epic into tasks and sync it to GitHubLimitations
The full workflow targets GitHub: it needs the git and gh CLIs installed and authenticated and a project repository. The skill creates and closes issues, posts comments, makes commits and sets up git worktrees, so it acts on the state of the project and the remote repository. By default an epic holds no more than ten tasks.
How to disable. Remove the ccpm symlink or folder from the skills directory, for example .claude/skills/ccpm.
FAQ
Is GitHub required?
Task sync and the work log rely on GitHub Issues, so the full workflow needs a repository and the gh CLI. PRD and epic planning can also be kept locally in project files.
Which agents does it work with?
CCPM is packaged as an Agent Skill and works in skill-capable harnesses: Claude Code, Codex, OpenCode, Amp, Cursor and others. Point the agent at the skill/ccpm folder.
Discussion
No questions or reviews yet.
Related
SkillsA scaffold for Claude Code and Codex: tasks in files, developer and QA roles, manual approval and shared state.
A set of 58 commands for product managers in Claude Code, Codex and Cursor: from an idea and a PRD to launch and growth analysis
A task manager for AI-driven development: breaks a PRD into dependent tasks and guides the agent through them via MCP or CLI
A skill that cross-examines a plan before work starts: numbered questions in rounds with a recommended answer and no changes until you confirm
A product management skill library for agents: product phases, sprints, templates and sample outputs
Four skills for a person with several AI assistants: a task register, evidence-based acceptance, beginner instructions
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| CCPM (this card) | no | 8,445 | |
| Goal Workflow | no | 300 | 19 skills for Claude Code |
| AI Product Development Toolkit | no | 1,055 | a skill set for Claude Code and Codex |
| Spec-Driven Develop | no | 993 | a plugin with three skills for large development work |
README in short
The README describes CCPM as a spec-driven delivery system where every line of code traces back to a requirement. The workflow has five phases: plan, document, decompose, execute and track, with GitHub Issues as the source of truth. It explains parallel execution: one issue is split into streams handled by different agents in a shared git worktree while the main conversation stays clean. Installation comes down to pointing the harness at the skill/ccpm folder; the dependencies are the git and gh CLIs. The project now ships as an Agent Skill and runs in harnesses compatible with the agentskills.io standard.
README badge
Original SKILL.md
--- name: ccpm description: "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, parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub, starting work on an issue, analyzing parallel work streams, running standups, checking status, closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context." --- # CCPM - Claude Code Project Manager A spec-driven development workflow: PRD to Epic to GitHub Issues to Parallel Agents to Shipped Code. ## Core Philosophy Requirements live in files, not heads. Every feature starts as a PRD, becomes a technical epic, decomposes into GitHub issues, and gets executed by parallel agents with full traceability. ## File Conventions Before doing anything, read `references/conventions.md` for path standards, frontmatter schemas, and GitHub operation rules. These apply to all phases.