claude-delegate

Claude Delegate

When to Use

• You want to delegate a bounded coding task to a separate claude implementer (Claude Code) and then review its diff yourself.
• The user explicitly asked for delegation to this implementer.

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. On macOS the live credentials sit in the

login Keychain; when the orchestrator's own sandbox blocks Keychain access (Codex's sandbox does), claude falls back to a possibl