eval-driven-development

What problem does it solve?

Many teams modify agent rules, skills, or prompts without a reliable way to confirm that changes produce the intended behavior and do not introduce regressions.

Core Features & Use Cases

• Eval Definition: Write an expected behavior test before making a change.
• Baseline & Regression Checks: Run the eval against the current version to establish a pass/fail baseline, then re‑run after modifications.
• Capability Validation: Confirm new capabilities pass a configurable pass@k threshold.
• Use Cases: Adding a new rule, updating a prompt, or extracting a pattern via continuous learning where confidence in behavior is required.

Quick Start

Prompt the skill to create an eval for a new rule, run the baseline, apply the change, and verify the eval now passes.