summon-cclisted

Spawn and conduct Claude Code worker sessions in detached tmux panes — run Claude Code in the background, from any agent on any harness. Use when asked to orchestrate or delegate work to Claude Code sessions, spawn workers in tmux, fan tasks out across parallel sessions, run an implement-then-review loop, or supervise long unattended Claude Code runs. Workers are supervised through file signals — never by parsing the terminal.
anfreire/summon-cc · ★ 1 · Data & Documents · score 74

Install: claude install-skill anfreire/summon-cc

# summon-cc — conduct Claude Code sessions from any agent You are the **orchestrator**. You spawn full interactive Claude Code sessions ("workers") in detached tmux panes, hand each a scoped prompt, and supervise them through append-only file signals. You orchestrate; workers do the work. Three laws make this cheap and calm: 1. **Never parse the terminal.** The signals carry everything; the pane is a debug surface, read only when a signal says something is wrong. 2. **Never idle-poll.** One waiter per worker blocks silently until something happens. 3. **Act on signals, verify by signals.** Every move — spawn, prompt, answer — leaves a signal proving it landed. The scripts verify their own steps; you verify yours. Any agent on any harness can be the orchestrator — every capability here is a plain shell command. Only the *worker* side is Claude Code, and that's the point: this skill hands you Claude Code sessions as a building block, unrestricted — what you build with them (pipelines, review loops, fan-outs, watchdogs) is your call. ## Requirements - Linux or macOS; `bash`, `tmux`, `jq`, and a `claude` CLI with `--settings` and `--effort` (any current one — `claude --help` to confirm). - **Nothing to install or wire.** Spawn injects the six lifecycle hooks per worker via `--settings` on the launch line: no settings file of the user's is ever touched, and sessions you didn't summon never load these hooks at all. - The two scripts sit next to this SKILL.md in `sc