criterion-verification-maplisted

Transform acceptance criteria into plan-time runnable verification commands (behavioral, API, UI, error, performance, config, data, contract types) with expected evidence shapes and risk areas, then execute at verify time and assemble the evidence bundle with its mandatory completeness subsections, including test inputs/expected values taken from test source and risk-map coverage. Use when planning implementation against issue acceptance criteria or verifying completeness. This skill MUST be consulted because deferring verification to later causes incomplete PRs, and suppressing evidence gaps prevents the verdict judge from reasoning about gaps.
synaptiai/synapti-marketplace · ★ 6 · AI & Automation · score 77

Install: claude install-skill synaptiai/synapti-marketplace

# Criterion Verification Map ## Contract Iron law: **every acceptance criterion is an eval source: at plan time it must produce a runnable verification command, or planning is blocked.** Invoked by `/flow:start` at the Spec Validation Gate and PLAN (Phases 1-2) to classify each criterion and emit the task's verification fields, and at VERIFY (Phase 4) to run them and assemble the evidence bundle shaped by [`references/evidence-bundle-format.md`](../../references/evidence-bundle-format.md). Returns task fields at plan time, the bundle at verify time. Permitted skips: none; an unmappable criterion is escalated through the Spec Validation Gate. ## Classification | Type | Signal words | Method | |---|---|---| | behavioral | "when X then Y", "should return" | unit/integration test | | api | "status code", "endpoint", "header" | curl/fetch | | ui | "displays", "renders", "layout" | screenshot + analysis | | error | "error message", "invalid", "fails gracefully" | invalid-input test | | performance | "within N ms", "timeout" | benchmark/timing | | config | "config", "setting" | build/load test | | data | "transforms", "output matches" | run with test data | | contract | "schema", "type", "signature" | validator / type-check | ## Plan-time task fields Tasks are atomic (`commands/start.md` Phase 2). Emit per criterion: ``` Criterion: {full criterion text} Verification type: {type from the table} Verification command: {exact runnable command} Expected evidence: {what successful