---
name: verification-before-completion
description: Require evidence-backed verification before completion claims or final handoff
permalink: opencode-config/skills/verification-before-completion/skill
---

# Verification Before Completion

Use this skill before declaring work done, handing off, or approving readiness.

## Verification Checklist

1. Re-state the promised outcome and scope boundaries.
2. Run the smallest reliable checks that prove requirements are met.
3. Run broader regression checks required by project workflow.
4. Confirm no known failures are being ignored.
5. Clean up temporary artifacts generated during work (e.g., scratch files, screenshots, logs, transient reports, caches). Intended committed deliverables are not cleanup targets.
6. Report residual risk, if any, explicitly.

## Evidence Standard

Use the compact verification summary shape for every evidence entry:

- **Goal** – what is being verified
- **Mode** – `smoke` (intermediate checkpoints) or `full` (final completion)
- **Command/Check** – exact command or manual check performed
- **Result** – `pass`, `fail`, `blocked`, or `not_run`
- **Key Evidence** – concise proof (output snippet, hash, assertion count)
- **Artifacts** – paths to logs/screenshots, or `none`
- **Residual Risk** – known gaps, or `none`

Keep raw logs out of primary context by default. When a check fails, summarize the failure first and then point to the raw evidence. Include full output only when explicitly requested.

Tie each evidence entry to an acceptance condition from the plan.

## Role Expectations

- Builder and tester: no completion claim without verification evidence in the compact shape above.
- Reviewer: reject completion claims that lack structured evidence or lane-ownership boundaries.
- Coder: include compact-shape verification evidence from the assigned lane before signaling done.

## If Verification Fails

- Do not claim partial completion as final.
- Return to debugging or implementation with updated hypotheses.
