Verification Before Completion

Verification commands confirm that work is actually complete by producing fresh evidence—exit codes, test results, and build outputs. Without running them, claims can mask incomplete work, failing tests, or lint errors that weren't caught, creating false confidence and quality gaps.

Execute the full verification workflow: run your build command, test suite, and lint checks. Analyze exit codes and output for errors. Report completion only when all verification steps pass and produce clean results—never skip or assume success.

Verification applies universally: run the build command for compilation errors, execute the test suite for failures, and run lint checks for code quality issues. Each step must complete successfully with zero errors before you can claim the task is done.

Yes. Verification gates catch omissions, misstatements, and failures before you report status. By enforcing evidence-based claims backed by fresh command outputs, it reduces risk of shipping incomplete or broken work.

Skipping verification means undiscovered failures—broken builds, failing tests, or lint violations—reach downstream stages. This creates rework, delays, and eroded confidence in status reports. Verification ensures claims match reality.