verification-before-completion

To enforce verification evidence before claiming completion, implement a verification gate that requires running tests and builds, then inspecting fresh outputs before reporting success. This prevents false completion claims by demanding verifiable command execution results across QA workflows.

Requiring fresh verification evidence prevents false completion claims by ensuring developers run actual verification commands and inspect current outputs before marking a task complete. Claiming completion without this verification gate is dishonest, as it bypasses evidence-based reporting.

The best way to verify code changes before merging is to run full verification commands and report fresh evidence. This quality-assurance approach enforces explicit verification steps and inspects fresh build outputs to satisfy strict completion criteria.

Yes, you can use automated verification gates for agent-assisted tasks. The gate applies to code changes and tests by requiring command execution and evidence-based reporting, ensuring the agent provides fresh verification outputs before reporting success.

Claiming completion without running verification commands leads to false success reports. The limitation of skipping this quality-assurance step is the lack of fresh evidence, meaning code changes, tests, and builds remain unverified and potentially flawed across development pipelines.

Yes, this verification approach integrates with existing quality-assurance workflows by enforcing a verification gate. It requires running the full verification command and reporting fresh evidence before making any completion claim, applying seamlessly across development pipelines and CI-CD processes.