provelisted

# /prove — Completion Proof (report-only) **Trigger:** `/prove` (alias of /5's finderSet, run standalone) · `/prove --selftest` **Channel:** CT=`CURRENT_TASK_chN.md` (channeled) or `CURRENT_TASK.md`. Full rules: `.claude/reference/channel-routing.md`. The engine + gate + finderSet live in `.claude/reference/adversarial-loop.md`; the opt-in schema in `.claude/reference/workflows-config.md`. This skill is the thin spine. --- ## Standalone mode ### Scope resolution Resolve scope identically to `/5`: CTs (channeled `CURRENT_TASK_chN.md` or shared `CURRENT_TASK.md`) + "diff since session start" (`git diff` of the working tree relative to the last commit at session open) + the plan pointer embedded in the channel CT. "The plan" = the plan file the CT references. This resolver is **shared with `/5`** — both skills call the same procedure. The build is DRY: no separate `/prove`-only resolution logic. ### MD-15 — No-CT pre-flight error **MD-15:** When no CT resolves and no plan pointer is found, emit a PRE-FLIGHT ERROR and stop: ``` PROVE ERROR: no scope resolved. No CURRENT_TASK_chN.md or CURRENT_TASK.md found, and no plan pointer was located. An empty scope finds nothing and would produce a false CLEAN. Provide a CT or plan pointer before running /prove. ``` Do NOT run the engine on an empty scope. (Exception: `--selftest` mode uses a synthetic fixture and explicitly bypasses this check — see below.) ### MD-16 — No-change short-circuit ("run once") **MD-16:** Before in