arenalisted
Install: claude install-skill ychampion/ystack
# Arena
When there are several reasonable ways to do something, a single attempt picks one of them by
accident. An arena tries a few on purpose, judges them on the same test, and keeps the best parts.
## When it applies
- The result depends on choices more than on effort: an algorithm, an API shape, a data model, a UI
layout, a prompt, a piece of copy.
- An earlier attempt came back mediocre and it's not clear why.
- The work is small enough that 2-4 copies are affordable.
Skip it for mechanical work (a rename, a known fix, a dependency bump), where every attempt converges
on the same answer and the arena only multiplies cost.
Say the cost before starting: N attempts cost roughly N times one attempt, plus judging.
## Procedure
### 1. Write the spec and the acceptance check first
Both are shared by every attempt and written before any attempt starts:
- the spec: what to build, inputs and outputs, constraints, what's out of scope;
- the check: something that runs and scores. Tests that must pass, a benchmark with a target, a
screenshot compared at three widths, a rubric with numbered criteria for copy. If the check can't
tell the attempts apart, sharpen it before going on.
### 2. Make the attempts different on purpose
Identical briefs to identical models give near-identical results. Vary one thing per attempt:
- the approach ("use a state machine", "use a lookup table", "stream it");
- the model or model family;
- the priority ("simplest that passes", "fastest