send-to-minionlisted

# Send to Minion Delegate the user's prompt to exactly one helper agent, called the minion, then supervise it until completion. Treat explicit invocation of `$send-to-minion` or `/send-to-minion` as explicit user permission to spawn one subagent. Do not use this skill implicitly for ordinary requests that merely need research, depth, or careful execution. ## Contract - Spawn exactly one subagent for the user's task. - Do not spawn multiple agents, use CSV fan-out, or ask the minion to spawn nested agents. - Keep the parent agent responsible for orchestration, verification, cleanup, and the final user response. - Let the minion do the substantive delegated work. - Preserve the user's original goal, constraints, language, and requested output format. - Close the minion after completion, failure, or cancellation unless the runtime has already closed it. - Do not silently downgrade to parent-only execution. If no subagent mechanism is available, say so. ## Runtime Selection Use the native subagent mechanism for the current runtime. Do not mix runtimes in one invocation. Prefer this order: 1. Codex multi-agent tools when `spawn_agent` is available. 2. Claude Code subagents when the `Agent` tool is available. 3. A legacy/adapted subagent runner such as `Task` only when neither of the above names is exposed but the runtime clearly documents it as the subagent tool. If no subagent mechanism exists, follow Failure Handling. ## Codex Tool Setup Use Codex multi-agent tools wh