Skills
61 click-first /ccc-* slash commands. Every menu is a native chip picker — no typing, no YAML, no syntax to memorize.
/ccc-deploy, /ccc-rollback, /ccc-onboard, /ccc-fleet-viz·
Cursor + Windsurf adapter scaffolds · Fly.io hosted MCP infra ready·
product contract CI gate · auto-CHANGELOG from conventional commits·
vanilla dashboard at port 4690 · React app retired · zero deps·
v4.0.0-beta.11
production hardening · 6 new skills · model pins · 560+ tests·
SessionStart orchestrator ~57ms p95 win · clickability AskUserQuestion enforcement·
Mintlify docs polish · 18-tool MCP cloud smoke suite·
v4.0.0
stable · 2026-04-26 · 60 plugin skills, 22 agents, 9 hooks, 862 tests — Codex fleet + cross-platform launch·
added /ccc-deploy, /ccc-rollback, /ccc-onboard, /ccc-fleet-viz·
Cursor + Windsurf adapter scaffolds · Fly.io hosted MCP infra ready·
product contract CI gate · auto-CHANGELOG from conventional commits·
vanilla dashboard at port 4690 · React app retired · zero deps·
Master Claude Code instantly. 60 plugin skills. 22 specialist agents. 9 lifecycle hooks. One install, zero config, free for now.
You have product velocity to protect. Commander gives your team a shared methodology, severity-rated reviews, and parallel worktrees so two engineers don't redo the same plan.
The fleet-worker dispatches on git worktrees so each project stays clean. Commander remembers each client's CLAUDE.md, conventions, and review rubric — context-switching becomes a slash command.
You don't need a project manager. You need 22 of them, on tap. Commander ships the discipline that solo devs end up reinventing on year three of a project.
Hooks log every tool use. PreToolUse blocks unknown commands. The security-auditor flags SEV-1 before deploy. MIT licensed, self-hosted, no telemetry — pass the SOC2 review on the first try.
Stock Claude Code is a blank terminal with amnesia. Every other plugin solves one slice. Commander is the first guided AI PM — click-first UX, an intelligence layer that thinks before you do, and the whole ecosystem pre-wired.
61 click-first /ccc-* slash commands. Every menu is a native chip picker — no typing, no YAML, no syntax to memorize.
22 specialist sub-agents with persona voices — architect, reviewer, security-auditor, debugger, designer. The brain/hands pattern: orchestration separated from execution.
9 lifecycle events × 9 lifecycle events × 9 lifecycle events × 24 handlers. SessionStart through SubagentStop fire automatically — the right agent runs at the right moment, every time.
/ccc and watch the orchestrator dispatch.Three surfaces, one plugin. Pick a chip on the left — the brain routes to the right specialist, hooks fire on lifecycle events, hands ship the diff.
/ccc-saas. Pick a workflow:stripe-checkoutbuilder + saas-specialistPreToolUse — verifying scope, deps, secretsScaffolded /api/checkout, wired client SDK, added webhook handler. Ready for review.
3 SEV-2 findings on session rotation. Suggested patches attached. /ccc-review --apply
FOR/AGAINST analysis on the email provider choice. Resend vs Postmark vs SES. ETA 2m.
From cold-start to /ccc in under 30 seconds. No API keys, no signup, no credit card. The plugin marketplace handles the rest.
Stock Claude Code is a blank prompt. You write the methodology, the spec template, the review rubric, the hook handlers. Or you type one slash command.
# CLAUDE.md ## Persona You are a senior engineer working on a SaaS product. You plan first, ship small, and operationalize fixes. ## Workflow for new features 1. Spec interview: ask 5-7 clarifying questions before code. 2. Write a plan.md with: scope, schema, files touched, tests. 3. Wait for approval before any implementation. 4. Implement in vertical slices, one PR at a time. 5. Run reviewer pass: severity-rate every diff. ## Review rubric SEV-1 = blocks deploy (auth, payments, data loss) SEV-2 = must fix before merge (race, perf, regression) SEV-3 = should fix this sprint (polish, dx) ## File conventions - src/* uses TypeScript strict mode - API routes return Result<T, AppError> - Webhooks verify signatures, no exceptions - Migrations are reversible - New deps require one-line justification ## Hooks - Before any tool use, log to .claude/audit.log - After session end, summarize diffs in NOTES.md - On error, dispatch debugger sub-agent - ... (180 more lines)
$ /plugin install commander ✓ 60 skills active ✓ 22 agents wired ✓ 9 hooks × 9 hooks × 9 hooks × 24 handlers ✓ BIBLE.md methodology loaded ✓ review rubric: SEV-1/2/3 # now type: $ /ccc-plan add stripe checkout → commander interviews you (5 questions) → writes plan.md → waits for approval → dispatches builder + saas-specialist → reviewer passes severity check → ships # the methodology is already written. # the agents are already wired. # the hooks are already firing. # you just type slash commands.
Stock Claude Code ships a powerful blank canvas. Commander adds the workflow layer most teams end up rebuilding from scratch — except it’s already built, opinionated, and free.
/ccc-suggest recommends by nameEach agent embodies a distinct role, model and voice — wired through the Claude Agent SDK sub-agent architecture. Ask once; the right specialist runs every time.
Every plugin skill that ships with Commander. Filter by domain, click a card to peek at the YAML manifest. The agent doesn't pick by accident — it picks from this menu.
Domain routers narrow the 457-skill ecosystem down to the half-dozen moves that matter for what you’re doing right now. Type the slash command, click the chip.
Every Claude Code event has a handler attached. Hover the timeline to see what fires when, and which handlers ship by default.
A two-layer SDK pattern with lifecycle automation between. Skills become inputs, agents become tools, hooks become guardrails. You write nothing — it’s already wired.
“Plan first. Ship small.
Operationalize fixes.”
Every feature starts with a spec interview. /ccc-plan writes a plan file you can read, review and reject before a token is burned on implementation.
The reviewer agent enforces it. Diffs that try to do two things get rejected with a severity rating. Boring is the strategy.
Every regression that lands in production turns into a lifecycle hook. The session never has to remember — it’s already enforced.
Every skill, every agent, every hook, every domain router — installable today, in beta, in production, on day one thousand. MIT licensed. It will not get worse.
/ccc-connect (you see them, you choose) and Kevin Z’s consulting practice underneath. The plugin itself is, and stays, MIT.
Works in Claude Code Desktop, the CLI, and any MCP-capable IDE. Pick the path that matches where you live — same plugin underneath.
Settings → Plugin Marketplace → Add from GitHub. Or run it from the CLI.
$/plugin marketplace add KevinZai/commander
One command activates 60 skills, 22 agents, 9 hooks, and 2 MCP servers.
$/plugin install commander
/ccc.The chip picker pops. Build · Review · Ship · Design · Learn · More. Click and go.
$/ccc
/ccc-connect shows transparent affiliate links to optional MCP integrations (Supabase, Vercel, Notion, etc.) — you see them and choose. Kevin Z’s consulting practice covers the rest.context7 and sequential-thinking — are credential-free. Sixteen optional integrations are opt-in via /ccc-connect; only those need keys, and only if you want them.mcp.commanderplugin.com — same 502+ skills, one URL./ccc-plan, /ccc-review). An agent is a persona with a distinct role, model, and voice that the orchestrator dispatches to. Skills route to agents. The brain/hands pattern./ccc-suggest recommends specific third-party plugins by name when they’re the right tool — claude-mem for persistent memory, superpowers for structured thinking, caveman for token-heavy iteration, and a dozen more./plugin uninstall commander removes everything. Or for the binary install, ./uninstall.sh at the repo root. No background daemons, no system-wide configs, nothing left behind.KevinZai/commander, or DM @commanderplugin on X. Or just run /ccc-doctor — if it’s a known regression, it’ll tell you the workaround. Otherwise it generates a bug report ready to paste.$/plugin install commander