recheck

To verify code changes match the original implementation plan, you need a post-implementation review process that reads modified files alongside the plan to assess scope, detect deviations, and confirm compliance with project conventions.

Parallel code review for post-implementation checks works by dispatching multiple specialized agents simultaneously to evaluate plan compliance, security, test coverage, and code quality, including one agent reading the plan cold to identify blind spots.

The best way to prevent scope creep after implementing new features is to run scope-aware validation that evaluates git history, diffs, and project conventions against the original plan to identify and reduce deviations.

To check if your git diff covers critical paths like error handling and security, perform a plan-aligned review that confirms these considerations are properly covered and validates overall test coverage.

You can use automated review agents when your base branch is unclear, but the review process will request clarification on the base branch before proceeding to evaluate git history and diff accurately.

You need a CLAUDE.md file or similar project conventions document to perform plan-compliance reviews, as the review process evaluates your changes against these established project standards to ensure quality and alignment.