validate-plan

To verify that code changes match the original implementation plan, you can validate the implementation by applying automated checks across commits, test results, and contextual notes. This process ensures all success criteria are met and highlights any deviations from the plan.

Plan-to-implementation alignment ensures implemented work satisfies the original plan's success criteria. Automated verification works by gathering evidence from commits and test results, running checks, analyzing deviations, and producing a final validation report.

You can generate a validation report by running a workflow that compares implemented changes against the plan. The report highlights matches, deviations, and risks by gathering evidence from commits, running tests, and analyzing contextual notes.

Yes, you can use git commits and test results as evidence for plan validation. The evidence gathering step collects commits, test outcomes, and plan references to verify traceability and ensure all success criteria are met.

The best way to identify deviations between a plan and its implementation is to run an automated verification workflow. This analyzes code changes, commits, and test results against the plan, producing a comprehensive report that highlights mismatches and risks.

No specific dependencies are required to run the plan validation workflow. The process relies on gathering existing evidence from your code changes, git commits, and test results to verify traceability and validate the implementation against the plan.