run-evals
Eval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 290
- Forks
- 24
01 前言 Front Matter
- name
- run-evals
- model
- sonnet
- description
- Eval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.
03 SKILL.md 正文
Run Evals
HARD GATE — Define evals before implementation. Code graders = runnable
verify:commands; model graders = explicit rubric with pass/fail criteria.
Process
-
Name the capability under test (one sentence).
-
Write
specs/EVALS-<feature>.mdwith:- Capability evals (does it do the job?)
- Regression evals (did we break anything?)
-
Assign grader type per eval:
code(shell verify) ormodel(rubric). -
Assign strictness tier per eval (graduated promotion — e45s37):
Tier Meaning Promotion rule EXPERIMENTALNew eval, may flake Not gating USUALLY_PASSESStable in dev; ≥2/3 recent runs pass Blocks BUILD only when combined with ALWAYS_PASSES suite ALWAYS_PASSESZero tolerance; required for release Any single failure blocks BUILD and merge Promote:
EXPERIMENTAL → USUALLY_PASSESafter 3 consecutive passes;USUALLY_PASSES → ALWAYS_PASSESafter 5 consecutive passes with zero flakes documented inspecs/state.yaml. -
Run evals; log results table with pass@k (e.g. 3/3 runs) and tier per eval.
-
Block BUILD phase until all
ALWAYS_PASSESevals pass at agreed k.USUALLY_PASSESfailures warn;EXPERIMENTALfailures log only.
Artefact
specs/verifications/eNNsYY-eval-report.md — see REFERENCE.md for template. Eval reports are stored alongside verification evidence in specs/verifications/, keyed by story ID for traceability.
Verify
→ verify: test -d specs/benchmarks && test -f specs/benchmarks/SCHEMA.md
<!-- story: e02s01 -->
Run Evals — Reference
Strictness tiers (e45s37)
Add a tier: column to each eval row:
| Tier | Gate behaviour |
|---|---|
EXPERIMENTAL |
Log only — does not block |
USUALLY_PASSES |
Warn on failure; blocks only when paired with failing ALWAYS_PASSES |
ALWAYS_PASSES |
Hard block on any failure |
EVALS template
# EVALS: <feature>
## Capability
| ID | Eval | Grader | Tier | verify / rubric |
|----|------|--------|------|-----------------|
| C1 | ... | code | ALWAYS_PASSES | `verify: npm test -- <file>` |
| C2 | ... | model | USUALLY_PASSES | Rubric: [ ] criterion A [ ] criterion B |
## Regression
| ID | Eval | Grader | verify / rubric |
|----|------|--------|-----------------|
| R1 | Full suite passes | code | `verify: npm test` |
## Results
| Run | C1 | C2 | R1 | pass@k |
|-----|----|----|-----|--------|
| 1 | PASS | PASS | PASS | 3/3 |
pass@k
Run capability evals k times (default k=3). Ship when all k pass or document known flake in specs/state.yaml handoff.open_decisions.
04 同仓库更多 Skills
skill-verify-fail-open-fixture
Negative-path fixture for run-skill-verify.sh — must never PASS.
negative-path
暂无简介
write-document
Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.
wire-observability
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
wire-ci
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
visual-dashboard
Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.