verifying-completion

To verify task completion, itemize all code changes, create verification todos for each piece, and perform structured gap analysis to hunt for missed requirements. This self-review process ensures implementation work is rigorously validated before final sign-off.

Structured uncertainty analysis is a gap analysis technique used during code review to proactively uncover missed requirements or edge cases. It employs alternative thinking to hunt for potential gaps in recently completed implementation work before declaring completion.

Audit implementation work by forcing a meticulous itemization of all changes made, establishing specific verification todos, and evaluating evidence against strict protocols. This auditing process prevents premature completion claims by requiring a definitive verdict.

You need to perform gap analysis after finishing implementation tasks and before claiming completion. It ensures every line of code, configuration change, and test case is accounted for, preventing bugs from slipping into production.

Yes, code review gap analysis works without external dependencies because it operates as a standalone script component. It enforces strict verification protocols internally to produce a definitive complete or incomplete verdict based on evidence.