agentleFS
Sign inStart free
ehnruizehnruiz/claude-skills/skills/grilling/SKILL.md

grilling

Skill3 starsChanged 29 days agoMITView on GitHub

Grill the user relentlessly about a plan, decision, or idea until every branch of it is settled. Use when the user wants to stress-test their thinking, says "grill me", "poke holes in this", "interrogate this plan", or asks to be questioned before building something.

193 other projects use a version of this, 142 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • The-Vibe-CompanySkill

    capture-learning-tools

    Turn technical conversations, bugs, CI failures, review comments,

    Also in 5 projects that use this

  • The-Vibe-CompanySkill

    design-frontend-dev

    Clean Impeccable frontend design skill. Use when the user wants to

    Also in 5 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 58 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 136 projects that use this

  • +3 more from The-Vibe-Company

The file

Create a free account to mount
Files
SKILL.md

Grilling

Interview the user relentlessly until you reach a shared understanding. Credit and license: LICENSE.md in this folder.

Map the plan as a design tree: every decision branches into the decisions that hang off it.

Rounds

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. Word each question so "yes" accepts your recommended answer, so agreeing never means answering "no". 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.

Facts are yours, decisions are theirs

Finding facts is your job, never the user's. When a frontier question needs a fact from the environment (the code, the docs, a config, a tool's output), look it up: hand it to a background subagent if you have one, otherwise read it yourself. Never ask the user for anything you could look up. Don't block on a lookup: a running search is an unsettled prerequisite, so only the questions downstream of it wait; ask the rest of the frontier now.

The decisions are the user's: put each one to them and wait.

Done

The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Close with the settled decisions as a short list. Do not act on them until the user confirms you have reached a shared understanding.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free