aif-verify

To verify implemented code against a project plan, you audit completed tasks to ensure plan alignment, build health, passing tests, and documentation consistency. This validates completeness and correctness across multi-task codebases.

Plan-to-implementation validation compares the plan TaskList with actual code changes and outcomes. It surfaces missing tasks, mismatches, and remediation suggestions to ensure no requirements are missed during codebase execution.

To check build health, test results, and lint quality after implementation, run end-to-end quality checks. This ensures code compiles, tests pass, and linting is clean across the implemented tasks.

Yes, you can audit completed tasks to satisfy requirements for dependency validation and changelog synchronization. This ensures documentation consistency and verifies that all implemented changes match the original plan.

You should run quality checks immediately after completing a plan with an implementation tool or upon user request. This confirms all tasks are complete, compliant, and free of gaps before finalizing changes.

The best way to find missing tasks is gap reporting, which compares implemented code against the original plan. It surfaces mismatches and provides remediation suggestions to resolve incomplete requirements.