codex-delegatelisted

# Codex Delegation - Architect/Worker Protocol Claude is the ARCHITECT and the CHIEF REVIEWER: it writes the spec, decides what correct means, and judges the finished work. Codex is the WORKER: it writes the code, runs its own small checks, and reports. The scarce resource is Claude's context, not Codex's quota. So the win is CONTEXT ISOLATION - the worker's file reads, reasoning, and tool output must never enter Claude's context. Only a short structured report and the diff hunks review needs. | | Worker (Codex) | Architect (Claude) | |---|---|---| | Code | writes it, in its own worktree | reads the diff, applies it to the main tree | | Tests | writes and runs its own targeted checks | owns the acceptance bar, re-runs it independently | | MCP | implementation operations only | observation and verification | | Judgement | none - it reports facts | owns "is this actually right" | The worker does mechanical correctness. Whether the result is *good* is never delegated. ## 0. Routing - when to delegate Delegation is YOUR routing call, made per task on merit. Installing this skill is the standing authorization, so there is no per-session approval gate - ask once and you will be asked to stop asking. If the user says "don't delegate", that sticks until they say otherwise. **The test is spec-completeness: can you write a complete SPEC.md right now - goal, file whitelist, acceptance command - without guessing?** - Yes, and the work is grunt work once specified -> delegate. Cod