Verification Before Completion
Run the verification and read its output before claiming work is complete, fixed, or passing — evidence first, claim second. Use before any completion claim, commit, PR, or harvest.
Install
$ agentstack add skill-skywalkercyt-mp-implement-verification-before-completion ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-skywalkercyt-mp-implement-verification-before-completion) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Verification Before Completion
> Adapted skill — discipline originating in Superpowers v5.1.0 (MIT, Jesse Vincent), rewritten in mattpocock-skills style. The honesty gate in /mp-implement-issue step 7 and both pipelines' harvest — no slice counts as done until it passes.
Iron law: no completion or success claim without fresh verification evidence produced in this step. A claim made before its verification is a guess dressed as a fact.
The gate
For each claim you are about to make:
- Name the command that proves it.
- Run that command in full — fresh, in this step.
- Read the complete output and the exit code.
- If the output confirms the claim, make the claim and quote the evidence ("34/34 pass", "exit 0"). If it contradicts the claim, state the actual status with the evidence instead.
Evidence means output from the run you just did. "Should pass", an earlier run, a partial check, a linter where tests are owed, or another agent's self-report are not evidence — a sub-agent's "success" is a lead to verify (check the diff), not a result.
Regression tests
A regression test proves red-green: revert the fix and watch the test fail, restore the fix and watch it pass. A test that never failed proves nothing about the fix.
Requirements
"Tests pass" is not "requirements met". Close out by re-reading the source checklist (issue, spec, plan) and verifying each requirement line by line; report any gap as its actual status.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: skywalkercyt
- Source: skywalkercyt/mp-implement
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.