verification-before-completion

To enforce verification before completion, apply a structured five-step process: identify claims, execute verification commands like tests or builds, read outputs, verify results, and claim completion with documented evidence.

Evidence-based completion is a standardized process requiring explicit verification through tests, builds, and linting before claiming task completion, ensuring outcomes are validated and documented for auditability.

You can verify tests, builds, and linting by executing definitive commands in a fresh run, recording full outputs and exit codes, and confirming they match claimed results before making any completion claim.

No specific testing frameworks are required. The verification process applies across any development workflow, allowing you to use standard commands like npm test, npm run build, or npm run lint to validate outcomes.

Yes, you can use this structured verification process for bug fixes across any software project. It standardizes the workflow by requiring you to run definitive commands and capture outputs as proof of the fix.

The best way to document completion for auditability is to record full command outputs and exit codes during verification, providing verifiable proof of successful tests, builds, and linting to stakeholders.