CCPM is a project-management system for coding agents that turns product requirements into PRDs, GitHub issues, and parallel implementation work using Git worktrees. It is for teams that want written specifications, traceable progress, and multiple agents working on separate tasks.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add automazeio/ccpm --skill ccpmgit clone --depth 1 https://github.com/automazeio/ccpmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/automazeio/ccpm/ccpm)<a href="https://agentmods.dev/skills/automazeio/ccpm/ccpm"><img src="https://agentmods.dev/badge/skills/automazeio/ccpm/ccpm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/automazeio/ccpm/ccpm"><img src="https://agentmods.dev/badge/skills/automazeio/ccpm/ccpm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00219 | $0.01071 |
| Opus 5.5 | $0.00088 | $0.00428 |
| Sonnet 5.5 | $0.00044 | $0.00214 |
| Haiku 4.5 | $0.00022 | $0.00107 |
Grade A, and why
ccpm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCPM - Claude Code Project Manager
A spec-driven development workflow: PRD → Epic → GitHub Issues → Parallel Agents → 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.
The Five Phases
1. Plan — Capture requirements
When: User wants to define a new feature, product requirement, or scope of work.
Read: references/plan.md
Covers: Writing PRDs through guided brainstorming, converting PRDs to technical epics.
2. Structure — Break it down
When: An epic exists and needs to be decomposed into concrete tasks.
Read: references/structure.md
Covers: Epic decomposition into numbered task files with dependencies and parallelization.
3. Sync — Push to GitHub
When: Local epic/tasks need to become GitHub issues, progress needs to be posted as comments, or a bug is found and needs a linked issue created.
Read: references/sync.md
Covers: Epic sync (epic + tasks → GitHub issues), issue sync (progress comments), closing issues/epics, bug reporting against completed issues.
4. Execute — Start building
When: User wants to start working on one or more GitHub issues with parallel agents.
Read: references/execute.md
Covers: Issue analysis (parallel work stream identification), launching parallel agents, coordinating worktrees.
5. Track — Know where things stand
When: User asks for status, standup report, what's blocked, what's next, or needs to validate state.
Read: references/track.md
Covers: Status, standup, search, in-progress, next priority, blocked items, validation.
Script-First Rule
For deterministic operations — anything that reads and reports without needing reasoning — always run the bash script directly rather than doing the work manually:
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/conventions.md 4.4 KB
- references/execute.md 6.2 KB
- references/plan.md 3.0 KB
- references/scripts/blocked.sh 1.7 KB runs code
- references/scripts/epic-list.sh 2.5 KB runs code
- references/scripts/epic-show.sh 2.4 KB runs code
- references/scripts/epic-status.sh 2.2 KB runs code
- references/scripts/help.sh 3.1 KB runs code
- references/scripts/in-progress.sh 2.1 KB runs code
- references/scripts/init.sh 6.0 KB runs code
- references/scripts/next.sh 1.7 KB runs code
- references/scripts/prd-list.sh 2.7 KB runs code
- references/scripts/prd-status.sh 1.7 KB runs code
- references/scripts/search.sh 1.6 KB runs code
- references/scripts/standup.sh 3.0 KB runs code
- references/scripts/status.sh 1.0 KB runs code
- references/scripts/validate.sh 2.6 KB runs code
- references/structure.md 2.9 KB
- references/sync.md 7.5 KB
- references/track.md 3.2 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 83 lines · 219 tokens per session scan A d56605fcdba0
ccpm is a skill published in the GitHub repository automazeio/ccpm (8,411 stars, last pushed yesterday), licensed MIT. It adds 219 tokens to every session and 1,071 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.