verification-before-completion

To validate work completion before submitting a pull request, manually run predefined validation commands and review their outputs to ensure accuracy and support honest claims about your software development changes.

Task validation in software development workflows is the process of executing predefined commands and reviewing their outputs to confirm correctness, ensuring accuracy and honesty before marking tasks as complete.

You ensure honesty in work completion claims by using evidence-based validation, which involves running necessary validation commands and reviewing the output to confirm the correctness of your changes before claiming completion.

No, validating software task completion does not require automated tools here, as this process requires manual execution of validation commands and manual review of their outputs to confirm work correctness.

The best way to prevent claiming work completion without proper validation is to follow a workflow that requires running validation commands and reviewing their outputs to gather evidence of correctness before marking the task complete.

A limitation of this task validation approach is that it requires manual execution of commands and manual review of outputs, relying on the user to interpret results correctly before claiming work completion.