Claude Code PM (CCPM)

What it does

• Five-phase discipline: brainstorm to PRD (.claude/prds/), PRD to epic with task files (10 or fewer per epic by default), GitHub sync, parallel execution, script-based tracking
• GitHub native: epic issue plus sub-issues, local task files renamed to match issue numbers, a dedicated ../epic-<name>/ worktree per epic
• Tasks carry depends_on / parallel / conflicts_with metadata; parallel streams run simultaneously in one worktree and agents coordinate through Git
• Tracking runs as bash scripts (status, standup, next, blocked — 14 of them): instant output, zero LLM token cost

When to use it

Solo founders or small teams shipping features end to end with traceability: every line of code traces back through PRD, epic, task, issue, to commit. Also fits teams already living in GitHub Issues — no new PM tool, progress visible in issue comments. Following the Agent Skills standard, the same skill serves Claude Code and non-Anthropic harnesses alike.

Getting started

It is a standard Agent Skill — clone the repo and point your harness at skill/ccpm/:

git clone https://github.com/automazeio/ccpm.git
ln -s /path/to/ccpm/skill/ccpm .claude/skills/ccpm

Prerequisites: git, an authenticated gh CLI (gh auth login), and a GitHub repository for the project.

Things to know

Proper parent-child issue relationships need the gh-sub-issue extension (gh extension install yahsan2/gh-sub-issue); without it CCPM falls back to task lists. The repo has been quiet — last push March 2026 per the GitHub API (checked 2026-10-17). The eval badges ("100% vs 27.7%") are the project's own structured evals, not an independent benchmark. The original /pm:* slash-command system is preserved on the v1 branch.