review-plan

# Review Plan Review implementation plans created by `superpowers:writing-plans` before execution. ## Arguments - Path: Plan file to review (e.g., `docs/plans/2025-01-15-auth-feature.md`) ## Hard gates (sequence) Do not skip ahead; each step **passes** only when the condition is objectively satisfied (artifact path, tool success, or labeled capture—not “I read it mentally”). 1. **Plan file reachable** — **Pass:** `Read` (or equivalent) succeeds on `Path`; if not, stop and report the missing path. **Pass:** You can quote or point to where `**Goal:**`, `**Architecture:**`, and `**Tech Stack:**` appear, *or* you record “header field X absent” as a finding before Step 2. 2. **Skills loaded before agents** — **Pass:** For each row you will rely on in Step 2’s table, the corresponding skill is loaded via the `Skill` tool (or you record explicit `N/A` with reason, e.g. stack not present). Do **not** spawn Step 3 `Task` runs until this gate passes. 3. **Five reviews captured** — **Pass:** You have five labeled artifacts (one per agent): pasted outputs, task transcripts, or saved snippet files. **Pass:** Each of the five INVESTIGATE/CHECK/VERIFY prompts has a corresponding response block before Step 4. 4. **Review file on disk before user prompt** — **Pass:** The file at `[plan-dir]/[plan-basename]-review.md` exists; **Pass:** `Read` succeeds on that path. Only then run the “Next Steps” / options prompt in Step 5. ## Step 1: Read and Parse Plan Read the plan file and extract: ...