Skip to content

CCPM Project Manager

Runs spec-driven delivery: PRDs, epics, GitHub issues, and parallel agent work tracking

Repository
automazeio/ccpm
Stars
8,425
Licence
MIT
Files
15 files

What it does

This skill teaches an AI agent a project-management workflow for shipping software features. You describe a feature, and the agent helps write a requirements document (PRD), turn it into a technical epic, split it into tasks, and sync those tasks to GitHub issues. It can also run small read-only status scripts that list epics, show what is in progress, next, or blocked, and summarise progress from local files stored under .claude/epics.

Great for

  • Developers who plan features in files and want tracked GitHub issues for each task
  • Small teams running parallel work streams on one repository who want status reports from local epic files

Skip it if

  • Debugging code, writing tests, or reviewing pull requests, which the skill says it should not handle (the agent may trigger it wrongly if the wording is vague)
  • Users without GitHub or a Git repository, since the sync and issue steps depend on GitHub

Try asking

  • “write a PRD for a user login feature”
  • “break down the login epic into tasks”
  • “what's blocked right now?”
  • “start working on issue 42”
Step-by-step guide: how to use CCPM Project ManagerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 15 original files, the MIT licence and an attribution note.

    ccpm.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip ccpm.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip ccpm.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Review generated PRDs and epics before syncing, because sync creates real GitHub issues visible to your team
  • Keep the epic and task names consistent so the status scripts can find them
  • Run the bundled status scripts for read-only checks before asking the agent to change anything

What's inside

  • references/conventions.md
  • references/execute.md
  • references/plan.md
  • references/scripts/blocked.sh
  • references/scripts/epic-list.sh
  • references/scripts/epic-show.sh
  • references/scripts/epic-status.sh
  • references/scripts/help.sh
  • references/scripts/in-progress.sh
  • references/scripts/init.sh
  • references/scripts/next.sh
  • references/scripts/prd-list.sh
  • references/scripts/prd-status.sh
  • references/scripts/search.sh
  • SKILL.md

Redistributed unmodified from automazeio/ccpm under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.