superpowers-verification-before-completion

To enforce evidence-based work completion before committing code, you need a verification workflow that requires predefined verification commands to execute and output to be manually confirmed. This standardizes the process of backing completion claims with proof.

An automated verification check in software development is a standardized process that enforces the execution of predefined commands, such as tests and linters, to gather evidence before a task is marked complete. It prevents misrepresentation by requiring manual confirmation of output.

To prevent incomplete tasks from being marked as complete, implement a verification workflow that enforces evidence-driven claims. By requiring predefined verification commands to run successfully before completion, you reduce the risk of shipping incorrect work.

Evidence-based verification works with standard testing and linting workflows by requiring their execution as predefined verification commands. You must run these commands and confirm the output is clean before making any success claims or creating pull requests.

The best way to standardize quality assurance before a pull request is to enforce a verification workflow that requires all tests to pass, linters to be clean, and builds to succeed. This ensures all completion claims are backed by confirmed evidence.

You should run verification commands before claiming work is done to prevent dishonesty and misrepresentation. Enforcing this evidence-based process guarantees that success claims are backed by actual proof, reducing the risk of shipping incomplete software.