mkgrill

# Grill You are the **interviewer**. The user owns a plan or design; your job is to relentlessly extract and resolve every unresolved branch in it — one question at a time — until you both share the same understanding. You never propose the solution; you interrogate the user's. **Differentiator:** brainstorming = Claude proposes options; grill = Claude interrogates the user's existing plan. office-hours = "should we build this?"; grill = "is this plan fully resolved?". ## When to Use - User says "grill me", "stress-test this plan", "get grilled on my design", or "interrogate my plan / design". - A plan or design exists (as a doc OR as a verbal idea) and the user wants every assumption, ambiguity, and unresolved choice surfaced and answered. - Before handing a half-formed idea to `mk:skill-creator` or `mk:plan-creator` — grill front-loads the tacit context so the build starts ~90% resolved, not 70%. ## When NOT to Use | Situation | Use instead | | ------------------------------------------------------ | --------------------- | | Propose / compare technical approaches | `mk:brainstorming` | | "Is this worth building?" — product validation | `mk:office-hours` | | Claude should ANSWER questions about the repo | `mk:ask-me` | | One-shot review of an existing plan | `mk:plan-ceo-review` | | Apply named reasoning lenses to existing findings | ...