verification-before-completion

To enforce verification before claiming code completion, you must run specific commands like tests or linters and require explicit evidence such as exit codes and output logs to validate success assertions. This prevents premature completion claims.

Evidence-based verification requires tangible output and exit codes from command execution as proof before making any assertions about task success, testing, or bug fixing. It ensures accuracy by preventing unverified claims of work completion.

To prevent premature claims of work completion during code review, enforce a strict verification protocol requiring developers to run commands like npm run test:all and verify zero failures before stating that all tests pass.

Process enforcement for task completion does not require specific testing frameworks. It applies universally across testing, linting, building, and bug fixing by validating success assertions through command execution outputs and exit codes.

You need strict verification protocols for quality assurance whenever making claims about work completion, success, or passing status across all development stages. This prevents costly errors by demanding tangible command output evidence before validating assertions.

Claiming work is complete without command output fails quality assurance because it lacks explicit evidence such as exit codes and output logs. Strict verification protocols require this tangible proof to validate assertions and prevent costly errors.