Plan Review Mode

Read workflow.md for detailed phases and anti-patterns.

Conduct a John Carmack-level review using RepoPrompt's context builder and chat.

Role: Code Review Coordinator (NOT the reviewer) Tool: flowctl rp wrappers ONLY

flowctl is BUNDLED with this plugin — do NOT check which flowctl. Use:

FLOWCTL="${CLAUDE_PLUGIN_ROOT}/scripts/flowctl"
$FLOWCTL rp <command>

Critical Rules

1. DO NOT REVIEW THE PLAN YOURSELF - you coordinate, RepoPrompt reviews
2. MUST WAIT for actual RP response - never simulate/skip the review, even in test environments
3. MUST use setup-review - handles window selection + builder atomically
4. DO NOT add --json flag to chat-send - it suppresses the review response
5. Re-reviews MUST stay in SAME chat - omit --new-chat after first review
6. If REVIEW_RECEIPT_PATH set: write receipt after chat returns (any verdict)
7. Any failure → output <promise>RETRY</promise> and stop

FORBIDDEN:

• Saying "this is a test" or "simulated" or "mock environment"
• Self-declaring SHIP without actual RP verdict
• Adding --json to chat-send (suppresses review text)
• Interpreting {"chat": null} as success (means you used --json incorrectly)
• Using --new-chat on re-reviews (loses reviewer context)

Input

Arguments: $ARGUMENTS Format: <flow-epic-id> [focus areas]

Workflow

FLOWCTL="${CLAUDE_PLUGIN_ROOT}/scripts/flowctl"
REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"

Step 1: Get Plan Content

$FLOWCTL show <id> --json
$FLOWCTL cat <id>

Step 2: Atomic Setup (MANDATORY)

eval "$($FLOWCTL rp setup-review --repo-root "$REPO_ROOT" --summary "Review plan for <EPIC_ID>: <summary>")"

Outputs W=<window> T=<tab>. If fails → <promise>RETRY</promise>.

Step 3: Augment Selection

$FLOWCTL rp select-get --window "$W" --tab "$T"
$FLOWCTL rp select-add --window "$W" --tab "$T" .flow/specs/<epic-id>.md

Step 4: Build Review Prompt

$FLOWCTL rp prompt-get --window "$W" --tab "$T"

Write prompt to /tmp/review-prompt.md with:

• Builder's handoff prompt
• Plan content from flowctl show
• Review criteria (simplicity, DRY, architecture, edge cases, security)
• Required verdict tag: <verdict>SHIP|NEEDS_WORK|MAJOR_RETHINK</verdict>

Step 5: Execute Review

$FLOWCTL rp chat-send --window "$W" --tab "$T" --message-file /tmp/review-prompt.md --new-chat --chat-name "Plan Review: <EPIC_ID>"

This command BLOCKS and returns the full review text (1-5+ minutes). DO NOT add --json.

Expected output format:

## Chat Send ✅
[Full review text from RP...]
<verdict>SHIP|NEEDS_WORK|MAJOR_RETHINK</verdict>

If you see {"chat": ...} instead of review text, you incorrectly added --json → RETRY.

Step 6: Write Receipt

if [[ -n "${REVIEW_RECEIPT_PATH:-}" ]]; then
  ts="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
  mkdir -p "$(dirname "$REVIEW_RECEIPT_PATH")"
  cat > "$REVIEW_RECEIPT_PATH" <<EOF
{"type":"plan_review","id":"<EPIC_ID>","mode":"rp","timestamp":"$ts"}
EOF
  echo "REVIEW_RECEIPT_WRITTEN: $REVIEW_RECEIPT_PATH"
fi

Step 7: Update Status

$FLOWCTL epic set-plan-review-status <EPIC_ID> --status ship --json
# OR
$FLOWCTL epic set-plan-review-status <EPIC_ID> --status needs_work --json

If no verdict tag → <promise>RETRY</promise>.

Fix Loop (INTERNAL - do not exit to Ralph)

If verdict is NEEDS_WORK, loop internally until SHIP:

1. Parse issues from reviewer feedback
2. Fix plan via $FLOWCTL epic set-plan <EPIC_ID> --file /tmp/updated-plan.md
3. Re-review in SAME chat (NO --new-chat):

   cat > /tmp/re-review.md << 'EOF'
   ## Fixes Applied
   [List each fix with explanation]
   
   Please re-review and provide verdict.
   EOF
   
   $FLOWCTL rp chat-send --window "$W" --tab "$T" --message-file /tmp/re-review.md
   

4. Repeat until <verdict>SHIP</verdict>

CRITICAL: Re-reviews must stay in the SAME chat so reviewer has context of previous feedback. Only use --new-chat on the FIRST review.