CCPM — Prompt Files
Verbatim Excerpt 1: SKILL.md description field
Prompting technique: Semantic intent mapping — the description covers natural language triggers explicitly to maximize autonomous activation.
description: "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."
Verbatim Excerpt 2: references/plan.md — PRD creation process
Prompting technique: Preflight check → guided interview → schema-enforced output
## Writing a PRD
**Trigger**: User wants to plan a new feature, product requirement, or area of work.
### Preflight
- Check if `.claude/prds/<name>.md` already exists — if so, confirm overwrite before proceeding.
- Ensure `.claude/prds/` directory exists; create it if not.
- Feature name must be kebab-case (lowercase, letters/numbers/hyphens, starts with a letter).
If not: "❌ Feature name must be kebab-case. Example: user-auth, payment-v2"
### Process
Conduct a genuine brainstorming session before writing anything. Ask the user:
- What problem does this solve?
- Who are the users affected?
- What does success look like?
- What's explicitly out of scope?
- What are the constraints (tech, time, resources)?
**Quality gates before saving:**
- No placeholder text in any section
- User stories include acceptance criteria
- Success criteria are measurable
- Out of scope is explicitly listed
**After creation**: Confirm "✅ PRD created: `.claude/prds/<name>.md`" and suggest:
"Ready to create technical epic? Say: parse the <name> PRD"
Verbatim Excerpt 3: Script-First Rule
Prompting technique: Explicit routing table (deterministic vs reasoning path)
## Script-First Rule
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` |
| 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.