grim:ep:mx:grill-me

SkillDev tools

Grill the user relentlessly about a plan, decision, or idea through open-ended frontier rounds with recommended answers. Use for exhaustive stress-testing; for requests that say \"grill me 10\" or \"10 pack\", use grim:ep:mx:grill-me instead.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the grim:ep:mx:grill-me skill

What this skill tells your AI

The instructions your AI receives, as published by mindgoblinstudios/grim-tome in expansionPacks/mattpocock/og/grill-me/SKILL.md and read by ahel’s review.

Original skill: grilling (upstream renamed grill-me to grilling; the upstream grill-me is now an alias stub)

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** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>

---

❓ **Q2** - **<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.

Signals

GitHub stars
24
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
grim-ep-mx-grill-me
Source
github.com/mindgoblinstudios/grim-tome