plan-reviewlisted

Pre-flight review of a software plan that hunts for the decisions an implementer will be forced to make that the plan has not made — and proposes each one — so the plan itself is the decision record and no ADRs are needed mid-build. Runs inline in a single context (no subagents). Produces a verdict (NOT READY / READY AFTER DECISIONS / READY), a decision ledger with a proposed resolution per open fork, an implementer dry-run, a reality check against the real repo and cluster, hard safety caps, and a compact structural sweep. `--lock` writes accepted decisions into the plan where an implementer will actually read them. Use before implementation begins, before decomposing a plan into beads, or whenever a project keeps spawning ADRs after the plan was "done".
jedarden/jeds-curated-skills · ★ 0 · Code & Development · score 75

Install: claude install-skill jedarden/jeds-curated-skills

# Plan Review **Thesis.** In-flight pivots are not caused by missing section headers. They are caused by *unmade decisions* meeting reality: an implementer (increasingly an autonomous worker holding one bead, unable to ask) reaches a fork the plan never chose, guesses, and the guess is later ratified or reversed as an ADR. Every post-hoc ADR is a decision the plan should have made. So this review does not grade a plan by how many of 83 headers it has. It asks one question, five ways: **what will the implementer have to decide that this document has not decided?** Then it proposes the decision — with rationale, the rejected alternative, the test that enforces it, and the signal that would reopen it — so the human's job shrinks to saying "yes". **Run everything inline.** Do not spawn subagents for judgement; the plan must stay in one context so that the dry run, the ledger, and the proposed decisions are consistent with each other. Plans up to ~6k lines fit; for larger ones read in section-sized chunks, never skim. ## Step 0 — Resolve the plan and the mode - Path argument → use it. Otherwise exactly one `docs/plan/plan.md` under cwd → use it. Otherwise scan `**/plan.md`, `**/PLAN*.md`, `**/design.md`, `**/ARCHITECTURE.md`; if several, AskUserQuestion once. - `--fast` → follow `runbooks/FAST-PATH.md` (caps + forks only, ~5 minutes) and stop. - `--lock …` → a memo from a previous run must exist next to the plan (Step 6 names where); follow `runbooks/LOCK.md` and stop.