What problem does it solve?
Claiming work is complete without fresh, explicit verification leads to false positives, rework, and broken trust. This skill enforces a strict protocol: you must run and confirm verification commands before making any success claims, ensuring that every assertion is backed by evidence.
Core Features & Use Cases
- Evidence-Based Claims: Mandates running the full, fresh verification command and reading its output before stating any status.
- Iron Law Enforcement: Strictly prohibits any completion claims without preceding verification evidence.
- Rationalization Prevention: Identifies and counters common excuses for skipping verification, such as "should work now" or "I'm confident."
- Use Case: Before committing a bug fix, this skill requires you to run the specific test that reproduces the bug, confirm it now passes, and only then can you claim the bug is fixed.
Quick Start
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim? (e.g., npm test)
2. RUN: Execute the FULL command (fresh, complete).
3. READ: Full output, check exit code, count failures.
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence.
- If YES: State claim WITH evidence.
5. ONLY THEN: Make the claim.