What problem does it solve?
Eval-driven development needs a repeatable way to define expected behavior, run checks, and detect regressions in Claude Code sessions instead of relying on subjective impressions of quality.
Core Features & Use Cases
- Capability Evals: Verify Claude can complete specific new tasks and meets explicit success criteria, making improvements measurable.
- Regression Evals: Ensure changes do not break existing workflows by comparing results against a known baseline.
- Multiple Grader Modes: Support deterministic code-based checks, model-based rubric scoring, and optional human adjudication for ambiguous or sensitive outcomes.
Use Case Examples: benchmarking agent reliability across model versions, creating prompt or agent change regression suites, and producing structured reports with pass@k and pass^k metrics for release readiness.
Quick Start
Create an eval definition for a feature, then run and report results with the commands: /eval define feature-name, /eval check feature-name, and /eval report feature-name.