verification-before-completion

Verification before completion requires running your specific build and test commands fresh, reading the actual outputs, and validating the results explicitly. This workflow enforces evidence-based checks to ensure all criteria pass before claiming task success.

Evidence-based completion enforces a step-by-step workflow where you identify a verification command, run it fresh, read the outputs, and validate success before claiming completion. This prevents unverified work claims from entering builds or handoffs.

You need fresh command outputs to claim task completion because relying on past execution results risks false positives from unverified changes. Requiring newly generated evidence ensures the current codebase genuinely meets all success criteria before handoff.

Yes, you can use this verification workflow for linting and build checks. The process applies to any task where verification outputs determine status, requiring you to run the dedicated command and report the exact output to prove success.

You should enforce verification checks before claiming completion during PR submissions, builds, and task handoffs. It is necessary whenever a success claim must be validated against fresh execution outputs to prevent unverified work from progressing.

The best way to prevent false positives in test and build verification is to enforce a step-by-step workflow that requires fresh evidence. By running explicit commands, reading fresh outputs, and validating results, you ensure only confirmed successes pass.