verification-checklist

Prevent premature done declarations by enforcing a structured verification process that requires evidence for every completion criterion before reporting a task as finished. This checklist enforces functional, standards, test, integration, and self-review checks.

A code change verification checklist should include functional verification, standards compliance, test coverage, integration safety, and self-review sections. Each item requires exported evidence to yield a reproducible completion report for audits.

Generate audit-ready evidence by running a multi-section verification checklist at task completion. It captures traceable proof for functional and non-functional criteria, yielding a reproducible completion report for feature completion, bug fixes, and refactoring.

Yes, the verification checklist is applicable for refactoring and integration safety checks. It enforces structured verification across any code change, requiring evidence exports to confirm integration safety and standards compliance before completion.

Evidence exports are required for test coverage and standards compliance verification to guard against premature completion. They provide traceable proof that every criterion was checked, yielding a reproducible completion report for reviews.

The best way to enforce code quality and self-review is to apply a structured verification checklist at the end of a task. It mandates self-review and standards compliance checks, requiring evidence before yielding a completion report.