verification

To verify task completion, systematically re-read the original request, list all acceptance criteria, provide concrete evidence like test output, and confirm functional resolution. This process prevents premature closure by rigorously checking that every requirement is fully satisfied before marking the task complete.

Checking for regressions after a bug fix involves running the full test suite to confirm no new issues were introduced. You must verify the original issue is resolved with evidence while simultaneously ensuring the codebase remains stable without unintended side effects impacting other functional areas.

Preventing tasks from being marked as complete prematurely requires a systematic 6-step verification process. This includes re-reading the request, listing criteria, providing evidence, checking for regressions, and confirming functional resolution to ensure strict adherence to all original requirements before closing.

Quality assurance verification works for both bug fixes and feature implementations by applying a unified process. It requires providing test output proving the fix or feature, running the full test suite, and confirming no regressions or unintended side effects before the task is considered functionally resolved.

Confirming functional resolution requires a 6-step process: re-reading the original request, listing all acceptance criteria, providing concrete evidence, running the full test suite, checking for regressions, and finally confirming that the task is functionally resolved without introducing unintended side effects.

Using a systematic verification process before closing a bug report ensures functional correctness and adherence to all original requirements. It validates the fix with concrete test output evidence and confirms no new regressions were introduced, guaranteeing the issue is truly resolved rather than superficially addressed.