How do I install the Grill skill?

Run npx skillmds@latest add kirodotdev/grill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Grill safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Grill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Grill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

kirodotdev (@kirodotdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Grill by kirodotdev — Agent Skill

Name: Grill
Author: kirodotdev

Grill

Structured questioning to reach shared understanding before action. Walks the decision tree one branch at a time, checks memory for already-answered questions, saves every answer as a lesson. Use when user wants to think through a plan, align on approach, poke holes in a design, or figure out decisions before committing.

kirodotdev 0d126ad 2.2 KB Updated Sep 17, 2026

File contents

Grill: one decision at a time

HARD RULE: One Question Per Turn

Your response MUST contain exactly ONE question. No exceptions. No "also" or "a few things." One question → wait → next question. Self-check: if you count more than one ? outside of quotes, delete the extras.

Activation

Explicit triggers ("grill me", "interview me", "challenge this"): Start immediately with the banner then ONE question:

🔥 Grill Mode — one concern at a time. Say "enough" when ready to move on.

Ambiguous triggers ("poke holes", "what am I missing", "think this through", "help me decide", etc.): Ask first:

One at a time, or full critique dump? [OPTIONS: Grill me one at a time | Just give me the full critique]

Turn Structure

Every grill turn = exactly this:

Context (1-2 sentences) — why this matters
Question — one decision only, ending with ?
My recommendation — what I'd pick and why (one line)

Rules

Facts vs Decisions: Look up facts silently (code, config, memory). Only ask about decisions the user must make.
Memory: Check lessons/memory first. If already decided, confirm: "Previously you decided X. Still holds?"
Save answers: learn_add(rule="<decision>", category="knowledge") after each. Put the alternative the user rejected in negative — a grill turn resolves a decision by ruling something out, and that half is what stops the question being re-asked. Add repo_scope="<path fragment>" only when the decision is true of one codebase; there is no scope parameter.
Document decisions: After 3+ decisions, offer once to capture them in a doc.
Exit: On "enough"/"just do it" → summarize decisions, proceed to action. Don't implement mid-grill.
Simple plans: If the plan is clear and simple, say so — don't manufacture questions.

---name: grilldescription: Structured questioning to reach shared understanding before action. Walks the decision tree one branch at a time, checks memory for already-answered questions, saves every answer as a lesson. Use when user wants to think through a plan, align on approach, poke holes in a design, or figure out decisions before committing.---# Grill: one decision at a time## HARD RULE: One Question Per TurnYour response MUST contain exactly ONE question. No exceptions. No "also" or "a few things." One question → wait → next question. Self-check: if you count more than one `?` outside of quotes, delete the extras.## Activation**Explicit triggers** ("grill me", "interview me", "challenge this"):Start immediately with the banner then ONE question:> 🔥 **Grill Mode** — one concern at a time. Say "enough" when ready to move on.**Ambiguous triggers** ("poke holes", "what am I missing", "think this through", "help me decide", etc.):Ask first:> One at a time, or full critique dump?> [OPTIONS: Grill me one at a time | Just give me the full critique]## Turn StructureEvery grill turn = exactly this:1. **Context** (1-2 sentences) — why this matters2. **Question** — one decision only, ending with `?`3. **My recommendation** — what I'd pick and why (one line)## Rules- **Facts vs Decisions**: Look up facts silently (code, config, memory). Only ask about decisions the user must make.- **Memory**: Check lessons/memory first. If already decided, confirm: "Previously you decided X. Still holds?"- **Save answers**: `learn_add(rule="<decision>", category="knowledge")` after each. Put the alternative the user rejected in `negative` — a grill turn resolves a decision by ruling something out, and that half is what stops the question being re-asked. Add `repo_scope="<path fragment>"` only when the decision is true of one codebase; there is no `scope` parameter.- **Document decisions**: After 3+ decisions, offer once to capture them in a doc.- **Exit**: On "enough"/"just do it" → summarize decisions, proceed to action. Don't implement mid-grill.- **Simple plans**: If the plan is clear and simple, say so — don't manufacture questions.

Frequently asked questions