task-completion-verify

You verify task completion with evidence by running deterministic verification commands and validating their fresh output before making any success claims. This process enforces a gate-by-gate check to guard against premature success claims in software development workflows.

Evidence-based completion verification in test automation is a workflow that requires running deterministic verification commands and capturing their output to prove a task is truly complete. It prevents premature success claims by enforcing validation before declaration.

You prevent premature success claims in CI/CD and code review workflows by enforcing a verification gate before marking tasks complete. This involves running deterministic verification commands and confirming the output provides fresh evidence of success.

Yes, you can use task completion verification for quality assurance and task dispatch workflows. The process applies across these domains by requiring deterministic verification commands to run and their outputs to be parsed before any completion is declared.

The best way to enforce a verification gate before declaring a build passing is to apply a gate-by-gate process that runs deterministic verification commands and validates their outputs. This ensures every completion claim is backed by fresh evidence.

You need to run deterministic verification commands before claiming work is complete whenever you are marking tasks as fixed, passing, or done in software development. This requirement ensures that output is captured and validated as evidence before any success declaration.