aif-verify

Verifying code implementation against a project plan requires auditing task completion, checking build status, running tests, and performing linting. This ensures all requirements are fully met and detects drift between the plan and code.

Plan adherence verification confirms completed code matches the project plan by auditing task completion and performing consistency checks. It prevents costly errors and rework by detecting drift between the plan and implementation.

Checking for leftover TODO comments and artifacts involves running consistency verification to identify remaining items in the codebase. It ensures configuration documentation aligns with the actual implementation before merging.

Code quality verification assesses build status, test results, linting, and dependency integrity to ensure implemented code meets quality standards. It confirms the codebase is production-ready and prevents costly rework.

You need to run a task completion audit after a developer completes a feature to verify every requirement in the project plan has been fully implemented. This prevents errors by ensuring no tasks are missed before merging.

Automated plan adherence checks verify task completion, build status, tests, and linting, but require a detailed project plan to function effectively. They detect drift and leftover artifacts but depend entirely on the plan's accuracy.