verification-before-completion

To prevent false task completion claims, enforce a strict 5-step verification protocol that mandates running fresh commands, reading their full output, and confirming results before marking any task complete.

A completion gate in quality assurance is a hard checkpoint that prevents any task completion claim from being made until fresh verification commands are executed and their outputs are explicitly reviewed and confirmed.

Verify code quality before marking a bug fix complete by running all relevant tests, linters, and build checks fresh in the current session, then reviewing their full output to confirm the fix actually resolves the issue.

Yes, the verification protocol operates without external dependencies, applying a 5-step completion gate across all development phases to mandate fresh evidence and confirm code quality before any completion claim is finalized.

Task verification relies on stale results when previous outputs are assumed valid; a strict completion gate protocol prevents this by requiring fresh command execution and reading full current session outputs before confirming code quality.

Manual task management limitations include assuming prior test outputs are valid; a hard-gated 5-step verification protocol overcomes this by mandating fresh command execution and full output review for every completion claim.