verification-before-completion

Task completion verification requires running a proving command that produces fresh output, reviewing the results, and confirming success before making any claims. This structured gate process enforces accountability by demanding evidence for PR readiness checks and feature sign-offs.

A gate-based verification workflow requires fresh command outputs as evidence before asserting successful task completion, preventing unverified claims in software development. It enforces accountability by gating claims behind executed proving commands and evaluated results.

To enforce evidence-based quality assurance for code reviews, implement a structured gate process requiring fresh command outputs as evidence before any task closure. This ensures claims of feature completion are backed by documented execution logs rather than unverified assumptions.

Yes, the verification workflow handles failing commands by flagging common failures and warnings to prevent premature assertions. If results do not confirm success, you must document the actual state with accompanying logs instead of claiming completion.

You need to run verification commands for software development workflows during PR readiness checks, feature completion sign-offs, and task closures. This structured gate process ensures that any claim of work being complete is supported by fresh, evaluated command outputs.