verification-before-completion

To enforce verification before completion, use a quality gate that requires running full test commands and inspecting their output prior to any phase transition. This prevents premature completion claims by demanding fresh command output evidence for every success statement.

Verifying compliance before a commit involves running linting, formatting, and type safety checks to ensure a clean state. You must execute these quality gates and cite concrete command outputs, exit codes, and failure counts instead of relying on vague confidence.

To prevent false success claims in dev workflows, mandate evidence-first communication by requiring agents to report exact outputs and exit codes. Enforce a verification gate so agents must run and inspect full commands before claiming tests or builds are done.

You need to run a quality gate check during a pull request when transitioning phases or declaring a fix complete. This ensures that tests, linting, and builds have been freshly executed and verified with concrete output evidence before completion.

Yes, claiming a build is done requires showing command output evidence. The verification process enforces evidence-first communication, demanding that you run the full verification command and report exact outputs, exit codes, and failure counts to substantiate passing assertions.