verification-before-completion

To enforce task verification, apply a mandatory protocol requiring specific validation commands to be executed and independently reviewed before any success claims are communicated, ensuring evidence-based reporting.

The best way to prevent rationalizing skipped testing steps is to implement a strict verification gate that provides a framework to identify and stop common excuses for skipping validation before task completion.

To verify passing tests and builds before submitting a pull request, identify the specific command that proves your work is finished, execute it, and confirm the output meets requirements before updating task status.

You need evidence-based reporting in software development workflows whenever marking a task as done or submitting work, applying to project management and agentic workflows where output accuracy and reliability are required.

Yes, this verification protocol works for project management tasks without dependencies, as it applies a general framework requiring the execution and review of validation commands across various workflows before completion.