verification-before-completion

Final verification before completion requires running all tests, confirming documentation updates, checking code reviews, and validating backward compatibility. This comprehensive checklist prevents incomplete work and forgotten steps from reaching production.

Verify that requirements are met, all tests pass with backups performed, end-to-end scenarios work manually, API documentation is updated, security vulnerabilities are absent, and deployment readiness is confirmed. This multi-faceted verification ensures professional-grade delivery.

Yes. Verification-before-completion enforces mandatory checks across commits, pull requests, issue closures, and task handoffs, requiring test passage, code quality review, documentation validation, and environment consistency before any release.

Establish a rigorous final verification protocol that includes test execution, database backups, code reviews, security scanning, performance validation, and documentation cross-checks before declaring work complete and deploying.

Incomplete verification before completion—skipping documentation updates, environment consistency checks, backward compatibility validation, or security reviews—allows issues to slip through despite passing tests.

A comprehensive final checklist covers requirements verification, functionality testing, integration checks, documentation audit, code quality review, security assessment, and performance validation to catch issues before deployment.