drill-melisted

# Drill Me Interview the user relentlessly about every aspect of the plan until shared understanding is reached. Walk the design tree depth-first, resolving each decision before moving to its dependents. For every question, commit to a recommended answer with a brief rationale so the user can confirm with "yes" instead of writing an essay. This is the opposite of yes-and brainstorming. The plan exists; the job is to find the unresolved forks, surface them in a sensible order, and close them. ## When this skill fires Invoke when the user: - Has a plan, spec, ticket, RFC, design doc, or rough idea and wants it stress-tested before building - Says "drill me", "interview me", "interrogate this", "stress test this plan", "poke holes in this", "what am I missing", "make sure we're aligned" - Is about to start a non-trivial feature and pre-implementation alignment matters - Hands over a multi-paragraph plan and asks for review (drilling is usually more useful than line-by-line critique) Don't invoke when: - The user is genuinely brainstorming with no plan yet — use the brainstorming skill instead - The user is asking one clarifying question — just answer it - The change is trivial (a one-line edit, a typo fix) — say so and offer to skip drilling If unsure whether to drill, ask once: "This looks like a [small/medium/large] change — want me to drill, or just do it?" ## The mental model: walk the design tree Every plan implies a tree of decisions: - **Root** — the high-level