aif-verify

Verifying code implementation against a project plan involves auditing completed work to ensure all plan tasks are fully realized, code compiles, automated tests pass, and quality standards are met. This generates a structured verification report with actionable findings.

Checking if all planned tasks are implemented in a feature branch requires a plan-alignment check. This compares the implemented work directly against the defined plan to highlight any gaps, ensuring branch-based development aligns with the original requirements.

Generating a structured report for build and test verification involves running checks to confirm the project compiles and automated tests pass. The process outputs a structured confidence report detailing actionable findings on implementation quality.

You need to run an implementation quality audit after a feature is implemented or during the verification phase across codebases using branch-based plans. It validates completeness, enforces plan adherence, and confirms that CI and diffs meet required quality standards.

Implementation verification is specifically applicable across codebases that use branch-based plans, CI, and diffs. Without these elements, the structured verification process cannot enforce plan adherence or perform the required build and test checks effectively.

A completed feature fails the plan-alignment check when the implemented work deviates from the defined plan, leaving gaps in task realization. The verification report highlights these specific mismatches in your codebase diff.