This file is byte-identical to the first copy the registry indexed, one of 8 indexed copies. Same content hash, so the same checks give both the same grade.
verification-before-completion from autovant/superpowers is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 |
…
The line at the top of this page pins the label git:20251017.48410c7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ms2q5bbjopzadypp
GET https://markdownregistry.com/api/v1/resolve?ref=autovant/superpowers/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/ea52d15aabaf72bc6b558efe2c126f161b53961090ddcd712000273bfe8c7b6c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
autovant/superpowers · skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
autovant/superpowers · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
autovant/superpowers · skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
autovant/superpowers · skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides…
autovant/superpowers · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
autovant/superpowers · skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
autovant/superpowers · skills/subagent-driven-development/SKILL.md · Use when executing implementation plans with independent tasks in the current session
autovant/superpowers · skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
autovant/superpowers · skills/using-git-worktrees/SKILL.md · Use when starting feature work that needs isolation from current workspace or before executing implementation plans -…
autovant/superpowers · skills/using-superpowers/SKILL.md · Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY…
obra/superpowers · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
mvschwarz/openrig · skills/_canonical/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
a5c-ai/babysitter · library/methodologies/superpowers/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before…
a5c-ai/babysitter · library/methodologies/cc10x/skills/verification-before-completion/SKILL.md · Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success…
ganyuanran/aegis · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish…
coco-research/coco · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
