verification-before-completionlisted

<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Verification Before Completion ## Overview Claiming work is complete without verification is dishonesty, not efficiency. **Core principle:** Evidence before claims, always. **Violating the letter of this rule is violating the spirit of this rule.** ## Fits in the pipeline The completion gate enforced at the close of **Stage 6 (Build)**, throughout the **Stage 7 per-feature QA gate** (`/feature-check`), and at the **Stage 8 ship gate** (`/ship-check`). The Consistency & no-orphans section below is the teeth of principle #6 and is checked here AND at `/ship-check`. Priority: **user > skills > default**; `_shared/vibegod-principles.md` apply (#8 evidence-based completion only). ## The Iron Law ``` NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE ``` If you haven't run the verification command in this message, you cannot claim it passes. ## The Gate Function ``` BEFORE claiming any status or expressing satisfaction: 1. IDENTIFY: what command proves this claim? 2. RUN: execute the FULL command (fresh, complete) 3. READ: full output, check exit code, count failures 4. VERIFY: does the output confirm the claim? NO → state actual status with evidence YES → state the claim WITH evidence 5. ONLY THEN: make the claim Skip any step = lying, not verifying ``` ## Verify the Real Signal — Anti-Hallucination Rules (MANDATORY) A confident, well-argued conclusion c