verification-before-completion

Pre-commit verification checks enforce a structured workflow requiring commands to be run and outputs reviewed before making claims about work status, ensuring accuracy and integrity.

Preventing premature success claims requires an evidence-driven verification process that demands command outputs as proof before any claims about fixing or passing work are made.

PR verification stages enforce an evidence-driven process by requiring commands to be run and their outputs reviewed before any claims about the completion status of work are accepted.

Workflow scripts can automate commit checks to ensure software development work meets predefined quality assurance criteria before any changes are committed and claims are made.

Workflows allow unverified success claims when they lack a structured verification process requiring commands to be run and outputs reviewed before making claims about work status.

Yes, an evidence-driven verification workflow requires running verification commands and reviewing their outputs before making any claims about the completion or passing of software development work.