The /grilling Skill

What it does

grilling is the interview loop that stress-tests a plan, a decision, or an idea before anyone acts on it. It maps the subject as a design tree: every decision branches into the decisions that hang off it, and interviews you branch by branch until no assumption stays unstated.

It does not ask one question at a time, and it does not ask everything at once. Each round asks the whole frontier: every decision whose prerequisites are already settled, and nothing else. Two questions never share a round if one depends on the other; a question that hinges on an answer still open belongs to a later round. Your answers settle decisions, the frontier moves outward, and the next round asks what that unblocked. Thirteen questions typically land in about three rounds rather than thirteen.

When to reach for it

Type /grilling, or the agent reaches for it on its own when a task fits. It is the only skill in the grilling family that is model-invoked, so you rarely type it. Usually a skill you did type runs it for you.

Typing /grilling directly gets you the plain interview and nothing else. Where you want something more than that:

What you have	Reach for
You aren't working in a working directory	grill-me: the same session, under a name the agent will never fire by itself
You are in a working directory	grill-with-docs: the same session, and it writes `GLOSSARY.md` and ADRs as it goes
An effort too big to hold in one session	wayfinder: it charts a map and runs grilling inside the decision tickets
A question that talking cannot settle: how something should look or feel	prototype: build the throwaway version, then come back
A skill of your own that needs an interview	Invoke `/grilling` from it, rather than writing another interview

The round, the frontier, and who decides

The skill rests on three ideas.

The design tree is the model of the subject: decisions with decisions hanging off them. The frontier is the set of decisions whose prerequisites are all settled: the only questions the agent can ask yet. A round is one frontier, asked in full and answered in full.

Inside a round, every question has a fixed format: numbered and titled behind a ❓, then the body, then the agent's recommended answer alone on a ➡️ line. This format lets you answer a round by number ("1 yes, 2 the second option, 3 no, here's why") instead of by quoting questions back. The format has one known problem. The recommendation sometimes argues against the question as it was worded, so agreeing with the recommendation means answering "no" to the question. When that happens, answer the recommendation and say so.

The other half of the design is the split between facts and decisions. Facts are the skill's own job. When a frontier question needs something the environment can settle, the agent dispatches a sub-agent to find out rather than asking you. The round does not wait for that research; only the questions that depend on it wait. Decisions are yours, and the agent must wait for them. An agent running grilling that answers its own decisions has broken the skill. The session ends when the frontier is empty. The agent then waits for you to confirm a shared understanding before it acts on what you agreed.

The frontier has one limit. The agent chooses it by judgement; it does not compute it from a graph. So it can put two questions in one round and only later find that one answer should have changed the other. The only guard is to tell it. That reopens the affected branch in the next round.

What lives here and what lives in the wrappers

This page covers the mechanism. The wrapper skills' pages answer the questions people ask most often.

Question	Where it is answered
The tree, the frontier, rounds, the question format, facts vs decisions	Here
How long a session should run, what to do with a question you can't answer by talking, how to avoid nodding along	grill-me
What gets written to `GLOSSARY.md`, what becomes an ADR	grill-with-docs

Common questions

Can I go back to one question at a time? Yes, and a large part of the audience does. Add this to your global CLAUDE.md:

When grilling, ask one question at a time.

Not everyone prefers the round-based default. Users who read slowly, who work in a second language, or who use the sequential format to help them focus report that one question at a time works better for them. The opt-out is a supported setting, not a workaround.

Where did /batch-grill-me go? Into this skill. Round-based questioning shipped briefly as a separate skill, then moved into grilling itself, so everything built on the primitive (grill-me, grill-with-docs, triage, wayfinder) got it at once. There is no batch-grill-me to install, and no separate sequential skill either; the CLAUDE.md line above is the way back to one-at-a-time.

Asking a whole round at once must lose the questions my earlier answers would have raised. Doesn't it? This is the most common objection to rounds, and the frontier answers it. A round only contains questions that do not depend on each other, so no answer in a round can invalidate another question in that round. Your answers still change what comes after them, because the agent works out each next round from scratch. You do lose something, but less than "all questions at once" implies. See the frontier's limit above.

It ran out of questions and started building. The confirmation gate exists for this. The skill is finished when you say the understanding is shared, not when the frontier empties. Weaker and faster models still skip the gate. Users report this most often on lower-effort or non-frontier models, which collapse "interview until shared understanding" into a couple of questions and an outline. If yours does it, the reliable fix is a line in your own AGENTS.md or CLAUDE.md telling the agent not to implement without permission.

It answered its own questions instead of asking me. That is a bug in the run, and it is the reason the skill's text separates facts from decisions. It happens most when another skill runs grilling to resolve a ticket, and the agent takes that task as permission to keep moving. The same constraint is why there is no async mode. People have asked for a variant that reads a GitHub issue and posts one consolidated decision memo, and that is a different skill, because a grilling session that nobody answers has produced the agent's opinion rather than yours.

Can I cap the number of questions? No, and a cap is out of scope on purpose. Some plans need three questions and some need fifty; a fixed ceiling either truncates the hard case or feels arbitrary on the easy one. The intended control is plain language. Tell it to wrap up, or stop and accept the plan where it stands. If a session is running very long, the cause is usually that the scope was too big; break the work up and grill the pieces.

I installed grill-me on its own and nothing happens. grill-me is a one-line skill whose whole body is "run a /grilling session", so it needs this skill installed too. The same is true of grill-with-docs, which additionally needs domain-modeling. Installing the whole set avoids the problem; installing selectively means installing the primitives as well.

grill-with-docs ran, but it never loaded grilling. This is a real bug, still unfixed, and users report it across harnesses and models. A skill that names another skill does not reliably cause that skill to load, and grill-with-docs names two. The sign is a session that asks everything at once with no recommendations. That means the model is improvising an interview rather than running this one. Asking the agent directly whether it loaded grilling and domain-modeling usually recovers it.

It's working if

A round arrives as a numbered list, each question with its recommendation on a separate ➡️ line, and you can answer the whole round by number.
Nothing in a round needs another question in the same round answered first.
Later rounds ask things the first round could not have asked.
It goes and looks facts up (reading files, dispatching a sub-agent) rather than asking you something it could have found out.
Research running in the background does not stall the round; only the questions that depend on it wait.
It stops at the end and asks you to confirm the understanding is shared, instead of starting work.
Question count stays high while round count stays low.

Where it fits

grilling is a primitive, not a step you schedule: the single source of truth for the interview technique, kept in one place so every skill that needs an interview reaches for it instead of inventing one. grill-me and grill-with-docs are its two user-invoked front doors, and grill-with-docs is where the main build chain begins, ahead of to-spec. wayfinder runs it to resolve decision tickets, triage to grill a vague report into a workable one, and improve-codebase-architecture to walk the tree once you have picked a candidate to deepen. When you are unsure which entry point fits, ask-matt routes you.