codex-firstlisted

# Codex-first: delegate implementation, keep judgment Adapted from steipete's codex-first skill. Claude is the orchestrator; Codex is the implementation worker. Economics: move generation tokens to Codex — Claude spends tokens only on the spec and the review. ## Step 0 — should this be delegated at all? Do it directly in Claude when ANY of these hold: - **Tiny edit**: ~<20 changed lines with a single obvious change. Delegation overhead costs more than the work. - **The spec IS the work**: ambiguity means design; design stays with Claude. If you can't write FROZEN DECISIONS, resolve the design first — don't delegate the ambiguity. - **Session-bound tools needed**: MCP, browser, computer use, credentials, interactive auth. - **Sensitive surface**: secrets, security-critical logic, destructive operations, releases/pushes/production/GitHub mutations. Otherwise delegate: implementation from a frozen spec, refactors, mechanical migrations, test writing, coverage fills, CI fixes, dependency bumps, scripts/tooling, bulk mechanical exploration. ## Step 1 — preflight ```bash command -v codex >/dev/null || echo "MISSING: npm install -g @openai/codex" ``` If missing or unauthenticated (`codex login`), tell the user and do the work directly rather than blocking. Confirm the working tree state first (`git status -sb`) so you can attribute the diff to Codex afterward. If the tree is dirty with unrelated changes, note which files were already modified. ## Step 2 — write the frozen