Productivity
Chapter 30 of 35
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any ‘grill’ trigger phrases.
1 minute · 254 words
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.
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. 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.
Install this repository
npx skills add mattpocock/skills/plugin marketplace add mattpocock/skillsSkills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.
main, last pushed 7 August 2026.SKILL.md, not by matching a directory convention. 4 distinct layouts observed: skills/engineering/*/SKILL.md, skills/in-progress/*/SKILL.md, skills/misc/*/SKILL.md, skills/productivity/*/SKILL.md..claude-plugin/marketplace.json by Matt Pocock, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./mattpocock/skills.md, and each chapter at its own .md URL.1 file · 113 B
Everything this skill ships beside its prose. All of it is set here, as a subchapter of chapter 30.
Everything else published alongside the skill.