36 lines
1.3 KiB
Markdown
36 lines
1.3 KiB
Markdown
---
|
|
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
|
|
|
|
- Include exact commands run.
|
|
- Include pass/fail outcomes and key output.
|
|
- Tie evidence to each acceptance condition.
|
|
|
|
## Role Expectations
|
|
|
|
- Builder and tester: no completion claim without concrete verification evidence.
|
|
- Reviewer: reject completion claims that are not evidence-backed.
|
|
- Coder: point to verification evidence from assigned lane before signaling done.
|
|
|
|
## If Verification Fails
|
|
|
|
- Do not claim partial completion as final.
|
|
- Return to debugging or implementation with updated hypotheses.
|