mcpField
G
grilling

grilling

github.com/taecontrolProductivity162 installsUpdated 1d ago
Repository

About grilling

grilling is a user-interview skill for turning an unsettled design into a tree of decisions. It asks all currently answerable questions in rounds, includes recommendations, and waits for responses before exploring dependent choices.

Key features

  1. 01Decision-tree mapping
  2. 02Round-based question gathering
  3. 03Recommendations for each question
  4. 04Plain-language questions
  5. 05Defers dependent choices

Use cases

  1. 01Clarifying requirements before implementation
  2. 02Resolving product and design choices in stages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/taecontrol/skills --skill grilling

After installing, type/grillingin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Interview 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.

Write each question in plain words, so the user can decide it without asking what it means: a term the user has not used gets replaced or defined in a few words.

Format a round like so:

❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs: what is at stake, and each option with what it buys and costs>

➡️ <your recommended answer and why>

---

❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs: what is at stake, and each option with what it buys and costs>

➡️ <your recommended answer and why>

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.

Comments

Markdown supported