changes

.config/opencode/skills/verification-before-completion/SKILL.md

@@ -1,47 +1,34 @@
 ---
 name: verification-before-completion
-description: Require fresh verification evidence before any completion or success claim
+description: Require evidence-backed verification before completion claims or final handoff
 permalink: opencode-config/skills/verification-before-completion/skill
 ---
 
-## When to Load
+# Verification Before Completion
 
-Load this skill immediately before claiming work is complete, fixed, or passing.
+Use this skill before declaring work done, handing off, or approving readiness.
 
-## Core Rule
+## Verification Checklist
 
-```
-NO COMPLETION OR SUCCESS CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
-```
+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. Report residual risk, if any, explicitly.
 
-If you did not run the relevant verification command for this change, do not claim success.
+## Evidence Standard
 
-## Verification Gate
+- Include exact commands run.
+- Include pass/fail outcomes and key output.
+- Tie evidence to each acceptance condition.
 
-Before any completion statement:
+## Role Expectations
 
-1. **Identify** the exact command that proves the claim.
-2. **Run** the full command now (no cached or earlier output).
-3. **Check** exit code and output details (failure count, errors, warnings as relevant).
-4. **Report** the result with concrete evidence.
-   - If verification fails, report failure status and next fix step.
-   - If verification passes, state success and include proof.
+- 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.
 
-## Common Proof Examples
+## If Verification Fails
 
-- **Tests pass** → fresh test run shows expected suite and zero failures.
-- **Lint is clean** → fresh lint run shows zero errors.
-- **Build succeeds** → fresh build run exits 0.
-- **Bug is fixed** → reproduction scenario now passes after the fix.
-- **Requirements are met** → checklist is re-verified against the implemented result.
-
-## Anti-patterns
-
-- "Should pass" / "probably fixed" / "looks good"
-- claiming completion from partial checks
-- relying on old command output
-- trusting status reports without independent verification
-
-## Bottom Line
-
-Run the right command, inspect the output, then make the claim.
+- Do not claim partial completion as final.
+- Return to debugging or implementation with updated hypotheses.