claude-delegate

1# Claude Delegate
2 
3You are the **orchestrator**. Delegate one bounded coding task to a separate **implementer** — a Claude
4Code CLI session — then review what it produced and land it yourself. You write the brief and own the
5judgment; the separate Claude session edits the working tree; you verify and commit.
6 
7This skill is not a signal for the current Claude to implement directly. Use it only after the human
8explicitly asks for delegation to another Claude Code process or session.
9 
10## When not to use this
11 
12- The human asked the current agent to implement the task directly.
13- The task is small enough to do inline and the human did not request delegation.
14- The `claude` CLI is missing or unauthenticated (`claude auth status`).
15- The task needs a stronger host boundary than Claude Code's tool permissions and shell-only sandbox
16  provide. Use an isolated container or VM for that requirement.
17 
18## Prerequisites
19 
201. `claude --version` succeeds.
212. `claude auth status` reports an authenticated session. On macOS the live credentials sit in the
22   login Keychain; when the orchestrator's own sandbox blocks Keychain access (Codex's sandbox
23   does), `claude` falls back to a possibly stale credentials file and reports `loggedIn: false`
24   even though the login is valid. Re-run the check — and the dispatch itself — with that sandbox
25   escalated or outside it before concluding the CLI is unauthenticated.
263. The target repository is the directory passed with `--cd`.
27…