verification-before-completion

To verify task completion before updating project status, execute specific verification commands in your terminal and review the output for errors. This process ensures tests and builds pass, preventing inaccurate completion reports and upholding project integrity.

Trusting agent reports without running verification commands risks false claims of task completion. Without executing tests and reviewing output, unrun tests or incomplete verifications may go unnoticed, compromising accountability and accuracy in your project workflows.

Command execution enforces quality assurance during software development by requiring users to run tests and builds, then review the output for errors. This strict verification procedure detects common failure points and ensures outcomes are validated before progressing.

Yes, you can use this verification process for general project management workflows. It enforces strict verification of task completion by checking for errors in tests, builds, and agent reports, ensuring accountability and accuracy across any project workflow.

Relying on manual task completion checks often leads to false claims of task completion due to human error or trust in unreliable agent reports. Without enforced command execution and output review, unrun tests and incomplete verifications frequently go undetected.

Task verification fails when builds or tests are incomplete because the verification procedure identifies common failure points by reviewing command output. Enforcing strict execution prevents false completion claims by requiring users to validate all outcomes before progressing.