verification-before-completion

Evidence-based verification requires running commands and capturing fresh outputs to validate changes before completion. This enforces explicit gating criteria, preventing premature success claims by ensuring actual command output matches expected results before updating status or creating PRs.

Preventing unverified success claims involves applying rigorous output validation during QA workflows. This enforces evidence gathering by capturing and referencing command outputs, ensuring that work cannot be marked complete without explicit, repeatable proof of success.

Automating PR review with command output evidence requires enforcing verification steps that validate command results before submission. This captures fresh execution outputs as proof, gating the PR creation process until evidence confirms the changes work as intended.

No specific testing frameworks or dependencies are required. The verification workflow operates independently by applying output validation and evidence gathering commands, fitting seamlessly into existing software development and collaboration environments without needing external modules.

Evidence gathering commands are needed whenever changes must be verified before status updates or pull requests. This applies directly to software development and QA workflows where proof of success matters, ensuring integrity by validating output before declaring completion.

Workflows allow premature completion when they lack explicit gating criteria and output validation. Implementing rigorous verification before completion prevents this by enforcing evidence-based checks, requiring fresh command outputs as proof before any success status is accepted.