verification-before-completion

To enforce verification before completion, you need a process that requires running specific tests, linters, and build commands. This approach captures concrete evidence from command outputs to support any assertions about task success, preventing premature claims and reducing errors.

Evidence-based task verification is a process that requires concrete proof from command outputs before declaring success. It ensures developers run specific verification commands and analyze their results, preventing unverified claims of completion and maintaining trust in the software development workflow.

To prevent premature claims of task completion, enforce a strict verification process that requires running specific quality assurance commands. By analyzing test and build outputs to provide concrete evidence, you ensure all assertions about work completion are validated before finalizing any code review.

Yes, the verification process requires running tests, linters, and build commands before committing code. You must review their output to confirm everything works as expected, providing evidence-based assertions that validate the work state before any claim of completion is made.

The best way to verify quality assurance before finalizing agent tasks is to enforce mandatory verification commands. By requiring concrete evidence from command outputs to support success claims, this process ensures all necessary steps are performed before declaring task completion, maintaining reliability.

You need to apply a strict verification process whenever you are finalizing tasks, passing tests, or claiming success in a software development workflow. It is required before committing code to ensure all tests, linters, and build commands have been validated with concrete evidence.