Plan Review

Pre-flight review of an implementation plan markdown file. Produces a verdict (READY / NEEDS_REVISION / BLOCKED) and a prioritized findings table. Used standalone and as a pre-execution gate by implement-plan.

This is a document review, not a code review. No static analyzers. No diff scoping. The plan is treated as the artifact under test; the codebase is read-only context for feasibility checks.

Workflow

1. Resolve the plan file

Priority order:

1. Explicit path from the invocation (e.g. /review-plan .plans/auth-rewrite.md).
2. ./.plans/PLAN.md in the current working directory.
3. Latest by mtime in ./.plans/*.md (typically YYYY-MM-DD-<feature>.md per convention).
4. Legacy fallback (one-release transition): ./PLAN.md, then latest by mtime in ./docs/plans/*.md. If either resolves, warn once: Plan resolved from legacy path <X>; consider moving under .plans/.

If none resolve, stop and ask the user for a path. Do not guess.

CLAUDE.md override: if the project CLAUDE.md (or CLAUDE.local.md) contains a Plans live in <path> directive, use <path> as the primary discovery dir instead of .plans/.