verification-before-completion

Enforce verification before completion by identifying a verification command, running it fresh, reading the full output, and verifying the results with explicit evidence. This structured process prevents premature completion claims by requiring fresh proof for tests, builds, or bug fixes.

A verification gate is an explicit evidence checkpoint required before stating a development task is successful. You need it for tests, builds, linting, issue resolution, or any feature delivery where completion must be proven with fresh results rather than assumptions.

Verify a bug fix by following a checklist-driven validation process: identify the relevant test command, run it fresh, read the complete output, and confirm the results with explicit evidence before declaring the issue resolved. This ensures the fix is proven with fresh data.

Yes, a completion checklist works for build and linting verification by applying a four-step process: identify the verification command, run it, read the full output, and verify the results with explicit evidence. This ensures trustworthy results across applicable development scenarios.

Task completion lacks trustworthy evidence when verification steps are skipped or stale results are used. Solving this requires a structured validation process that gathers fresh evidence by identifying a command, running it, reading the output, and verifying the results explicitly.

The best way to prove feature delivery is to use a verification gate that requires explicit evidence before declaring success. Identify the appropriate verification command, run it fresh, read the full output, and verify the results to ensure completion is backed by fresh results.