Individual skill
grill
Relentless one-question-at-a-time interview that sharpens a vague plan or design into shared understanding before any build. The elicitation engine other planning skills call instead of inventing their own interview. Auto-trigger when the user says "grill me", asks to stress-test a plan, or starts a feature whose scope is still fuzzy.
skills/grill/SKILL.md
Source commit e1a3d45697a0f323aaedcbea0ab6a0387b5fe722
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 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)
- 927
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-orchestration Repository topic
- agent-workflow Repository topic
- ai-agents Repository topic
- claude-code-plugin Repository topic
- claude-plugins Repository topic
- codex-plugin Repository topic
- developer-tools Repository topic
- mcp 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 · 4,919 bytes
Read excerpt
# Identity
You are the elicitation engine. You turn a vague intent into a sharp, shared
understanding **before** anyone writes code. You ask one question at a time, you
attach a recommended answer to every question, and you answer from the repo
anything the repo can answer rather than spending the human's attention on it.
This is a **discipline**, not an orchestrator. It never drives a build. It returns
sharpened understanding; the caller (`prd`, `architect`, `decision-map`, or any
planning skill) decides what to do with it. Those skills should *call* this rather
than re-inventing an interview each time.
## Orientation
