ccpm

Solid

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 ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.

Code & Development 8,145 stars 831 forks Updated 2 months ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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. ...

Details

Author
automazeio
Repository
automazeio/ccpm
Created
9 months ago
Last Updated
2 months ago
Language
Shell
License
MIT

Integrates with

GitHub · DevTools

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

prd-taskmaster

Smart PRD generator with TaskMaster integration. Detects existing PRDs and offers execute/update/replace options. Generates comprehensive technical PRDs optimized for task breakdown, validates with 13 automated checks, and optionally executes tasks autonomously with datetime tracking and rollback support. Use when user requests "PRD", "product requirements", or mentions task-driven development. Defaults to PRD generation with handoff to TaskMaster. Optionally supports autonomous execution with 4 modes.

451 Updated 4 weeks ago
anombyte93
Web & Frontend Featured

code-to-prd

Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.

16,173 Updated today
alirezarezvani
AI & Automation Featured

agent-orchestrator

Open-source, pluggable agentic coding orchestrator. Manages durable coding agents (Claude Code, Codex, OpenCode) through a simple interface — spawn agents, track progress, and let feedback loops like PR reviews and CI failures automatically route to the right agents. Use for fixing bugs, building features, working on GitHub issues, checking status, and managing agent sessions.

7,269 Updated yesterday
ComposioHQ
AI & Automation Solid

prd

Generate Product Requirements Documents with optional research — brainstorm, challenge assumptions, define scope

1,727 Updated 3 days ago
maxritter
Code & Development Solid

sddp-projectplan

Create or refine the canonical project-level Project Implementation Plan (`specs/project-plan.md`)

76 Updated 3 weeks ago
attilaszasz