verification-before-completion

You can enforce evidence-based verification by applying a mandatory completion gate that requires fresh, acceptance-mapped data. This prevents premature completion claims by ensuring all behavior-changing work is verified against established acceptance criteria before finalization.

Acceptance-to-evidence mapping links each completion claim to fresh, verifiable data that directly satisfies established acceptance criteria. This mechanism ensures work is validated against actual results rather than stale or unverified outputs before final approval.

A mandatory risk assessment is required to identify potential regressions or uncovered edge cases before finalization. Integrating this risk check into your quality assurance workflow ensures behavior-changing tasks are properly evaluated for completion.

Yes, subagent-based review coordinates independent verifier and code-reviewer agents to audit task scope and validate completion claims. This role-based approach ensures behavior-changing work meets quality standards before being marked as done.

An evidence gate is not necessary for trivial tasks that do not change system behavior. You should apply this verification workflow exclusively to behavior-changing tasks requiring independent audit, risk assessment, and acceptance mapping.