Essentials
Verify Before Claiming Done
Listed under Software DevelopmentBug Fixing
Summary
Before claiming done, passing, or merge-ready, require running verification commands and reading full output—evidence first. Input is the claimed status; output is a status note with evidence. Suited to regression and close-out checks.
Why we picked it Why recommended
SkillPouch records why this skill was curated, stage by stage.
-
T14.s3Regress & check
Demands fresh verification evidence before stating regression conclusions and fix notes.
How to use Applicable stages
Use it in these workflow stages. Open a stage to return to its task.
Get and review
App deep-link installation is coming soon. Open the upstream repository to inspect the skill today.
Check the sources Evidence & sources
Public links you can open and verify on your own.
Upstream source
- Upstream repository (obra/superpowers) ↗ Verified on 2026-10-28
Boundaries Known limitations
Verification commands must be defined by task context; skipping any step counts as unverified. Does not replace release-approval process.
Identity and license
License, review date, repository path, and stable identifier.