verification-before-completion

Evidence-based validation requires executing specific verification commands and analyzing their output to confirm state changes before declaring task completion. This mitigates failure patterns by blocking assumptions and unverified reports.

Preventing premature task completion requires rigorous verification protocols that mandate objective evidence of state changes. This approach blocks partial checks and enforces accountability before success is declared.

Run the verification protocols to execute necessary test commands and confirm the output matches expected success criteria. This validates the current task status by requiring objective evidence before submission.

Yes, evidence-based verification applies to project management workflows by requiring the execution of specific validation commands and analysis of their output to confirm state changes before task success is declared.

Verifying output matches expected success criteria is necessary to prevent prematurely declaring work as finished without actual proof. It ensures all claims of success are backed by verifiable evidence.

Relying on partial checks instead of full test suite verification leads to failure patterns like assumptions and unverified agent reports. These limitations are actively identified and blocked by rigorous verification protocols.