Skip to content
Development
Skill

/grilling

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.

BOOST
From plugin
dotclaude
59683 skills7 agents4 commands3 MCP
Install
$ npx -y skills add FradSer/dotclaude --skill grilling --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/grilling

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

grilling.SKILL.md
name: grilling
description: 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.

Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Use the AskUserQuestion tool to ask each question; one question per call, waiting for the answer before continuing. Give 2–4 options per question, put your recommended option first marked "(Recommended)", and rely on the tool's built-in "Other" option for answers you didn't anticipate. Asking multiple questions at once is bewildering.

If a *fact* can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The *decisions*, though, are mine: put each one to me via the AskUserQuestion tool and wait for my answer.

Do not act on it until I confirm we have reached a shared understanding.

CRITICAL: One question at a time: facts you look up, decisions the user makes

Ask each question via the AskUserQuestion tool, one question per call, waiting for the answer before continuing; multiple questions at once is bewildering. Put the recommended option first, marked "(Recommended)"; the tool's built-in "Other" option covers anything unanticipated. If a fact can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking. The decisions are the user's: put each one to them, and do not act until they confirm shared understanding.

Read more
Ships withdotclaude

A curated collection of 22 plugins for Claude Code, providing specialized agents, skills, and automation tools for development and productivity workflows.

Get the whole plugin

Other skills on dotclaude.