verification-before-completion

To enforce evidence-based work completion, you must execute objective verification commands and validate fresh output logs or exit codes prior to asserting any task success. This protocol prevents premature or inaccurate status reporting in software development workflows.

A verification gatekeeping protocol in software testing mandates running specific verification commands before any status claims are made. It ensures high-quality output by requiring fresh, verifiable evidence like test logs before declaring work successful.

To verify test suite and linter output before a pull request, systematically run your verification commands and confirm zero failures in the execution logs. This validates output evidence prior to declaring the development task complete.

Yes, evidence-based reporting works for agent-based task delegation workflows by preventing the common pitfall of claiming work is finished without objective proof. It requires validating execution output and exit codes before any success assertion is made.

Claiming work is finished without objective proof causes workflow problems because it leads to premature or inaccurate status reporting. Enforcing strict verification protocols prevents this pitfall, ensuring high-quality output and maintaining trust in the development process.