rad-planner

Plan a project before you write code — and re-plan it as reality unfolds. Built for solo developers who aren't formally trained engineers: it interrogates you until it actually understands what you're building, then produces a plan a moderately experienced vibe coder can read AND a coding agent can execute. Strictly a planner — it never writes implementation code. The method is interview-driven, risk-first, adversarially-reviewed, and mechanically-validated: - The grilling: a structured discovery interview — eight coverage areas (end goal, users, MVP, success criteria, constraints, assets, exclusions, danger zones), each driven to settled-or-explicitly-unknown; the project mirrored back for correction; assumptions proposed for confirm/deny. Capped at 3 rounds so it stays fast. Pre-fills from the repo AND from dated spec docs (docs/*-spec.md, docs/*-design.md) — a brainstorm or design spec gets confirmed ("the spec says X — still true?"), never re-asked. - One vocabulary, the naming ladder: Goal (the end state, in the PRD) → Release (Now / Next / Later horizons) → Milestone (M1…) → Task (T1…). No phases, sprints, epics, slices, or stages as units of work. The PRD speaks Goal/Release; plan.md speaks Milestone/Task. The repo's AGENTS.md doc-model block is authoritative when present; these defaults match it. - The release ladder in practice: every plan anchors to your end goal via the Now / Next / Later release map — Now (MVP/Beta, fully specced tasks), Next (V1 milestone outline), Later (end-goal themes). Detail decays with distance by design; pulling the next horizon into detail is a /replan event. - Written for two readers: a plain-language layer (how-to-read note, release map, 'After this ships' lines, technical terms glossed on first use) for you; six-field task blocks (objective, files, dependencies, done-when, validation, rollback) for the coding agent. - The seed packet: /plan ends by routing planning's structured leftovers onto the repo's doc shelf — stack choice + why appended to docs/decisions.md, cut features and stray ideas appended to docs/ideas.md, an AGENTS.md stack block proposed (owner applies), architecture/api docs seeded only when their triggers fire. Never creates docs for "Later" work, status/roadmap files, or empty scaffolds. - Codegen-aware stack evaluation (AI-native Golden Path matrix), goal-backward decomposition, risk-first sequencing with size discipline. - Mechanical validation via `plan-lint.py` (required sections incl. the release map, per-task fields, dependency resolution + cycles, vague language) — a real pass/fail check, not the model grading itself. - Adversarial review via the `risk-assessor` agent against 14 documented anti-patterns (APPROVE / REVISE / RETHINK; iterative on the full path, single-pass on the quick path you can choose at discovery). Gatekeeping follows challenge-once-then-commit: one honest assessment, then full execution on your confirmation, logged as a decision. Four skills — two doors in, one maintained plan: - `/plan` — greenfield or a clear next effort: the six-step conversation → `docs/plan.md` + the seed packet. On a bare repo (no AGENTS.md, no docs/) it recommends /rad-repo-manager:repo-init first and degrades gracefully without it. - `/rescue` — a project in an unclear state: read-only archaeology (code + git evidence), evidence-led interview (keep/cut/unknown per piece), then a fresh release-map plan from where the project actually is. Runs after /rad-repo-manager:adopt when structure is the mess — adopt is structure archaeology, rescue is intent archaeology. Assesses and plans; never fixes, runs, or deletes code. - `/replan` — the single deliberate direction-change moment: marks shipped work from git + handoff (moved to a `## Shipped` section — history preserved, never deleted), gives every parked idea in docs/ideas.md a fair hearing (pull in / keep parked / reject with a recorded why), re-baselines the rest, pulls the next horizon into detail when Now ships. - `/review-plan` — two-layer quality audit of an existing plan (mechanical lint + adversarial risk review). The PRD exception: when `docs/prd.md` is missing or skeletal, the planner offers to draft it — each section written from your own interview answers, applied only on per-section confirmation. After that birth the PRD is yours (rad-repo-manager keeps it fresh); the planner never edits an existing PRD. Changes to docs it doesn't own go into a paste-ready `docs/[date]-update-prompt.md` for you to apply — durable docs stay under your control. Pairs with rad-repo-manager (which owns the doc model the planner conforms to, and maintains plan.md status and PRD freshness between plans); works standalone. Two agents: `stack-advisor`, `risk-assessor`.