verify-plan-grounding

To verify if a coding plan matches the current repository state, you can generate and execute a bash script that asserts load-bearing claims like file paths, line numbers, and function signatures against the actual codebase.

Plan drift detection is the process of validating outdated coding plans against the current codebase to identify stale assumptions caused by file movements, refactoring, or dependency updates before execution begins.

You can validate outdated file paths and function signatures by generating a bash-based verification script that checks these load-bearing claims against the repository's current state using standardized assertion logic.

Yes, you need a POSIX-compliant shell environment to run these automated codebase verification scripts, along with access to the project's internal helper scripts for standardized assertion logic.

You should use automated verification scripts for code analysis when executing multi-agent plans that are several days old to confirm all referenced files and code structures still exist as expected and prevent execution errors.