ccc-adopt

$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:start --> marker and replace in place — never duplicate the block.

Arguments

• --check — read-only: detect stack + existing CLAUDE.md + marker state, print the plan, do NOT write anything.
• bare $ccc-adopt — detect, preview the diff via chips, write on confirm.

Step 1 — Detect

IS_GIT=$(git rev-parse --show-toplevel 2>/dev/null || echo "")
echo "GIT_ROOT=${IS_GIT:-n/a}"

HAS_CLAUDE_MD=$([ -f "CLAUDE.md" ] && echo yes || echo no)
HAS_MARKER=$(grep -l "CCC:orchestrator-executor:start" CLAUDE.md 2>/dev/null && echo yes || echo no)
echo "HAS_CLAUDE_MD=$HAS_CLAUDE_MD"
echo "HAS_MARKER=$HAS_MARKER"

# Stack detection — same style as ccc-onboard's clone-time validator
test -f package.json && echo "STACK=node" && grep -o '"\(react\|next\|vue\|nuxt\|express\|fastify\|hono\)"' package.json 2>/dev/null
test -f pyproject.toml -o -f requirements.txt && echo "STACK=python"
test -f Cargo.toml && echo "STACK=rust"
test -f go.mod && echo "STACK=go"
test -f Gemfile && echo "STACK=ruby"
test -f composer.json && echo "STACK=php"
test -f pom.xml -o -f build.gradle && echo "STACK=jvm"

# Package manager clues (mirrors ccc-onboard)
test -f bun.lockb -o -f bun.lock && echo "PM=bun"
test -f pnpm-lock.yaml && echo "PM=pnpm"
test -f yarn.lock && echo "PM=yarn"
test -f package-lock.json && echo "PM=npm"