Menu
Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.
| name | verification-before-completion |
| version | 6.2.0 |
| category | workflow |
| description | Use when about to claim work is complete, fixed, passing, or ready to integrate. Do NOT use to repeat checks without a completion claim or concrete doubt. |
Claims require fresh evidence from the current state.
Read ../using-superpowers/references/risk-policy.md.
Before a completion claim:
The complete command means the complete chosen check, not the entire repository suite. Verification scope follows risk.
| Claim | Evidence |
|---|---|
| Focused behavior works | affected test or reproducible smoke path |
| Build succeeds | build command exits 0 |
| Bug is fixed | original reproduction no longer fails |
| Plugin is installed | plugin listing shows expected source and version |
| Requirements are met | final diff checked against the approved scope |
Do not substitute old output, a reviewer summary, lint for a build, or tests for an untested user-visible boundary.
If verification fails, report the actual state. Do not soften it into a success claim.
