verification-before-close

Final task verification uses a checklist-based validation process to check touched files, commands, and scripts before marking a task as complete. It runs relevant validations and ensures proper evidence is recorded to support completion claims.

False closure in software engineering happens when tasks are marked complete without proper validation. You prevent it by running a final verification checklist that categorizes checks into passed, skipped, and blocked, ensuring the final answer matches recorded evidence.

You document evidence for code review by identifying manual follow-up steps and environment-specific dependencies during validation execution. The verification process ensures the final answer explicitly calls out any unverified work alongside the recorded evidence.

The best way to ensure task completion accuracy is applying a checklist-based validation process that separates passed, skipped, and blocked checks. This verification process is applicable to environments where accuracy and completeness are critical.

Yes, final verification works without external dependencies for quality assurance. It operates independently using scripts to perform a checklist-based validation of touched files and commands, identifying environment-specific dependencies without requiring external packages.