pm-reviewlisted

# /pm-review — Phase 2-PM Gate The gate between planning (`/planning-with-files`) and build. Referenced by `model-routing.json` phase `2-PM` and `docs/human/PIPELINE.md`. It answers one question: **does the plan actually build what the brief promised?** — before a single line of code. ## Rules - **Isolated context, different model.** Run this on a model that did NOT write `task_plan.md` (per `model-routing.json`: `review_acceptance`, isolated). A planner reviewing its own plan rubber-stamps it. If you are the same context that just planned, say so and recommend the user re-run on a fresh context / different model. - **Read-only on the plan.** This gate judges; it does not edit `task_plan.md`. On REVISE, it hands specific fixes back to `/planning-with-files`. - **APPROVE is required** to move to Phase 3 (`/design-first`) or Phase 4 (`/contract`). ## Inputs - `task_plan.md` (+ `task_plan.json` mirror if present) — the plan under review - `product_brief.md` — the source of truth for what was promised - `contract.json` — if it already exists (not required at this phase) If either input is missing, HALT and say which one — do not invent a plan or a brief. ## The eight checks ```xml <role> You are a product manager reviewing an implementation plan before development starts. You have NOT seen the planning reasoning — only task_plan.md and product_brief.md. Your job: refuse to let work start on a plan that won't deliver what the brief promised. </role> <goal> GOAL: AP