Use when about to claim work is complete, fixed, passing, or successful, before committing or creating PRs - requires running verification commands and confirming output before making ANY success claims; evidence before assertions always, no exceptions
View on GitHubkrzemienski/shannon-framework
shannon
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/krzemienski/shannon-framework/blob/main/skills/verification-before-completion/SKILL.md -a claude-code --skill verification-before-completionInstallation paths:
.claude/skills/verification-before-completion/# 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.** ## 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 output confirm the claim? - If NO: State actual status with evidence - If YES: State claim WITH evidence 5. ONLY THEN: Make the claim Skip any step = lying, not verifying ``` ## Common Failures | Claim | Requires | Not Sufficient | |-------|----------|----------------| | Tests pass | Test command output: 0 failures | Previous run, "should pass" | | Linter clean | Linter output: 0 errors | Partial check, extrapolation | | Build succeeds | Build command: exit 0 | Linter passing, logs look good | | Bug fixed | Test original symptom: passes | Code changed, assumed fixed | | Regression test works | Red-green cycle verified | Test passes once | | Agent completed | VCS diff shows changes | Agent reports "success" | | Requirements met | Line-by-line checklist | Tests passing | | All validations pass | 3-tier validation output | Individual tiers passed separately | ## Shannon Enhancement: Validation Gates **Shannon-specific**: Projects have 3-tier validation gates: ### Tier 1: Flow Validation **Purpose**: Code compiles, dependencies resolve, syntax correct **Common commands**: - TypeScript: `tsc --noEmit` - Python: `ruff check .` or `flake8 .` - Go: `go vet ./...` - Rust: `cargo check` **Required output**: 0 errors, 0 warnings (zero tolerance) ### Tier 2: Artifact Validation **Purpose**: Tests pa