grill-me
Skill0 starsChanged 6 months agoMITView on GitHub
Interview the user relentlessly about a plan or design until reaching shared understanding. Use when asked to 'grill me', 'interview me', 'ask me questions about this', or before writing a PRD to flesh out vague ideas.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
If running interactively (human present), output "Read Grill Me skill." to acknowledge.
- Distinctive: line 15
Ask the questions one at a time, waiting for feedback before continuing.
- Distinctive: line 17
If a question can be answered by exploring the codebase, explore the codebase instead.
- Distinctive: line 22
When the user uses vague or overloaded terms, propose a precise canonical term.
- Distinctive: line 25
When domain relationships or flows are being discussed, stress-test them with specific scenarios.
- Distinctive: line 28
When the user states how something works, check whether the code agrees.
- Distinctive: line 33
After reaching shared understanding, offer the user three paths:
- Very specific: line 41
If context fills up during the interview, follow the standard handoff protocol (@~/dotfiles/instructions/handoff.instructions.md) — persist …
“Common” is measured: kept by at least 6 in 10 of the 178 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
If running interactively (human present), output "Read Grill Me skill." to acknowledge. If running with --dangerously-skip-permissions (AFK/unattended), skip acknowledgement and proceed directly.
Pipeline position: /grill-me → /write-a-prd → /architect → /prd-to-issues → /do-work → shft
<what-to-do>
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.Ask the questions one at a time, waiting for feedback before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
</what-to-do>
<interviewing-discipline>
### Sharpen fuzzy language
When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."Discuss concrete scenarios
When domain relationships or flows are being discussed, stress-test them with specific scenarios. Invent edge cases that force the user to be precise about boundaries and behaviour.
Cross-reference with code
When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"
</interviewing-discipline>
Handoff
After reaching shared understanding, offer the user three paths:
- /write-a-prd — capture decisions as a formal PRD
- /prd-to-issues — break directly into GitHub issues
- /do-work — start implementing immediately
Let the user choose.
If context fills up during the interview, follow the standard handoff protocol (@~/dotfiles/instructions/handoff.instructions.md) — persist decisions made so far to working/ and provide the pickup command.
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 77
- langfuse/langfuse★ 37k63% same
- humanlayer/humanlayer★ 13k65% same
- openstatusHQ/openstatus★ 9.2k63% same
- webiny/webiny-js★ 8k66% same
- sanity-io/sanity★ 6.4k63% same
- camunda/camunda★ 4.3k63% same
- event-catalog/eventcatalog★ 2.9k66% same
- Akylas/OSS-DocumentScanner★ 2.6k66% same
- openstatusHQ/data-table-filters★ 2.3k63% same
- owid/owid-grapher★ 1.6k57% same
67 more not listed
Wrote their own version · 116
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- nrwl/nx★ 29ksame name
- windmill-labs/windmill★ 18ksame name
- GreyDGL/PentestGPT★ 16ksame name
- jaredpalmer/kev★ 9.3ksame name
- ArcReel/ArcReel★ 6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- pollinations/pollinations★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
106 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.
Used alongsideProjects with it also use brief-to-tasks, decision-mapping 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
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 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 59 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 63 projects that use this
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 40 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 58 projects that use this
- +2 more from simo97
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-assetsSkill
- agent-navigabilitySkill
- agent-session-frictionSkill
- agent-testabilitySkill
- architectSkill
- atomic-commitsSkill
- cavemanSkill
- codebase-auditSkill
- code-reviewSkill
- compliance-auditSkill
- data-object-conventionsSkill
- documentSkill
- do-workSkill
- error-auditSkill
- exploreSkill
- frontend-component-styleSkill
- grill-with-docsSkill
- halbert-copy-editorSkill
- improve-architectureSkill
- logging-auditSkill
- mobile-devSkill
- npm-security-auditSkill
- performance-auditSkill
- plan-archiveSkill
- prd-to-issuesSkill
- press1-checkSkill
- pr-preflightSkill
- repo-hygieneSkill
- researchSkill
- review-pr-copilotSkill
- sanity-best-practicesSkill
- session-closeSkill
- sketch-the-solutionSkill
- skill-scaffolderSkill
- stress-testSkill
- systematic-debuggingSkill
- tddSkill
- visual-feedbackSkill
- write-a-prdSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

