review-plan

/volley:review-plan

Hand a plan to Codex. Get back a review. Write it to disk, show it inline.

Steps for Claude

1. Verify .volley/ is initialized and the lock allows Claude to act.

   [ -d .volley ] || { echo "ERROR: .volley/ not found. Run /volley:setup first." >&2; exit 1; }
   [ -f .volley/STATE ] || { echo "ERROR: .volley/STATE not found. Run /volley:setup first." >&2; exit 1; }
   . "${CLAUDE_PLUGIN_ROOT}/scripts/lib.sh"
   volley_state_assert_active .volley/STATE claude || exit 1
   

   If the assert fails, the helper already printed a refusal message. Stop.

2. Resolve the plan path.

   • If user passed a path argument, use it.
   • Otherwise: ls -t .planning/**/PLAN.md 2>/dev/null | head -1 (or use Glob tool with pattern .planning/**/PLAN.md and take the most recent by mtime).
   • If no plan found, tell user "No PLAN.md found under .planning/. Pass an explicit path, or check that you've run /gsd:plan-phase to create one." and stop.

3. Read the plan and HANDOFF.

   • Read the plan file's full content.
   • Read .volley/HANDOFF.md for acceptance criteria.

4. Build the review prompt for Codex.

   The prompt to send via mcp__codex__codex (the only Codex session-start tool the MCP server exposes; older docs may say mcp__codex__review or mcp__codex__exec - those names are wrong):

   You are reviewing an implementation plan. Be specific and concrete.
   
   ACCEPTANCE CRITERIA (from HANDOFF.md):
   <paste HANDOFF.md content>
   
   PLAN TO REVIEW:
   <paste plan content>
   
   Provide your review in this format:
   
   ## Verdict
   APPROVE | CONCERNS | REJECT
   
   ## Strengths
   - (specific things the plan gets right)
   
   ## Concerns
   - (specific issues, with file/line refs from the plan if applicable)
   
   ## Suggested changes
   - (concrete edits, not vague advice)
   
   Keep it under 500 words. Skip filler.
   

5. Resolve the review role's model/effort/context from config. Read .volley/config.json (parse it yourself; absent = defaults). Take codex.review.model, codex.review.reasoningEffort, and apply any .volley/local.json modelOverrides.review. Check context.required files all exist - if any is missing, stop with a clear error naming the file (fail early). Note which context.optional files exist; missing optional files are reported and skipped.