verification-before-completion

Enforce evidence-based verification before a pull request by executing verification steps, evaluating outputs, and documenting findings to satisfy formal criteria. This prevents premature completion claims by requiring fresh validation data as auditable outputs.

Evidence-first task completion is a workflow mechanism that gates status updates or releases behind fresh verification data. It ensures software delivery claims are backed by auditable outputs from executed tests and evaluated results rather than assumptions.

Document quality assurance findings for code review readiness by running a formal verification gate on the current work item. Execute the required verification steps, evaluate the outputs against clear criteria, and record the findings as auditable evidence before declaring completion.

Yes, you can use this verification process for general task completion workflows. It applies to any software delivery or QA task requiring evidence-driven validation, guiding you through a repeatable process to generate auditable outputs that satisfy completion criteria.

Premature completion claims cause failed software deployments because they bypass fresh verification data, eroding trust and introducing faulty software. An enforced verification gate prevents this by requiring evaluated outputs and documented findings before any status update or release.