Skills Library
Skill Pack
Never claim completion without fresh verification evidence
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the command in THIS message, you cannot claim it passes.
Before claiming ANY success:
1. IDENTIFY → What command proves this claim?
2. RUN → Execute the FULL command
3. READ → Full output, check exit code
4. VERIFY → Does output confirm the claim?
5. CLAIM → Only now, with evidence
Skip ANY step = lying, not verifying.
| Claim | Requires | NOT Sufficient |
|---|---|---|
| "Tests pass" | Test output: 0 failures | "Should pass", previous run |
| "Build works" | Build output: exit 0 | Linter passing |
| "Bug fixed" | Test of original symptom | "Code changed" |
| "Linter clean" | Linter output: 0 errors | "Looks right" |
| "Feature complete" | All requirements checked | "Tests pass" |
If you catch yourself:
STOP. Run the verification.
| You Think | Reality |
|---|---|
| "Should work now" | RUN IT |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ tests |
| "I'm tired" | Exhaustion ≠ excuse |
Tests:
✅ [run test] → See "34/34 pass" → "All tests pass"
❌ "Tests should pass now"
Build:
✅ [run build] → See "exit 0" → "Build passes"
❌ "Build looks good"
Requirements:
✅ Re-read requirements → Check each → Report gaps
❌ "Tests pass so it's complete"
From actual failures:
Run the command. Read the output. THEN claim the result.
This is non-negotiable.