criterion-verification-maplisted

# Criterion Verification Map Domain skill that treats acceptance criteria as **eval sources**. Each criterion produces a concrete, runnable check at plan time — not at verify time. Planning a criterion without a runnable command is a blocking error. ## Iron Law **EVERY ACCEPTANCE CRITERION IS AN EVAL SOURCE.** At plan time, each criterion must produce a runnable verification command. No criterion is deferred to verify time with "we'll figure out how to test this later." No criterion passes by assumption. No criterion is "too obvious to verify." ## Criteria as Eval Sources (Plan Time) An acceptance criterion is useful only if it can be evaluated mechanically. At plan time, the criterion must be transformed into: 1. **A verification type** (classification — see table below) 2. **A runnable command** (the exact bash/test/curl/script invocation that will be executed at verify time) 3. **Expected evidence shape** (what the command's output must contain to count as PASS) 4. **What the criterion does NOT promise** (non-goals scoped to this criterion — prevents scope creep and false-positive verdicts) If any of the four cannot be filled in at plan time, the criterion is not ready. Escalate through the Spec Validation Gate in the `start.md` EXPLORE phase, not here. ### Criterion Classification Table | Criterion Type | Signal Words | Verification Method | Evidence Format | |---------------|-------------|-------------------|-----------------| | Behavioral (logic) | "when X then