mcpField
M
matt-grilling

matt-grilling

github.com/learnpromptProductivity88230 installsUpdated 1w ago
Repository

About matt-grilling

matt-grilling is a skill for agents conducting structured requirements interviews. It organizes decisions into a branching design tree, asks all currently answerable questions in rounds, and waits for confirmation of shared understanding before action.

Key features

  1. 01Maps decisions into a branching tree
  2. 02Asks questions in dependency-aware rounds
  3. 03Recommends an answer for each question
  4. 04Delegates environment fact-finding
  5. 05Waits for confirmation before acting

Use cases

  1. 01Clarifying requirements for a new feature
  2. 02Resolving dependent product decisions
  3. 03Gathering input without asking for discoverable facts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/learnprompt/laoyeye --skill matt-grilling

After installing, type/matt-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.

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.

Comments

Markdown supported