verification-before-completion

name	verification-before-completion
description	Use before any completion or fix claim to bind the final claim to fresh proof, required runtime evidence, review coverage, and residual risk.

Verification Before Completion

Owns final completion claim gating. Review approval scope, runtime verdicts, and platform mechanics stay with their owner skills.

Completion claims require fresh proof against the binding objective before saying work is fixed, done, ready, or approved.

Rule

The final claim cannot exceed the binding objective, accepted reductions, owner-skill intake, adequacy re-check, fresh proof, required runtime evidence, and review coverage.

Broad product-facing UI design readiness also requires design_judge pass covering the same screenshots/contact sheets, declared project design source, project design source requirements, applicable project-local artifacts, states, viewports, and devices as the final claim.

Compare completion to the original objective plus accepted reductions, not to the implemented slice, diff summary, reviewer prompt, or handoff wording.

Required References

• Read ../runtime-proof/SKILL.md when the claim is runtime-visible, uses runtime evidence, or needs entrypoint fidelity.
• Read ../just-recipe-routing/SKILL.md when choosing quality or proof commands.
• Read ../code-review/SKILL.md when review coverage or approval scope matters.
• Read ../user-apps-design/SKILL.md when product UI design readiness is part of the claim.

Gate

Before completion:

1. name the binding objective and accepted reductions
2. name the exact final claim
3. confirm owner-skill intake is complete and current for the final claim
4. re-check adequacy against the touched owner/component and binding objective
5. run fresh owner-selected proof
6. include runtime evidence when the claim includes non-trivial runtime-visible behavior that needs it
7. include design_judge pass when broad product UI design is claimed
8. confirm required review is valid and covers the same claim
9. report residual risks or none

Stop

Stop or narrow the claim when:

• owner-skill intake is missing, stale, or narrower than the claim
• adequacy re-check is missing, stale, or says the touched owner/component remains inadequate for the binding objective
• proof is stale, missing, indirect, or narrower than the claim
• runtime evidence is required but missing, rejected, blocked, incomplete, or mis-scoped
• broad product UI design readiness is claimed but design_judge is missing, rejected, blocked, stale, or narrower than the claim
• tests, code review, or approval history are offered as substitutes for required runtime evidence
• runtime evidence is offered as a substitute for broad product UI design approval
• review rejected, is invalid, or did not cover the binding objective
• residual gaps belong to the current objective

Completion Note

Report proof command or artifact, runtime verdict when applicable, review status when required, and residual risks or none.