Saga
warpdotdev/common-skills
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
$ npx skills add automazeio/ccpm --skill ccpm -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automazeio/ccpm ccpm --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/ccpm .claude/skills/ccpm && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .claude/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automazeio/ccpm/tree/main/skill/ccpmType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automazeio/ccpm --skill ccpm -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automazeio/ccpm ccpm --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill/ccpm .agents/skills/ccpm && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .agents/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automazeio/ccpm --skill ccpm -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automazeio/ccpm ccpm --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill/ccpm .cursor/skills/ccpm && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .cursor/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automazeio/ccpm.git --path skill/ccpm--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automazeio/ccpm --skill ccpm -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automazeio/ccpm ccpm --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill/ccpm .gemini/skills/ccpm && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .gemini/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automazeio/ccpm ccpmInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automazeio/ccpm --skill ccpm -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill/ccpm .github/skills/ccpm && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .github/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automazeio/ccpm --skill ccpm -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automazeio/ccpm ccpm --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automazeio/ccpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill/ccpm .opencode/skills/ccpm && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ccpm" agent skill from https://github.com/automazeio/ccpm/tree/main/skill/ccpm into .opencode/skills/ccpm/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccpm", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ccpmRuns a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Software delivery is organized around files and GitHub issues. A feature starts as a PRD, becomes a technical epic, is split into numbered task files with dependencies, is synced to GitHub issues, and is executed by parallel agents working in worktrees. The core idea is that requirements live in files, not in anyone's head.
Work is divided into five phases, each with its own reference note: plan, structure, sync, execute and track. Plan covers guided PRD writing and converting a PRD to an epic, sync pushes epics and tasks to GitHub and posts progress comments, execute analyzes parallel work streams, and track covers status, standups, what is blocked and what is next. A conventions file sets path standards and frontmatter schemas.
For read-and-report jobs the agent is told to run the bundled bash scripts directly instead of redoing the work by hand, for example status, standup, epic list, epic status, next and blocked. The skill steps aside for debugging, writing tests, reviewing PRs or plain GitHub issue operations.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 7d7e462. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (Shell, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
bashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
CCPM Project Management loads about 1.1k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 226 tokens; SKILL.md has 356 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from automazeio/ccpm at commit 7d7e462, republished under its MIT licence (© automazeio). 356 words, ~1,118 tokens.
.claude/skills/ccpm/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.A spec-driven development workflow: PRD → Epic → GitHub Issues → Parallel Agents → Shipped Code.
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.
Before doing anything, read references/conventions.md for path standards, frontmatter schemas, and GitHub operation rules. These apply to all phases.
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.
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.
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.
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.
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.
For deterministic operations — anything that reads and reports without needing reasoning — always run the bash script directly rather than doing the work manually:
| What the user wants | Script to run |
|---|---|
| Project status | bash references/scripts/status.sh |
| Standup report | bash references/scripts/standup.sh |
| List all epics | bash references/scripts/epic-list.sh |
| Show epic details | bash references/scripts/epic-show.sh <name> |
| Epic status | bash references/scripts/epic-status.sh <name> |
| List PRDs | bash references/scripts/prd-list.sh |
| PRD status | bash references/scripts/prd-status.sh |
| Search issues/tasks | bash references/scripts/search.sh <query> |
| What's in progress | bash references/scripts/in-progress.sh |
| What's next | bash references/scripts/next.sh |
| What's blocked | bash references/scripts/blocked.sh |
| Validate project state | bash references/scripts/validate.sh |
Use the LLM for work that requires reasoning: writing PRDs, analyzing parallelism, launching agents, synthesizing updates.
Plan a feature: "I want to build X" or "create a PRD for X"
Parse to epic: "turn the X PRD into an epic"
Decompose: "break down the X epic into tasks"
Sync to GitHub: "push the X epic to GitHub"
Start an issue: "start working on issue 42"
Check status: "what's our status" / "standup"
What's next: "what should I work on next"
Merge epic: "merge the X epic"
Report a bug: "found a bug in issue 42" / "testing issue 42 revealed X"© automazeio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 20 other files (references) in skill/ccpm of automazeio/ccpm.
Open the folder on GitHubat commit 7d7e462
CCPM Project Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CCPM Project Management this skillautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sagawarpdotdev/common-skills | 608 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Reviewfossasia/eventyay-interpretation | 1.6k | 35 repos | ~996 | Automated safety check: Pass | Apache-2.0 | |
| Gh Issuestrpc-group/trpc-agent-go | 1.8k | 8 repos | ~8.7k | Automated safety check: Pass | Apache-2.0 | |
| Review Spdzhu1090093659/spec_driven_develop | 984 | — | ~1.5k | Automated safety check: Pass | MIT | |
| GitHub Project Management Swarmruvnet/agentic-flow | 816 | 6 repos | ~7.1k | Automated safety check: Pass | None |
warpdotdev/common-skills
Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.
fossasia/eventyay-interpretation
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match…
trpc-group/trpc-agent-go
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments.
zhu1090093659/spec_driven_develop
Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.
ruvnet/agentic-flow
Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.
OpenMinis/MinisSkills
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment.
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts. Software delivery is organized around files and GitHub issues. A feature starts as a PRD, becomes a technical epic, is split into numbered task files with dependencies, is synced to GitHub issues, and is executed by parallel agents working in worktrees.
CCPM Project Management fits situations like: writing a PRD and turning it into an epic with tasks; syncing an epic's tasks to GitHub issues; starting parallel agents on several GitHub issues; running a standup or checking what is blocked and what is next.
Run `npx skills add automazeio/ccpm --skill ccpm -a claude-code`. Or copy the skill folder (skill/ccpm in automazeio/ccpm) into .claude/skills/ccpm in your project. Claude Code loads it when a task matches its description.
Run `npx skills add automazeio/ccpm --skill ccpm -a codex`. Or copy the skill folder (skill/ccpm in automazeio/ccpm) into .agents/skills/ccpm in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automazeio/ccpm --skill ccpm -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccpm, .gemini/skills/ccpm, .github/skills/ccpm and .opencode/skills/ccpm in your project.
Going by SKILL.md and its folder, CCPM Project Management needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A GitHub repository with Issues enabled; Bash and Git for the bundled scripts.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
CCPM Project Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with CCPM Project Management: Saga (warpdotdev/common-skills, 608 stars), Review (fossasia/eventyay-interpretation, 1.6k stars), Gh Issues (trpc-group/trpc-agent-go, 1.8k stars) and Review Spd (zhu1090093659/spec_driven_develop, 984 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
automazeio (a GitHub organization) maintains it in automazeio/ccpm, which has 8,408 GitHub stars. The repository was last updated on March 18, 2026.
Source: automazeio/ccpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.