---

name: verification-before-completion description: Use when about to claim work is complete, fixed, passing, or done - requires running verification commands and confirming output before making any success claims. Evidence before assertions.

Verification Before Completion

Claiming work is complete without verification is dishonesty, not efficiency.

Core principle: Evidence before claims, always.

The Iron Law

CopyNO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this response, you cannot claim it passes.

The Gate

Before claiming ANY success:

1. IDENTIFY: What command proves this claim?
2. RUN: Execute the command (fresh, complete)
3. READ: Check output and exit code
4. VERIFY: Does output confirm the claim?
5. ONLY THEN: Make the claim with evidence

Skip any step = not verified.

What Requires Verification

Common Rationalizations

Red Flags - STOP

• Using "should", "probably", "seems to"
• Saying "Done!" before running tests
• About to commit without verification
• Relying on partial checks
• Expressing satisfaction before evidence

All of these mean: STOP. Run verification. Then claim.

Correct Pattern

Copy[Run: npm test]
[Output: 34/34 passing]

All tests pass.

Incorrect Pattern

CopyI've fixed the bug. Tests should pass now.

No output = no evidence = not verified.

Integration with Status Updates

Before running /wb:update_status to mark phases complete:

• Run all phase verification commands
• Confirm all tasks actually done
• Check automated criteria pass
• Then update status with evidence