qa-verifylisted

# Verification Before Completion **Announce:** "I'm using enggenie:qa-verify to verify before claiming completion." ## Hard Rule: Don't say "done" until you've seen the proof. No "should work." No "probably passes." No "looks good." Run the command. Read the output. State the evidence. **Current-turn binding:** If you haven't run the verification command in THIS response, you cannot claim it passes. Previous turns don't count - state may have changed. ## The Verification Gate Before claiming ANYTHING is complete, follow this exact sequence: ``` 1. IDENTIFY - What command proves this claim? 2. RUN - Execute the FULL command. Fresh. Complete. Not partial. 3. READ - Full output. Exit code. Failure count. Warnings. 4. VERIFY - Does output actually confirm your claim? YES → State claim WITH evidence ("47/47 tests pass, exit 0") NO → State actual status ("3 failures in auth module") 5. ONLY THEN - Make the claim. ``` Claiming work is complete without verification is dishonesty, not efficiency. Skip any step and you're lying, not verifying. ## What Counts as Evidence | Claim | You need | Not sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures, exit 0 | "Should pass", previous run, partial run | | Build works | Build command: exit 0, no errors | "Linter passed" (linter is not compiler) | | Bug fixed | Original symptom gone + regression test passes | "Code changed, should be fixed" | | Feature complete | Every acce