grill-me
Skill2 starsChanged 5 months agoMITView on GitHub
Use when authoring an initiative, clarifying interdependent open questions, or designing a multi-quarter roadmap — depth-first one-at-a-time interrogation with agent recommendation + reasoning per question. Skip for bug-fix / implement / verify (too much friction).
193 other projects use a version of this, 66 of them edited.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
Used with
Projects with it also use brief-to-tasks, writing-beats 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.
julianoczkowskiSkillbrief-to-tasks
Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".
Also in 7 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 74 projects that use this
simo97Skillmigrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Also in 78 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 45 projects that use this
LesaniSkillwriting-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.
Also in 73 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 64 projects that use this
- +1 more from simo97
- +1 more from Lesani
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 66
- langfuse/langfuse★ 37k32% same
- humanlayer/humanlayer★ 13k33% same
- openstatusHQ/openstatus★ 9.3k36% same
- webiny/webiny-js★ 8.1k33% same
- sanity-io/sanity★ 6.4k36% same
- camunda/camunda★ 4.4k36% same
- event-catalog/eventcatalog★ 3k33% same
- Akylas/OSS-DocumentScanner★ 2.7k33% same
- openstatusHQ/data-table-filters★ 2.3k36% same
- owid/owid-grapher★ 1.6k32% same
56 more not listed
Wrote their own version · 127
- mattpocock/skills★ 325ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- nrwl/nx★ 29ksame name
- windmill-labs/windmill★ 19ksame name
- GreyDGL/PentestGPT★ 16ksame name
- jaredpalmer/kev★ 9.8ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- pollinations/pollinations★ 5.3ksame name
117 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- analyzeSkill
- animation-disciplineSkill
- api-versioningSkill
- autopilotSkill
- browser-e2eSkill
- characterizeSkill
- clarifySkill
- codemodSkill
- constitution-compactSkill
- constitutionSkill
- context-budgetSkill
- creative-webSkill
- db-migrationSkill
- debugSkill
- detect-stackSkill
- dispatch-criteriaSkill
- dreamSkill
- experimentSkill
- fastapiSkill
- flag-cleanupSkill
- flag-rolloutSkill
- flask-realtimeSkill
- framework-detectorSkill
- front-end-designSkill
- handoffSkill
- image-generationSkill
- implementSkill
- initiativeSkill
- instinctSkill
- loopSkill
- nextjsSkill
- observabilitySkill
- okr-alignSkill
- parallel-swarmSkill
- pivotSkill
- planSkill
- pr-bodySkill
- prime-disciplineSkill
- prod-observabilitySkill
- react-nodeSkill
- react-viteSkill
- release-trainSkill
- researchSkill
- reviewSkill
- security-guardSkill
- self-healSkill
- shipSkill
- skill-creatorSkill
- specifySkill
- tailwind-disciplineSkill
- tasksSkill
- tdd-loopSkill
- token-budgetSkill
- typographySkill
- verify-loopSkill
- verifySkill
- wip-checkpointSkill
- <kebab-case-skill-name>Skill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 179 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Use AskUserQuestion with the header field.
- Distinctive: line 60
Ask in dependency order. If Q2's answer depends on Q1, ask Q1 first.
- Distinctive: line 62
When you sense the operator is uncertain, ask a meta-question:
- Very specific: line 68
When running in unattended context (AUTOPILOT=1, Cloud Routine, claude --bg, claude -p):
- Very specific: line 70
Do NOT call AskUserQuestion.
- Distinctive: line 76
Never block on a human in autopilot.
- Distinctive: line 80
When the design tree is exhausted (no more questions whose answers materially shape the artifact), stop.
- Distinctive: line 90
Always provide a recommendation.
- Distinctive: line 91
Always provide reasoning. The operator should learn from the recommendation even when they override it.
- Distinctive: line 93
Don't grill beyond the depth that materially affects the artifact.
“Common” is measured: kept by at least 6 in 10 of the 179 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Grill me
Vendored from mattpocock/skills/skills/productivity/grill-me (commit
bd04394c). House-extended with recommendation format, codebase exploration policy, complexity gate, and AUTOPILOT bailout.
When to invoke
Auto-on:
/initiative create(every initiative, regardless of size)/specifyfor specs withcomplexity: Lorcomplexity: XL/clarifywhen ≥3[OQ]items cluster around one subsystem (interdependent)/okrs(when defining new KRs — they cascade)/roadmap(Now/Next/Later cuts — prioritisation cascades)
Hard-exclude (do NOT grill):
- Bug-fix /
/debug//implement//verify— interrogation is too late - Trivial specs (
complexity: S) — batched questions are faster - Refactors that don't change architecture
- Anything in
[autopilot]/ Cloud Routine /--bgcontext (no human to answer — use recommendations as defaults instead; log open questions in handoff)
The core directive
Interview the operator relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
For each question:
- Pose ONE question (never batch — one at a time)
- Provide YOUR recommended answer
- Give 3-4 multiple-choice alternatives
- Explain WHY you recommend the option you did, in one sentence
If a question can be answered by exploring the codebase, explore the codebase instead. Never ask the operator "what does X do" when grep can tell you in 10 seconds.
House format
Use AskUserQuestion with the header field. Format:
Q<N>: <one specific decision-forcing question>
Recommended: <option you'd pick>
Why: <one sentence reasoning — cite codebase evidence where possible>
Other options:
(a) <alt 1>
(b) <alt 2>
(c) <alt 3>Pass the recommendation as the FIRST option in the options array (with "(Recommended)" in the label).
Branch-walking discipline
Ask in dependency order. If Q2's answer depends on Q1, ask Q1 first. The mental model is a directed acyclic graph; you walk depth-first.
When you sense the operator is uncertain, ask a meta-question:
- "Should I keep grilling, or would you rather defer the rest to /clarify later?"
- "I have ~5 more questions in this branch. Continue, or stop here and let the rest emerge from prototyping?"
AUTOPILOT bailout
When running in unattended context (AUTOPILOT=1, Cloud Routine, claude --bg, claude -p):
- Do NOT call
AskUserQuestion. - For each question that would be asked, write the recommended answer to a draft, with confidence: high|tentative.
- Append the question + recommendation to
[OQ-pending-operator-review]items in the spec/initiative. - Tag the artifact with
status: draft-autopilot-needs-review(notapproved). - Surface the count of unresolved Qs in the handoff (
OVERNIGHT_REPORT.mdor stream NEXUS handoff).
Never block on a human in autopilot. Never auto-approve as if the human answered.
Closing the grill
When the design tree is exhausted (no more questions whose answers materially shape the artifact), stop. Don't ask filler questions to seem thorough.
Output a one-line confirmation:
"Grilled. Drafting <spec/plan/initiative> now."
Then proceed.
Hard rules
- One question per turn. Never batch.
- Always provide a recommendation. "What do you think?" is not grilling.
- Always provide reasoning. The operator should learn from the recommendation even when they override it.
- Cite the codebase when possible — grep is free, operator time is not.
- Don't grill beyond the depth that materially affects the artifact. Stop when stopping.
- Confidence: high for high-stakes branches, tentative for nice-to-have details. Make it explicit so the operator knows where to apply scrutiny.
Attribution
Original: mattpocock/skills — skills/productivity/grill-me/SKILL.md at commit bd04394c675ee54173a093c50eb74da01a2940fa. MIT-licensed.
House extensions (recommendation format, complexity gate, AUTOPILOT bailout, codebase-exploration substitution) are project-specific to this harness.
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
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.

