| name | codex-implementation |
| description | Delegate bounded implementation work to Codex (GPT-5.x) — clear-spec features, migrations, bulk mechanical edits. Use when a task is well-specified enough to hand off whole and worth doing on Codex's near-free usage instead of Claude's, usually in a worktree. |
Bounded implementation via Codex
Codex only gets what you put in the prompt — no conversation context, no memory. Bounded is the contract: a task Codex can complete from the prompt alone, with a done-condition you can check mechanically afterward.
Command mechanics (flags, sandbox, resume) live in the shared wrapper's docs: C:\Users\shawn\.claude\skills\codex\SKILL.md.
Steps
-
Bound the task. Write a self-contained prompt: what to build or change, which files/dirs are in scope, relevant conventions from the codebase, and an explicit done-condition (e.g. "tests in X pass", "every call site of Y migrated"). Done when someone with no context could execute from the prompt alone.
-
Isolate. If Codex's edits could collide with work in the current tree, create a git worktree and point Codex there. Done when the working root is one Codex can freely mutate.
-
Run with write access, generous timeout:
node C:\Users\shawn\.claude\skills\codex\scripts\codex-run.mjs --write --cd <worktree-or-repo> "<bounded prompt>"
If it comes back incomplete, resume the same session with a short delta prompt (--resume-last) rather than restarting. Done when Codex reports the done-condition met.
-
Verify before adopting. Read the full diff, run the tests or checks named in the done-condition yourself, and judge the code against the taste bar — Codex solves problems well but writes TypeScript like a Python dev. Rework or redo with a smarter model anything below the bar; escalating costs less than shipping mediocre work. Done when every changed file has been read and the done-condition independently confirmed.
