verification-before-completion

Verification before completion means executing fresh test runs, build checks, and linting commands to confirm all acceptance criteria pass. Analyze exit codes and failure counts to prove quality standards are met before claiming success, preventing rework from incomplete submissions.

Run unit tests, linting, and build commands to verify the code passes all checks. Document the evidence—test results, build logs, and lint output—confirming no failures exist before handoff. This prevents merged code from breaking downstream systems.

Yes. Integrate verification into testing tools and CI/CD workflows to automatically validate code against defined quality standards. Generate dynamic checklists tied to acceptance criteria, then confirm all checks pass before approving reviews or deployments.

Verification prevents false success claims—tests passing, builds succeeding, bugs fixed—when they haven't actually run or passed. It reduces rework by catching incomplete work early and ensures deliverables consistently meet quality requirements before finalization.

Claiming completion relies on assumption; verification requires executing fresh commands, analyzing outputs and exit codes, and confirming evidence of success. Verification transforms subjective assertions into measurable proof that work meets all defined standards.

Extract acceptance criteria from the feature requirements, then map each criterion to a concrete verification action—run specific tests, check documentation updates, validate linting output. Execute each action, record results, and confirm all pass before marking the feature complete.