verification-before-completion

Evidence-based completion claims require running explicit verification commands and confirming successful output before proceeding. This structured approach ensures all tests, linters, and builds pass before you assert project completion.

Evidence-based project completion verification is a quality control process requiring concrete proof of success before making claims. It involves executing commands, interpreting output, and addressing failures to ensure accuracy in project management.

Handle verification failures by following detailed error handling instructions that identify and address common issues like empty prompts or missing requirements. This ensures you resolve blockers before making any completion claims.

The best way to enforce quality control before a code commit is to implement a rigorous verification process with a checklist of steps. This confirms all tests and regression checks pass, fostering a culture of honesty and accuracy.

Claiming project completion without verification causes problems because it allows untested code and errors to slip through. Rigorous checks ensure all assertions are backed by evidence, preventing inaccurate or dishonest status reporting.