verification-before-completion

To verify task completion before creating a pull request, run pre-defined verification commands to validate work status output, ensuring code claims are backed by evidence prior to committing.

Evidence-driven verification in a development workflow is the process of executing specific commands to check output and status, ensuring software integrity before making any success or completion claims.

Run the 'verify-work-status' command to validate task results; this enforces a strict verification protocol that checks output before allowing you to claim work is complete.

Yes, you can use automated verification for quality control by executing pre-defined commands that validate results, ensuring high standards are maintained before committing code changes.

Task completion claims fail without verification output because the system enforces an evidence-driven protocol that requires command execution and status validation before permitting any success assertions.

The best way to ensure software integrity before committing code is to execute pre-defined verification commands that confirm work status, preventing dishonest claims by validating evidence first.