Codex Implementation

Optional cross-vendor executor. Requires the OpenAI codex CLI. If command -v codex fails, this skill isn't available on this machine — say so and implement natively instead. The model-orchestration doctrine (references/model-orchestration.md) routes here only when the CLI is present.

Use Codex for bounded, clearly specified implementation work — typically in a worktree or from a parallel implementation agent producing a patch. Do not let Codex commit, push, deploy, or edit global config unless the user explicitly asked for that.

Workflow

1. Pin the current state with git status --short and note any user changes already present.
2. Define the implementation scope: files or behavior to change, files to avoid, constraints, and verification commands.
3. Create a temporary artifact directory for Codex's report.
4. Run codex exec with repo write access.
5. After Codex exits, inspect git status and git diff.
6. Run the cheapest reliable verification yourself when practical.
7. Report what Codex changed, what Claude verified, and any remaining risks.

Use this command shape: