ccc-adoptlisted

# $ccc-adopt — Bring CCC Doctrine Into an Existing Project **CC Commander** · $ccc-adopt · Adopt Orchestrator/Executor in your own repo ## Not to be confused with - **`$ccc-onboard`** — onboards a new *contributor* INTO the cc-commander repo itself (this repo). - **`$ccc-tuneup`** — tunes up the user's local `~/.claude` CC Commander *install* (plugin freshness, junk, settings). - **`$ccc-adopt` (this skill)** — runs INSIDE ANY OTHER PROJECT (yours, not cc-commander) and adds CCC's Orchestrator/Executor doctrine plus a tailored skill/agent pointer list to that project's own `CLAUDE.md`. If the current working directory's git root is `cc-commander` itself, stop and point the user at `$ccc-onboard` or `$ccc-tuneup` instead — this skill is for adopting CCC doctrine into a *different* codebase. ## Safety rules (NON-NEGOTIABLE) - ❌ NEVER `rm` or `trash` anything. - ✅ Before ANY write to `CLAUDE.md`: `cp CLAUDE.md CLAUDE.md.backup-$(date +%Y%m%d-%H%M%S)`. - ❌ NEVER overwrite an existing `CLAUDE.md` wholesale — only append/replace the clearly delimited CCC block. - ❌ NEVER run outside a confirmed git repo without asking first (`git rev-parse --show-toplevel` must succeed, or the user must explicitly confirm working in a non-git directory). - ✅ Always show a diff preview via `AskUserQuestion` before writing anything. - ❌ NEVER silently create a `CLAUDE.md` that doesn't exist — offer via `AskUserQuestion` first. - ✅ Re-run safe: detect an existing `<!-- CCC:orchestrator-executor: