benchmark

# Benchmark — progress-ceiling verdict gate The **benchmark** gate, part of `/spec execute`'s improve tail in `AGENTS.md § The Workflow`. It answers one question: *was this change actually beneficial — did it move or hold the capability ceiling without breaking the regression floor, and is it worth its complexity?* — and emits exactly one verdict. **Core principle: compose, don't re-derive — and judge OUTCOMES, not machinery.** This skill owns the *verdict*, not the instruments. The regression floor is `/eval`; the progress ceiling is the capability benchmark (`.oh/evals/capability/`). `/benchmark` runs both and integrates them into a single `BENEFICIAL` / `NOT-BENEFICIAL`. *Adding machinery is not progress* — a change that grows the harness but does not move the capability benchmark is `NOT-BENEFICIAL` **by definition**. > **Not `/audit implementation`.** `/audit implementation` is the per-unit *floor* gate (does this one impl > satisfy its task graph and is it promotable?). `/benchmark` is the *ceiling* > gate (did the harness get **better**?). Distinct instruments, distinct > question — see `.oh/evals/capability/README.md` § *Ceiling vs. floor*. `/benchmark` > *consults* `/eval`; it does not replace or fork it. --- ## Inputs | Arg | Meaning | |-----|---------| | `--base <ref>` | The counterfactual to score against — the state *without* this change. Defaults to the merge-base with `development` (i.e. "the repo before this change"). | | `--cycles <N>` | Window for the ...