orchestrator-implementer-judge-loop
Strict orchestration workflow for engineering tasks that must be solved one numbered problem at a time through an explicit cycle: define the current problem, build a Robust Code strategy, delegate the work to an implementer with the current situation and exact solution method, send the result to a judge with the audit target and audit criteria, repeat implementation and judgment until defects are closed, then issue a final orchestrator verdict before moving to the next problem. Use when Codex must run a deterministic orchestrator-to-implementer-to-judge regression loop with bounded scope, explicit packets, and no ambiguity.