# Evals — project-ops

`cases.yaml` is a routing + capability harness, not an automated test runner. To run it, feed each `should_trigger` prompt to the skill router and confirm `project-ops` loads, then feed each `should_not_trigger` prompt and confirm the router instead routes to the named sibling (`tasks`, `plan`, `decision-records`, `meeting-notes`, `sop-builder`, `dashboard`). For the `capability` case, give the scenario to an agent with this skill loaded and grade the resulting transcript by hand against the `must_include` rubric — each bullet is pass/fail. Separately, you can run `scripts/verify.sh` against a produced milestone file to confirm the structural contract holds (unique ids, one owner, parseable date, allowed status, non-empty done-test, resolvable depends_on); it exits 0 on a clean or empty target.
