superpowers-verification-before-completion

Enforces running verification commands before claiming work is complete or passing.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill superpowers-verification-before-completion-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-verification-before-completion
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/superpowers-verification-before-completion
Command: npx skills add https://github.com/avel123111/triplanio --skill superpowers-verification-before-completion-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is complete, tests pass, or bugs are fixed without actually running the verification commands, leading to broken code, lost trust, and wasted rework. This Skill enforces an evidence-before-claims discipline so no success statement is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a mandatory gate function requiring you to identify the proving command, run it fully, read the output and exit code, and only then make a claim. - Failure Pattern Catalog: Maps common claims (tests pass, linter clean, build succeeds, bug fixed) to the exact evidence required and what is not sufficient. - Rationalization Blocking: Lists red flags and common excuses ("should work", "just this once", "agent said success") with their rebuttals to prevent shortcut-taking. - Use Case: Before committing a bug fix, run the test suite, confirm zero failures in the output, verify the regression test fails without the fix, and only then report completion with the evidence attached. ## Quick Start Before claiming any task is done, run the relevant verification command and report the actual output alongside your claim.

Frequently Asked Questions about superpowers-verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify work is complete before committing code?

Identify the command that proves your claim, run it fresh and in full, read the complete output including exit code, and only then state the result with that evidence. Never claim success based on a previous run or assumption.

What counts as evidence that tests pass?

Only the output of a freshly run test command showing zero failures counts as evidence. Prior runs, partial checks, linter results, or confidence that the code should pass are explicitly not sufficient.

How do I verify a regression test actually works?

Use the red-green cycle: write the test, run it to confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that only passes once proves nothing.

Can I trust a sub-agent's report that a task succeeded?

No. Agent success reports must be independently verified by checking the version control diff and confirming the actual changes exist. Trusting an agent's self-report without verification is listed as a common failure mode.

Why is linter output not enough to claim a build succeeds?

Linters do not check compilation, so a clean lint run does not prove the build works. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.