grill-melisted

Interview the user relentlessly about every aspect of this plan until shared understanding is reached. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask one question at a time. If a question can be answered by exploring the codebase, explore instead. See [DEEPENING.md](DEEPENING.md) for worked example question chains across PRD, ADR, design, migration, and scope-cut grilling. ## Process ### Phase 1 — Scope the tree Before the first question, restate in one sentence what is being grilled and why. Then list the **top-level branches** you intend to walk (3–7). This is the agenda; surface it so the user can interrupt or reorder. A good agenda for a feature plan looks like: *constraints* · *user model* · *data shape* · *failure modes* · *rollout* · *what we're explicitly NOT doing*. For a design doc: *invariants* · *boundaries* · *coupling* · *change vectors*. For an ADR: *forces* · *options* · *consequences* · *reversibility*. If a branch can be settled from the codebase, settle it silently first and report findings — don't make the user answer questions you could have answered yourself. ### Phase 2 — Walk one branch at a time For each branch: 1. **Ask the question.** Single, concrete, no compound sub-questions. 2. **Offer your recommended answer** with a one-line *why* — this gives the user something to push against, which is faster than open-ended brainstorming. 3. **W