verification-before-completion

name	verification-before-completion
description	Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.
user-invocable	false

Verification Before Completion

The Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you have not run the verification command in this turn, you cannot claim it passes. The superpowers-evaluator reads narration and runs commands independently — your unverified "done" can be waved through unless it self-evidences.

Violating the letter of this rule is violating the spirit of this rule.

The Gate Function

Run this before claiming any status, expressing satisfaction, or returning a PASS-shaped verdict to the coordinator:

1. IDENTIFY — What command proves this claim? (the task file's ## Verification Commands)
2. RUN — Execute the FULL command, fresh, in this turn. Not a previous run, not "should pass".
3. READ — Full output, check exit code, count failures. Last 20-30 lines pasted into your return.
4. VERIFY — Does the output confirm the claim?
   • NO → state the actual status with evidence (exit code, failure count)
   • YES → state the claim WITH evidence (exit 0, N/N pass)
5. ONLY THEN make the claim.

Skipping any step is lying, not verifying.