# Evals — proposals

`cases.yaml` holds three things: `should_trigger` (prompts that must route into this skill, including a non-obvious "why isn't this closing" diagnostic and Spanish/Catalan phrasings), `should_not_trigger` (prompts that belong to a named sibling — `contracts`, `pricing`, `pitch-deck`, `invoicing`, `sales-pipeline`, `cold-outreach`), and one `capability` scenario with a `must_include` rubric. There is no automated runner here: route the trigger prompts through your skill-selection harness and confirm each lands (or doesn't) as labelled, then have an agent run the capability scenario and score the output against the rubric by hand — every `must_include` line should be present and pass. To sanity-check a generated proposal/SOW structurally, run `../scripts/verify.sh <draft.md>`; a clean rubric pass plus a clean verify run is the bar.
