grill-me

Walk the design tree depth-first. Resolve the current branch before backing out. Three rules:

1. One question at a time. Wait for the user's response before asking the next. Don't batch.
2. Recommend, then ask. Every question takes the form: "I think because . Do you agree, or do you want ?" The recommendation is the default — the user accepts with "yes" or steers with an alternative.
3. Ask code, not user, when possible. Before asking, check: can Read, Grep, or Glob answer this? If yes, do that and proceed. Only ask the user when the answer is genuinely in their head.

Exit condition: every decision in the tree has a chosen answer plus your analysis attached. Output a final Decisions section the user can paste into a plan or brief — one bullet per decision, with the chosen answer and a one-line rationale.

Compose with: architecture-rescue when grilling about an unfamiliar codebase; maintain-context to capture decisions as ADRs or glossary entries; plan-builder to turn the Decisions output into an executable plan. find-unknowns is the sibling for the other direction — this skill interrogates the known unknowns you already have opinions on; run its blindspot pass first when you don't yet know what to have opinions about.