verification-before-completion

To prevent false positive claims of task completion, you must execute specific verification commands and confirm their outputs before asserting success. This enforces rigorous validation by ensuring evidence precedes any claims of code correctness or work status.

Assuming tests pass without running them causes code regressions because it skips concrete validation. Preventing false positives requires running verification commands to confirm the build is successful and linters are clean before stating work is complete.

The best way to ensure code quality before committing code is to mandate verification steps that run relevant tests and check build success. This enforces validation by requiring concrete evidence of clean outputs before any claims of completion are made.

Yes, you can use automated verification for agent-based task execution workflows. This enforces rigorous validation by ensuring all verification commands are executed and confirmed, requiring evidence to precede assertions of work status or task success.

Verification before completion does not work effectively without specific test commands, because it mandates running commands to confirm status. Without concrete evidence from executed outputs, preventing false positives and ensuring honest reporting is impossible.

To enforce evidence-based assertions in task management, mandate that all verification commands are executed and their outputs confirmed before claiming success. This enforces validation by requiring concrete evidence to precede any assertions of task completion.