ccpm

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