--- name: mattpocock-grilling description: "Interview a design through questions." license: MIT metadata: source: mattpocock/skills source-commit: 4ae2317ddb22b046e26455e4f9c9b3aaaf62212d upstream-name: grilling upstream-status: published adaptation: namespaced-port --- ## Skillz integration This is Matt Pocock's version. Skill references use the `mattpocock-` prefix. Read a referenced skill's `SKILL.md` through the host's skill loader or file tools. Map AskUserQuestion to the host's question tool and shell examples to its shell. Use delegation only when available and permitted by the active instructions; otherwise perform the same work sequentially and report that limit. The user's scope and repository rules govern setup, file writes, tracker changes, messages, schedules, publishing, merging, and cleanup. A skill invocation alone does not broaden the user's request. Preserve existing work and configuration. Verify provider examples against current primary documentation before use. 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. Format a round like so: ``` ❓ **Q1** - ****: ➡️ --- ❓ **Q2** - ****: ➡️ ``` Word each question so "yes" accepts 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 with a fresh context window 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.