ito-verification-before-completion

Verification before claiming work completion requires running tests, reviewing command outputs, and documenting evidence of success. This skill enforces those verification steps by requiring manual execution of builds and fixes before any success claims are made in software development.

Accountability in work completion is achieved by enforcing pre-claim verification. This requires running verification commands, reviewing the output, and documenting evidence of success before claiming an issue is resolved or a bug is fixed.

To verify software builds and tests before reporting success, manually execute verification commands and review their outputs. This process ensures all tests and fixes are thoroughly checked before any completion claims are made.

Documenting evidence of a successful bug fix requires running the test, reviewing the output, and recording the proof of success. This skill provides process guidance to ensure these verification steps are executed before reporting the issue as resolved.

Yes, this software quality process requires manual execution of verification commands. It enforces accountability by ensuring you actively run tests and review the output yourself before you can document evidence and claim work completion.

You should not use automated verification when manual execution and output review are required for accountability. This process enforces manual verification steps to ensure all tests, builds, and fixes are actively checked before reporting completion.