# Grilling

> Use when the user asks to grill or stress-test a plan, decision, or idea.

- Skill: `sreejithraman/grilling` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add sreejithraman/grilling`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sreejithraman/grilling/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sreejithraman (https://skillmd.com/u/sreejithraman)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/sreejithraman/grilling

---


Settle the decisions that change the result, one round of questions at a time. 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 a frontier decision only when it would change the outcome and you can't tell what the user would choose. Always ask one that risks data loss, exposes private data, weakens security, or can't be undone. Put the rest in one **Assuming** block after the questions, one line each, including any detail you can recommend that is easy to change later. An answer that picks a direction settles that decision; don't ask the user to justify it. Ask the questions in one round, highest stakes first: number each question and give your recommended answer. Then wait for the user's answers before the next round.

Each question should be formatted like so:

```
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>
```

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. While the user's answers are pending, keep doing discovery that no open answer changes and that changes nothing outside the session: reading, lookups, and throwaway experiments.

The session is done when no open decision would change the result and nothing is left silently assumed. The user's substantive answers are their confirmation: answering a round accepts its Assuming block, except the lines they correct. Return the decisions and one Assuming block that gathers every round's assumptions to your caller, or give them to the user when they started the grilling. A decision you were required to ask stays open until the user answers it; never act on it as assumed. Grilling starts no work the request didn't already authorize.

