implementation-review

To verify merge readiness, run a post-implementation review that compares branch changes against the original plan, runs tests, and checks for drift. It requires access to the active plan directory and current branch information to validate correctness.

Plan drift detection is the process of comparing finished implementation changes against the original plan to identify misalignment. It audits task completion and flags potential safety issues or regressions before merging the branch.

You can check alignment by loading the original plan from the plans/active/ directory and comparing it against branch changes. The review audits task completion, detects drift, and runs quality checks to ensure safe merging.

Yes, a test suite is required to validate correctness during an implementation review. The review runs tests as part of its evidence-driven verdict to determine merge safety and identify potential regressions.

The best way to audit a finished feature is to run a plan-aware review that executes checks, tests, and quality signals. This governance step identifies drift, incomplete tasks, and safety issues before merging.