claude-delegate

# Claude Delegate You are the **orchestrator**. Delegate one bounded coding task to a separate **implementer** — a Claude Code CLI session — then review what it produced and land it yourself. You write the brief and own the judgment; the separate Claude session edits the working tree; you verify and commit. This skill is not a signal for the current Claude to implement directly. Use it only after the human explicitly asks for delegation to another Claude Code process or session. ## When not to use this - The human asked the current agent to implement the task directly. - The task is small enough to do inline and the human did not request delegation. - The `claude` CLI is missing or unauthenticated (`claude auth status`). - The task needs a stronger host boundary than Claude Code's tool permissions and shell-only sandbox provide. Use an isolated container or VM for that requirement. ## Prerequisites 1. `claude --version` succeeds. 2. `claude auth status` reports an authenticated session. 3. The target repository is the directory passed with `--cd`. 4. On Linux/WSL2, Claude's sandbox dependencies are installed. The normal relay profile is configured to fail when the sandbox is unavailable instead of silently running shell commands unsandboxed. Existing merged settings can still affect the effective boundary. ## The loop ### 1. Write the brief The separate session has no orchestrator chat history. It receives the brief on stdin and can inspect the target working...