plan-reviewlisted

# plan-review — voidcorp craftsman edition `brainstorming` pressure-tests the idea and `writing-plans` authors the plan. This skill sits between the written plan and implementation: it **critiques an already-written plan** from up to four expert lenses, surfaces findings one decision at a time, and appends an Implementation Tasks list to the plan. It is read-mostly — it **proposes**; the plan's author (you, via `writing-plans`) **disposes**. It never writes code and never restructures the plan itself. Invoke it on a plan in `docs/specs/` or `plans/` before the plan becomes tickets. Pick one lens, several, or `all` (the orchestrated pass, below). **Attribution**: see `.source`. Distilled from gstack `/plan-ceo-review`, `/plan-eng-review`, `/plan-design-review`, `/plan-devex-review`, `/autoplan` (methodology only; the runtime and the named-founder rosters are rejected). --- ## The shared contract (every lens obeys this) - **Scope gate first.** Before reviewing, state what the plan touches and what is explicitly NOT in scope. A plan touching > 8 files or > 2 new services is a size smell — flag it before anything else. - **One finding = one decision.** Surface findings interactively, one at a time, each as a concrete decision with 2-3 options (always including "do nothing / defer") and a recommendation mapped to a stated preference. Never dump a wall of findings. - **Severity**: `P1` blocks ship · `P2` same-branch follow-up · `P3` later. Effort is dual-scaled (human hours v