Back

Verification Before Completion

Other269.2K installs

What it does

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Install

npx skills add https://github.com/obra/superpowers --skill verification-before-completion

Website

www.skills.sh/obra/superpowers/verification-before-completion

Details

From the skill’s SKILL.md or README, by its authors. View the original

Verification Before Completion

Overview

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

ClaimRequiresNot Sufficient
Tests passTest command output: 0 failuresPrevious run, should pass
Linter cleanLinter output: 0 errorsPartial check, extrapolation
Build succeedsBuild command: exit 0Linter passing, logs look good
Bug fixedTest original symptom: passesCode changed, assumed fixed
Regression test worksRed-green cycle verifiedTest passes once
Agent completedVCS diff shows changesAgent reports success
Requirements metLine-by-line checklistTests passing

Red Flags - STOP

  • Using should, probably, seems to
  • Expressing satisfaction before verification (Great!, Perfect!, Done!, etc.)
  • About to commit/push/PR without verification
  • Trusting agent success reports
  • Relying on partial verification
  • Thinking just this once
  • Tired and wanting work over
  • ANY wording implying success without having run verification

Rationalization Prevention

ExcuseReality
Should work nowRUN the verification
I'm confidentConfidence ≠ evidence
Just this onceNo exceptions
Linter passedLinter ≠ compiler
Agent said successVerify independently
I'm tiredExhaustion ≠ excuse
Partial check is enoughPartial proves nothing
Different words so rule doesn't applySpirit over letter

Key Patterns

Tests:

✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"

Regression tests (TDD Red-Green):

✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)

Build:

✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)

Requirements:

✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"

Agent delegation:

✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report

When To Apply

ALWAYS before:

  • ANY variation of success/completion claims
  • ANY expression of satisfaction
  • ANY positive statement about work state
  • Committing, PR creation, task completion
  • Moving to next task
  • Delegating to agents

Rule applies to:

  • Exact phrases
  • Paraphrases and synonyms
  • Implications of success
  • ANY communication suggesting completion/correctness
See all
  • Other

    Implement a piece of work based on a spec or set of tickets.

    npx skills add https://github.com/mattpocock/skills --skill implement
    843.9K installs
  • Other

    Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

    npx skills add https://github.com/mattpocock/skills --skill to-spec
    785.9K installs
  • Other

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    npx skills add https://github.com/mattpocock/skills --skill to-questionnaire
    559.8K installs
  • Other

    Stop. That last message did not land: re-pitch it.

    npx skills add https://github.com/mattpocock/skills --skill wait-what
    511.1K installs

Skills are shared by members and not reviewed by us. Read a skill’s code before you install it.