Ccpm

OrganizationPopular

automazeio

ccpm

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.

Overview

Publisher	automazeio
Repository	`ccpm`
Skill name	`ccpm`
Stars	8.4K
Forks	835
Bundled files	20
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
20 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by automazeio on GitHub. Read the source before you install it.

Installation

Install the Ccpm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/automazeio/ccpm.git /tmp/ccpm
mkdir -p .claude/skills
cp -r /tmp/ccpm/skill/ccpm .claude/skills/ccpm

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ccpm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ccpm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ccpm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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. Read: references/execute.md Covers: Issue analysis (parallel work stream identification), launching parallel agents, coordinating worktrees.

5. Track — Know where things stand

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.

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

Quick Reference


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"

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ccpm AI skill do?

Why use Ccpm on TypingMind?

Because you install it once and use it with any model. Ccpm is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ccpm in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/automazeio/ccpm/tree/main/skill/ccpm. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ccpm?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ccpm?

As many as you like. As long as a model supports skills, you can use Ccpm with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ccpm AI skill free?

Yes. It is published on GitHub by automazeio under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

Ask Matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

Code Review

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 what…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

CCPM - Claude Code Project Manager

Core Philosophy

File Conventions

The Five Phases

1. Plan — Capture requirements

2. Structure — Break it down

3. Sync — Push to GitHub

4. Execute — Start building

5. Track — Know where things stand

Script-First Rule

Quick Reference

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now