| name | codex-delegation |
| description | How to delegate implementation tasks to workers via Codex MCP or Task sub-agents. Use when executing tasks that require code implementation. |
Worker Delegation Skill
This skill defines how the CEO (Claude) delegates tasks to workers. Workers can be either Codex MCP (GPT) or Claude Task sub-agents.
Executor Selection
The executor is determined by priority:
--executor argument (explicit override)./specs/.ralph-executor.json (saved config from /ceo-ralph:setup)- Runtime detection: check if
mcp__codex__codex tool exists
- Default:
auto (try Codex, fall back to Task)
Codex MCP Executor
- Tool:
mcp__codex__codex
- Runs GPT models in a sandboxed environment
- Best for: code generation, file manipulation
- Requires: Codex CLI installed + authenticated
Task Sub-agent Executor
- Tool:
Task with subagent_type: "general-purpose"
- Runs Claude sub-agents (model: sonnet)
- Best for: when Codex is unavailable, or for Claude-native tasks
- Requires: nothing (built into Claude Code)
When to Delegate
Delegate to workers when:
- Task is implementation-focused (writing code)
- Task has clear acceptance criteria
- Task doesn't require strategic decisions
- Task is scoped to specific files
Do NOT delegate when:
- Task requires architecture decisions
- Task is a [VERIFY] checkpoint (delegate to qa-engineer instead)
- Task requires user interaction
- Task involves research or analysis
