verification-before-completion

Evidence-based verification requires running testing, linting, and building commands to produce concrete output before making any work completion claims. This framework standardizes the process of checking software quality through external tools.

The best way to verify code quality before merging is to execute all verification commands manually and review the output. This framework requires evidence of successful testing, linting, and building before asserting work completion.

Yes, verifying work completion requires external tools for testing, linting, and building. The framework mandates manual execution of these tools to gather evidence before making any success claims about your software.

Standardizing software quality verification involves enforcing a workflow that requires running all testing and linting commands first. You must review the external tool output as evidence before making any assertions about development completion.

Development workflows lack evidence when they skip verifying work through testing, linting, and building. This framework solves that by enforcing a culture of thoroughness requiring external tool output as proof before claiming success.

You should not use an evidence-based verification framework if you cannot manually execute external testing and building tools. The framework strictly requires running verification commands and reviewing their output before making completion assertions.