CC Commander.
The AI project manager that sits above your Claude Code sessions.
Not another prompt pack. CC Commander orchestrates 71 plugin skills across 22 specialist agents and 23 lifecycle hooks, compounds knowledge from every session into the next, and ships real code while you sleep. One install. Zero config. Free for now.
One command turns Claude Code into a staffed dev team.
Most Claude Code tools live inside your session — they inject prompts, add context, append rules. CC Commander runs a level above all of that: it picks which skill fires, routes complexity to the right specialist, and tracks progress across builds.
/ccc-fable.You type. It plans. Agents build.
- npx / plugin install
- reads package.json
- picks the profile
- /ccc menu
- spec interview
- parallel dispatch
- tests + types + e2e
- lessons captured
- skills compound
▸ why it matters — one command turns Claude Code into a staffed dev team: 71 skills, 22 agents, zero config.
CC Commander grew from a single frustration: the Claude Code ecosystem had fragmented into dozens of separate prompt packs, extensions, and skill bundles — each configured by hand, none aware of the others. Every new tool meant another setup cycle, and none of them carried what you learned in the last session into the next. Nobody had stitched the ecosystem into one interface.
Commander does. It aggregates 18 vendor packages — gstack, Superpowers, Compound Engineering and 15 others — into 457+ total skills surfaced through one click-first menu. Auto-detect what you have installed, sequence the tools in the right order, route each task to the right model tier, and inject past lessons into every new session. Ships under MIT license with a single npm dependency (figlet) and a clean security audit — 0 issues.
v6.4.0’s headline is the Fable Method — the operating doctrine distilled from Claude Fable 5, encoded as 12 enforceable gates (never trust a single pass, loops need verifiers/state/stops, prove before you alarm, context is disposable) so any model running CCC — Sonnet, GPT, anything — produces Fable-shaped results. The method IS the moat. Run /ccc-fable to turn it on, check status, or run audit to self-check which gates the session is violating.
v6.3.0’s Orchestrator/Executor doctrine still ships — “pay for Fable on the thinking, not the typing.” A high-reasoning orchestrator (Claude Fable 5 or Opus 4.8) writes the plan; a fast executor (GPT-5.5 via codex, or a Sonnet subagent) implements it; the orchestrator verifies against acceptance criteria. Roughly 70% token savings on large tasks. Run /ccc-orchestrate to use it, /ccc-handoff to reset context before quality degrades, and /ccc-adopt to bring the doctrine into any existing project.