evaluator

Installation
SKILL.md

Evaluator Protocol

Separate the agent doing work from the agent judging it. This is more tractable than making one agent self-critical.

When to Invoke

The orchestrator calls the evaluator in these situations:

  1. Post-subagent, pre-merge — after implementation passes mechanical gates AND either:
    • Browser-qa is available (CDT MCP connected + app running) — runtime evaluation
    • Acceptance criteria require runtime testing ("user can...", "page shows...", "form validates...")
  2. On-demand — evaluate <bead-id> to test an existing feature against its criteria
  3. Post-merge — /dm-work:post-merge runs evaluator against closed beads

Skip evaluator when:

  • XS/S tasks without acceptance criteria
  • Intent review returned COVERAGE: full, DRIFT: none, GAPS: none AND no browser-qa available
  • Bead has no acceptance criteria (report to orchestrator, don't run empty evaluation)
  • Task has no bead (ad-hoc work)
Installs
2
GitHub Stars
2
First Seen
Apr 7, 2026