About batch-grill-me
An interview skill that guides users through design decisions using a branching tree. It asks all currently answerable questions in numbered rounds, recommends answers, and handles environmental fact-finding through sub-agents rather than asking the user to investigate.
Key features
- 01Branching design-decision tree
- 02Frontier-based question rounds
- 03Numbered questions with recommendations
- 04Sub-agent fact-finding
- 05Waits for confirmation before action
Use cases
- 01Clarifying requirements for a new design
- 02Resolving dependent decisions in sequence
- 03Investigating environment facts while discussion continues
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/batch-grill-mein Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMEInterview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.
Work the tree in rounds. The frontier is every decision whose prerequisites are already settled — the questions you can ask now without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
Each round the user answers reshapes the tree — settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.
Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it — don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report — ask the rest of the frontier now. The decisions are the user's — put each to them and wait.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.