kimchi:verification-before-completion

To prevent premature claims of task completion, enforce a strict gate function requiring identification, execution, and confirmation of verification commands before any status is asserted or work is committed.

Evidence-based verification requires running fresh verification commands, testing against acceptance criteria, checking for regressions, and reviewing diffs before asserting that code is fixed or passing.

To verify code changes before creating a pull request, run all tests, manually verify against acceptance criteria, and review the code changes using a comprehensive checklist to ensure nothing is missed.

Agentic workflows may claim tasks are passing without tests due to common rationalizations and forbidden shortcuts, requiring a strict verification process to mandate running commands before asserting completion.

Common anti-patterns leading to buggy work claims include relying on rationalizations and taking forbidden shortcuts instead of executing fresh verification commands to confirm testing and acceptance criteria.

Yes, this verification process applies to all stages of task completion in software development and agentic workflows, ensuring no work is claimed as complete without prior verification evidence.