run-codex-exec

This is a deprecated compatibility shim. Do not restore the old implementation here. The active runtime is orchestrate-codex exec mode. This skill exists so that users who installed the old path or who reach for the old verb still get routed to the right place.

When to use this skill

Trigger when the user is asking for the exec-mode workload, regardless of whether they name the skill:

• "run codex exec across these tasks in parallel worktrees"
• "spawn N codex agents, one per task, each in its own git worktree, auto-commit when done"
• "parallel codex exec fleet with a live monitor and per-worktree commits"
• "give me run-codex-exec for tasks A, B, C"
• "orchestrate codex exec on tasks.json"
• "fan out codex agents across a tasks list, each agent in a worktree, watch progress live"

Do NOT use this skill when

• The user wants one prompt template applied to N inputs (URLs, IDs, file paths) with one answer file per input → use run-batch-codex-research (also a shim) → routes to orchestrate-codex batch mode. No worktrees, no auto-commit; idempotent skip-existing.
• The user wants per-branch codex review convergence loops with classifier-driven rounds → use run-codex-review (also a shim) → routes to orchestrate-codex review mode. Branch list, not task list; review surface, not coding tasks.