verification-before-completion

To prevent false completion claims, you must require fresh verification evidence before making any success statements. This involves identifying the proving command, running it fully, reading outputs, verifying status with documented evidence, and only then declaring completion.

The verification process requires a five-step gate: IDENTIFY the proving command, RUN it fully, READ and interpret the outputs, VERIFY the status with documented evidence, and ONLY THEN declare the task complete. This stops premature success claims.

You document evidence by running the full verification sequence in your project workspace and recording the outputs. This enforces examining tests, linters, and builds to provide concrete proof before asserting any successful completion.

Common red flags include making success claims without running the full verification command or failing to examine the output first. Guardrails against these false positives require interpreting actual outputs and verifying status with evidence before closing tasks.

No dependencies are required to enforce this verification gate. It operates independently within your software development and QA workflows to ensure teams run checks and document evidence before making any statements of success.