review-plan

Review Plan — External Consultant Validation

External consultants + codebase verification catch plan flaws before execution begins.

Workflow

digraph review_plan {
  rankdir=TB;
  node [shape=box];

  locate [label="Step 1: Locate Plan"];
  verify [label="Step 2: Codebase Verification"];
  launch [label="Step 3: Launch Consultants\n(gemini + codex in parallel)"];
  synthesize [label="Step 4: Deduplicate & Synthesize"];
  present [label="Step 5: Present Structured Output"];
  decide [label="Step 6: User Decision"];

  locate -> verify -> launch -> synthesize -> present -> decide;

  decide -> execute [label="Ready to execute"];
  decide -> revise [label="Needs revision"];
  decide -> discuss [label="Needs discussion"];

  execute [label="Offer execution handoff" shape=ellipse];
  revise [label="List specific changes\nAsk: revise or proceed?" shape=ellipse];
  discuss [label="Present trade-offs\nfor user decision" shape=ellipse];
}

Step 1: Locate Plan

Check these sources in order — use the first match:

• Explicit argument: If the user provided a file path, use it
• Conversation context: If a plan was written or pasted earlier in this conversation, use that content
• Plan directory discovery: From the repository root, search both plan directories and use the most recently modified .md file:

  ls -t .dev/cdt/plans/*.md docs/plans/*.md 2>/dev/null | head -1
  

  Note: Run this from the repo root, not from the skill directory.

If no plan is found, ask the user with AskUserQuestion.

Read the full plan content before proceeding.

Step 2: Codebase Verification

Verify every concrete claim in the plan against the actual codebase. Check ALL of:

Claim Type	Verification Method	Failure =
File paths (modify/delete)	Glob for existence	Critical — plan references nonexistent files
File paths (create)	Verify parent directory exists	Note — files being created are expected to be absent
Line numbers	Read the file, check lines match	Warning — line numbers may have drifted
API signatures	Grep for function/method names, verify params	Critical — API has changed
Import paths (relative only)	Glob for referenced module path, then Read to confirm expected export — skip package imports (react, lodash) and alias imports (@/lib/db)	Critical — module doesn't exist or export is missing
Duplicate work	Grep for existing implementations	Warning — feature may already exist
Test files	Glob for existing test files in same area	Note — tests may already cover this