verification-before-completion

Task completion verification requires executing end-to-end commands and capturing outputs with exit codes to validate success criteria before declaring a PR ready for review. This prevents unverified claims by mandating a documented evidence trail.

Evidence-based verification is the process of running designated validation commands, collecting logs and exit codes, and validating them against success criteria to ensure completed states in feature development or bug fixes are backed by verifiable results.

Validate success criteria by executing verification commands, capturing their terminal outputs and exit codes, and refusing to signal task completion until the collected evidence explicitly matches the defined success conditions.

Yes, automated verification applies across CI/CD workflows and team code reviews by capturing command outputs and logs to provide a clear evidence trail that supports status updates and audits for feature releases or bug fixes.

Unverified completion erodes trust and causes wasted effort because status updates lack documented evidence. Mandating verification commands ensures honesty and accountability by requiring verifiable results before signaling work is done.

Refusing completion without an evidence trail means tasks cannot be marked done if verification commands fail or lack documented outputs, ensuring task closure strictly depends on validating exit codes against success criteria.