Individual skill

grill-me

Interview the user relentlessly about a plan, design, or idea until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, validate an idea, get grilled on their design, or says "grill me".

skills/grill-me/SKILL.md

Read pinned source

Source commit bc5e2cd450b25fa64e4ba3127f3e9b6ab33923c3

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 85
Repository last updated: Nov 3, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
claude-code Repository topic
claude-skills Repository topic
spec-driven-development Repository topic
design Derived category
testing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 1,129 bytes

Read excerpt


Interview the user relentlessly about every aspect of their plan, design, or idea until you reach
a shared understanding. Walk down each branch of the design tree, resolving dependencies between
decisions one by one.

- One question at a time, each with your recommended answer, worded so that "yes" accepts it, via
  `explain-in-simple-language` when available.
- Facts are yours to find (codebase, docs, tool output): look them up, never ask. Decisions are
  the user's: put each one to them and wait.

Done when no branch is open and nothing is silently assumed. Then print the settled decisions as a
short list (decision, chosen answer, one-line why) the user can paste into the plan, ticket or
doc, and stop: act on it only after the user confirms.