ccc-plan SKILL.md skillA

ccc-plan from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kevinzai/commander/ccc-plan@git:20261013.fbe187d

Pins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kevinzai/commander
Path: commander/cowork-plugin-codex/skills/ccc-plan/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: Jul 1, 2026
Size: 8,588 bytes
Repository stars: 6
License: MIT

Turn an idea, bug, refactor or Linear issue into a reviewed plan file with evals, via a short spec interview and a background planner agent that writes to the session plan path. Use when the user wants to plan a feature, scope work before coding, or types $ccc-plan.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# $ccc-plan — spec before any code

**CC Commander** · $ccc-plan · a plan file with success and failure evals, shown in the Desktop Plan pane before anything is built.

This is the evals-before-specs-before-code gate. Plan mode is entered here because the user asked for a plan; it is not the session's default posture.

## When to use / when not to

- Use for multi-step features, non-trivial bug fixes, refactors, or turning a tracker issue into scoped work.
- Use `$ccc-brainstorm` first when the approach itself is undecided. Use `$ccc-plan-exec` when the work is the same body repeated over many items. Skip planning for a one-line fix.

## What happens

### 1. Resolve `PLAN_PATH` (always first)

- If the system context contains a "Plan File Info" block, plan mode is already active: capture that path as `PLAN_PATH` and do not call `EnterPlanMode`.
- Otherwise call `EnterPlanMode` and capture the path it returns as `PLAN_PATH`.
- If `EnterPlanMode` is not available (Codex, or a context without plan mode), set `PLAN_PATH` to `~/.claude/plans/ccc-<YYYY-MM-DD>-<slug>.md` and tell the user the Desktop Plan pane may not pick it up.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-plan@sha256:cca26a104e643bc9

The line at the top of this page pins the label git:20261013.fbe187d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_5qp76xuj6nguc3tn.svg)](https://markdownregistry.com/a/art_5qp76xuj6nguc3tn)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Jul 1, 2026 and Oct 13, 2026, about one every 26 days.

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	8,588 B	A	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	14,274 B	A	view · diff
git:20260716.930d05a	2026-07-16	930d05a	14,142 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	14,143 B	A	view · diff
git:20260701.1f4accc	2026-07-01	1f4accc	13,974 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8588 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_5qp76xuj6nguc3tn
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-plan
GET https://markdownregistry.com/api/v1/blob/cca26a104e643bc9f83c4e2116d077b63c358a90026c7d6e7dab357e5d418fc6

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from kevinzai/commander

mintlify SKILL.md skill

kevinzai/commander · .agents/skills/mintlify/SKILL.md · Build and maintain documentation sites with Mintlify. Use when

v1.0 · audit A · 6 stars

.cursorrules Cursor rule

kevinzai/commander · .cursorrules

git:20260327.b10b207 · audit A · 6 stars

AGENTS.md AGENTS.md file

kevinzai/commander · AGENTS.md