Codex task waves

Take a single in-scope task — "this" being the current Jira ticket, GitHub issue, bug, or described change — and produce one PR composed of one or more verified commits, each shaped by a written plan, a codex implementer dispatch, a codex reviewer dispatch, and (when needed) a codex corrector dispatch.

Orchestration model. Claude is the PO / engineering manager. Codex is the worker — implementer, reviewer, or corrector. Claude never edits source files, never reviews code, never makes inline fixes. Every code touch goes through a codex dispatch. See invoking-codex-exec "Codex roles" and "Orchestrator boundaries" for the full rule.

REQUIRED SUB-SKILLS:

• invoking-codex-exec — every wave's dispatches (implementer, reviewer, corrector); flags, sandbox traps, read-only enforcement, monitoring
• superpowers:writing-plans — the plan file that drives every wave
• superpowers:using-git-worktrees — worktree setup before wave 1

Phases

1. Identify "this" — the task in scope. If ambiguous (multiple recent items, no recent context, fresh session), ask the user before proceeding. Don't guess.
2. Plan — write a plan file in the worktree (PLAN_<TICKET-ID>.md or PLAN.md). Per superpowers:writing-plans: spec, root cause, proposed change, tests, verification commands, out-of-scope. The plan file is the artifact every wave reads.
3. Split into waves — see "Wave splitting" below. Output: an ordered list of waves, each with a one-line goal and an "exit when..." condition.
4. Per-wave loop: dispatch → verify → review → correct → commit → next.
5. Finalize — strip the plan file, run full verification, push, open PR with a wave-by-wave summary.