Start with a story
Turn project notes into a clear plan and a useful first draft.
Keep the openingNext step is missing
Explore approaches / 02
Try different solutions before one shape becomes the whole project.
Turn project notes into a clear plan and a useful first draft.
Keep the openingCompare clarity, mobile fit, and maintainability. Candidate workers use separate output paths.
Use Arena for a homepage direction, an architecture, or another substantial artifact with several plausible approaches. A routine change rarely needs competing candidates.
Candidate workers explore in parallel, each in its own scratch folder. When the task improves something that already exists, the current version joins unchanged as a baseline and goes to the judge under a neutral letter like any candidate; picking it is a valid outcome. After the candidates finish, a blind judge sees only the criteria and the anonymized work, checks each one against them, and recommends a base. The manager reads every candidate, scores the criteria too, and rechecks the judge's evidence before overruling it. The base is the candidate whose design the planned merges would disturb least. From each other candidate the manager takes at most one or two ideas, rewritten to the base's conventions. When the baseline is the base, an idea comes in only if another candidate passed a criterion the baseline failed; otherwise the current version stands unchanged.
One final artifact, which is the unchanged current version when the baseline wins with nothing to add, and a note listing each worker, the judge’s verdict, the base and why, every idea taken or left, and the check results. Candidates stay in .tmp/arena/.
Fresh-context candidate workers, isolated output paths, and a fresh judge. When Codex is signed in with a ChatGPT login or set up with a gateway, one candidate and the judge run on Codex by default. Review starts after candidate writing stops, and the whole run gets one rerun. The combined result still needs verification; agreement is not a pass.
Three candidates answer the same homepage brief. The homepage is new, so there is no baseline. B becomes the base for its hierarchy and mobile layout. A contributes the opening explanation; C contributes a compact preview. The result is checked against the original rubric before it is accepted.
Define the artifact and a few concrete checks. In this example: explain the product on the first screen, fit navigation at 390px, and keep the page easy to extend.
$arena Explore three homepage approaches. Compare first-screen clarity, navigation at 390px, and maintainability.