verification-before-completion

Verification before completion requires executing the full test command, inspecting complete output, and confirming results only when evidence passes. This prevents premature success claims by enforcing fresh verification at each stage of your build and testing workflow.

Implement a verification gate that identifies what to test, runs the complete command, reads all output thoroughly, validates results match claims, and only marks completion when fresh evidence confirms success. This five-step process catches false positives before they propagate.

Builds fail post-claim when verification skips inspection of complete output or relies on partial evidence. Enforcing fresh verification of full command execution and concrete test results before any completion claim eliminates gaps where failures hide.

Structure validation by identifying acceptance criteria, running all required tests end-to-end, reading the full output without skipping sections, verifying results against criteria, then claiming completion only when evidence is concrete and fresh.

Yes. Verification before completion gaps your test suite by requiring manual inspection of complete output, not just pass/fail status. Reading full results identifies edge cases, warnings, and partial failures that automated checks may overlook.