Grill me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".From its SKILL.md
npx -y skills add muzalee/claude-atelier --skill grill-meAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 304 tokens by cl100k_base, as published. Nobody here has run it
Interview the user relentlessly about every aspect of the plan until you reach shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one at a time. For each question, propose your recommended answer and the tradeoff so they can push back — never a bare question.
Example prompts
- "Grill me on this plan before I start"
- "Stress-test my approach to the notifications feature"
- "I want you to poke holes in this design"
- "Interview me on the migration plan"
Rules
- One question at a time. No lists of questions. Wait for the answer before asking the next.
- If the codebase can answer it, read the codebase. Don't waste the user's time asking things a
grepor file read would resolve. - Always propose your recommended answer and the tradeoff. Bare questions ("how should we handle auth?") are lazy — give a starting point.
- Order matters. Resolve foundational decisions before dependent ones. Don't ask about button hover states before the page structure is decided.
- Stop when the tree is resolved. When there are no more unknowns that could change the plan meaningfully, say so and summarize the decisions. Don't manufacture questions to seem thorough.
- Capture the outcome. At the end, restate the resolved decisions as a short bulleted summary the user can paste into a brief or ticket.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.