codex-delegation

Delegates implementation tasks to Codex GPT-5.6 models with tiered routing and fallback rules.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/em411/supercodex --skill codex-delegation-em411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-delegation
Source: https://github.com/em411/supercodex/tree/main/skills/codex-delegation
Command: npx skills add https://github.com/em411/supercodex --skill codex-delegation-em411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating work between an orchestrating AI and an external coding model requires consistent rules for model selection, dispatch, retries, and failure handling; this Skill defines that contract so implementation tasks are delegated to Codex GPT-5.6 predictably and transparently. ## Core Features & Use Cases - Tiered Model Routing: Classifies each task as mechanical, standard, or complex and routes it to gpt-5.6-luna, gpt-5.6-terra, or gpt-5.6-sol with matching effort levels. - Preflight & Health Checks: Verifies the Codex CLI is installed, authenticated, and new enough to support the GPT-5.6 tiering models before the first delegation. - Fix Cycles & Fallback Ladder: Resumes Codex sessions with delta-only fix instructions after review findings, and falls back to a Claude implementer subagent after repeated failures, always announced to the user. - Use Case: While executing a multi-task implementation plan, the orchestrator dispatches each coding task to the appropriate Codex tier, reviews the returned diff, sends back only the review findings for fixes, and records the model and fix-cycle count in a progress ledger. ## Quick Start Ask Claude to implement the next task in the plan and have it delegated to the appropriate Codex GPT-5.6 model tier.

Frequently Asked Questions about codex-delegation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate coding tasks to Codex from Claude Code?

Dispatch every task through the codex-implementer agent with a complete task prompt plus explicit --model and --effort flags. The orchestrator classifies the task first and never calls the Codex runtime directly, keeping Codex transcripts out of its context.

How does Codex model tiering choose between sol, terra, and luna?

Task classification determines the tier: mechanical work like renames and boilerplate goes to gpt-5.6-luna, standard plan tasks go to gpt-5.6-terra, and complex implementation or debugging goes to gpt-5.6-sol. The orchestrator picks the tier; the implementer agent never selects models itself.

What Codex CLI version is required for GPT-5.6 models?

Codex CLI version 0.144.4 or later is required, since earlier versions reject the GPT-5.6 tiering models. If the preflight reports supportsGpt56 as false, tasks are dispatched without --model so Codex uses its supported default instead of falling back.

What happens when a Codex delegation fails?

The first failure triggers one retry, resuming the existing Codex session if available. A second failure falls back to a Claude implementer subagent with the same task brief, announced to the user in one line and recorded in the ledger.

When should I use --write instead of --full-access for Codex tasks?

Use --write when the workspace is untrusted or the user requests containment, since the sandbox mounts .git read-only and may block nested processes. In that mode the orchestrator makes commits after independently re-running the task's tests.