verification-before-completion

To enforce a verification process, require fresh verification evidence for all work completion claims by running verification commands and confirming their output before any success is declared. This protocol maintains software integrity across development and QA workflows.

Common red flags for skipping quality assurance include rationalizing that previous checks suffice or assuming code changes without testing. The verification protocol identifies these mistakes and provides counterarguments to ensure development integrity through fresh evidence.

To verify work completion step by step, identify the specific verification command, execute it freshly, read the output carefully, and confirm the claim matches the results before declaring success. This ensures claims are backed by evidence.

Evidence-based verification applies directly to development, QA, and project management workflows. It requires a clear definition of verification steps and the ability to execute them independently to ensure software integrity before completion is claimed.

You need to run verification commands fresh because claiming work is complete requires current evidence. Relying on past outputs or assumptions undermines software integrity and skips the required confirmation that the verification protocol enforces.