Verification Before Completion
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.
30-Second Summary
Verification Before Completion is an agent-readable workflow from obra/superpowers for verification before completion.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating verification before completion as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Verification Before Completion packages instructions from obra/superpowers into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around verification before completion and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match verification before completion, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to obra/superpowers. Risk boundary: git state, commit, branch, PR, or push actions require explicit repo-owner approval before mutation.