verification-before-completion

Task verification before completion requires running tests, building, and linting, then collecting evidence such as logs, test outputs, and artifacts to confirm specific requirements are met before reporting done.

Evidence-first completion is a workflow that requires verifiable proof, such as test outputs and build artifacts, to be collected and attached before any development task, bug fix, or refactor is marked complete.

To attach verification evidence to a completed task, run the verification workflow to collect logs, test outputs, and build artifacts, ensuring reproducible results back your completion claims.

Yes, the verification checklist works for configuration updates and refactoring by applying a standardized process of running tests, builds, and linting to ensure verifiable results across all task types.

Requiring reproducible results before reporting a task done improves quality control and accountability by ensuring completion claims are backed by actual test outputs, logs, and artifacts rather than unsupported assertions.