Before invoking it, ask the question above. If there's tacit knowledge to extract, two triggers start the interview; if not, grill-me just gets in the way.
Trail map
Detailed content
🎯 Putting grill-me into practice
The most practical path: ready-to-paste prompts, the real pain of answering, and the grill-me + skill-creator loop that helps the skill mature.
Two triggers: the slash command (/grill-me) or just ask in natural language ("grill me about X"). The skill’s description takes care of the rest.
You don’t even need to remember the command name — just describe what you want grilled.
Two triggers · natural-language phrase · slash command.
Use grill-me to map a process, a funnel, or how you package content — things that only live in your head.
It’s the most valuable use case: it becomes documentation and skills for your business.
Process · funnel · business map.
Answering question after question is exhausting—sometimes it gets irritating when so much detail is requested. But that's exactly where the value lies (95% vs. 80% success).
Knowing that discomfort is expected helps you avoid ending the session too soon.
Discomfort = signal · persist · the pain is the gold.
When someone else has the answer (the stakeholder/operator who runs that process), it becomes a flag with an owner; you find the information and come back to update it.
Not knowing doesn’t stall the session—it becomes a clear next step.
Flag → owner · follow up later · update the doc.
When you discover something new (e.g., a breakthrough in how to package it), return to the SAME brainstorm: "grill me again; here’s what changed" — and update everything.
The brainstorm is a living document, not a dead record.
Living doc · re-enter · update.
The raw capture ALWAYS stays in brainstorms/; when it becomes a polished deliverable (plan, map, spec), that artifact moves to the folder projects/ relevant.
Separating raw from polished keeps the history intact and the deliverable clean.
brainstorms = raw · projects = polished · separation.
The output from grill-me feeds into creating/refining skills (skill-creator): you grill, extract the nuance, and the skill goes from ~70% to ~95% in fewer iterations.
It’s the mechanism that turns extraction into real quality gains.
Loop · skill-creator · 70% → 95%.
Don’t respond in batches and skip the checkpoint; don’t ask what you can explore; don’t stop early thinking “that’s enough”; don’t leave a flag without an owner.
Knowing common mistakes protects the quality of the brainstorm.
No batching · don't skip checkpoints · don't stop early.