verification-before-completion

To prevent broken TypeScript code from being submitted, enforce a strict verification process requiring fresh evidence before completion claims. You must run commands like `npx tsc --noEmit` and `npx eslint src/ --ext .ts,.tsx` to validate code quality.

The Iron Law of verification before completion is the principle that no completion claims can be made without fresh verification evidence. This quality assurance mechanism mandates executing specific validation commands to prove work success.

To verify code quality before claiming an agent task is complete, follow a strict gate function process. Execute mandatory verification commands like `npx tsc --noEmit && npx eslint src/ --ext .ts,.tsx` and confirm the output shows zero errors.

Yes, the verification process integrates with CI/CD pipelines for quality assurance by enforcing an evidence-before-claims principle. It applies to software development workflows, requiring fresh validation outputs before any success assertions are made.

You need to run fresh verification evidence during development whenever you are ready to claim work completion or success. This prevents premature declarations of finished tasks and ensures all defined criteria are validated.

Claiming completion without verification causes costly errors because it allows broken or non-compliant code to bypass quality assurance checks. Enforcing mandatory verification steps maintains honesty by requiring actual command outputs before any success assertions.