Run N parallel candidates at one brief and synthesize: rubric-first framing, isolated fan-out, a cross-judge on a different model, criterion-by-criterion pick, hand grafting. When one attempt would lock in the wrong shape.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/arena/SKILL.mdN parallel candidates attack the same brief; the best artifact is picked criterion by criterion and strengthened by grafting. Diversity of candidates is the mechanism: agreement across independent attempts is high-signal, and divergence exposes what the brief under-specified.
execute insteadresearchEvery candidate gets the same brief, so the brief is the contract.
Task dispatches to oh-my-claudecode:executor,
one per candidate, each given its own output location.team.roleRouting from the project config (.claude/omc.jsonc) or the
user config (claude-omc/config.jsonc; omc config prints the
effective values), collect up to three distinct provider families in
canonical role order, and fill remaining seats from the default
families — claude, codex, gemini — not already seated; with no routing
config, use
OMC_TEAM_WORKTREE_MODE=detached omc team --no-decompose 1:claude,1:codex,1:gemini "<brief>".
Worktree isolation must be on — an unset mode resolves to disabled
and all candidates would share one checkout — and --no-decompose
keeps every candidate on the same brief instead of splitting a
multi-point brief across workers (one writer per worktree).
Use diverse models when the work is judgment-sensitive; the same model N
times when it is generation-bound.Spawn all candidates in one message, in the background, each with the brief, its output location, and instructions to return the artifact plus a short rationale naming the alternatives it considered and rejected. If a candidate produces nothing, proceed with N-1 and note the dropout. Keep at least two candidates: when dropouts leave fewer, spawn replacements — each on a remaining candidate's model, or on the parent's model when none remain — until two produce artifacts, and say so.
After all candidates finish, spawn one read-only judge on a model from a provider family none of the candidates ran on. If that dispatch is rejected, fall back down the remaining cross-family models; when no cross-family dispatch runs, skip the judge, pick the base alone in Phase D, and say so. If you cannot tell which family the candidates ran on, try the models you would have picked and name in the verdict that the family check did not run. The judge sees the rubric and the candidates by path label, scores each criterion, and recommends a base with rationale. It runs while you read.
Read every candidate end to end. Score each against the rubric criterion by
criterion, not on holistic feel, and compare with the cross-judge when
Phase C ran one. Agreement
on the base confirms the pick; disagreement means one of you is biased or the
rubric is ambiguous — read both rationales before deciding. Tie-break toward
the smaller API and the cleaner boundary (minimal-code-discipline).
Walk each losing candidate once more for what is worth porting — usually one or two things, not most of it. Fold grafts in by hand so the result stays coherent under one mental model. Candidates that converge on one shape are strong agreement: note it and ship the consensus shape. Candidates that wildly diverge mean Phase A was under-specified: reframe and rerun rather than averaging the divergence.
Verify the synthesized artifact under the verify skill protocol — real
command output, fresh evidence. A problem the arena missed means either the
rubric was wrong (reframe and rerun) or a graft was missed (back to Phase E).
Do not paper over it.
review judges the synthesized artifact, not the candidates.Yeachan-Heo/oh-my-claudecode
453d3de
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.