verification-before-completion

Require the agent to run the actual verification command and quote its output before any completion claim. This Skill enforces a gate: identify the proving command, run it fresh, read the full output and exit code, then claim only what the evidence confirms.

Valid verification means running the full test suite, build, or linter in the current session and confirming zero failures from the actual output. Previous runs, partial checks, or assumptions like "should pass" do not qualify as evidence.

Use the red-green cycle: write the test, confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing about the regression.

No. Agent success reports are claims, not evidence. Independently verify by inspecting the version control diff and running the relevant verification commands before reporting the delegated work as complete.

Run verification before any success claim, expression of satisfaction, commit, pull request, task handoff, or move to the next task. The rule applies to exact phrases, paraphrases, and any implication that work is complete.