agentleFS
Sign inStart free
galandogalando/temper/skills/grill-me/SKILL.md

grill-me

Skill18 starsChanged 8 months agoMITView on GitHub

Socratic challenge mode — stress-test plans and designs with adversarial questions, one at a time

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the plan/design document.

    line 26
  2. Distinctive:

    Ask exactly one question per turn and wait for the answer.

    line 53
  3. Distinctive:

    If the answer raises new questions: Ask a follow-up (still one at a time).

    line 77
  4. Distinctive:

    After the loop ends:

    line 89
  5. Distinctive:

    After the grill session ends, the user returns to the original stage gate (Plan or Design).

    line 109

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grill Me

Interview the user relentlessly about a plan or design until reaching shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.

Credit: adapted from Matt's Grill Me skill (AI Hero), with thanks.

This is NOT the walkthrough. The walkthrough explains the plan. Grill Me challenges it.

PropertyWalkthroughGrill Me
PurposeExplain the plan to the userChallenge the plan's assumptions
DirectionTemper → User (teaching)Temper ↔ User (adversarial)
Questions"Does this make sense?""What happens if X fails?"
OutcomeUser understands planUser discovers weaknesses
ModeSequential section presentationOne hard question at a time

Algorithm

1. Extract Claims

Read the plan/design document. Extract:

  • Claims — explicit assertions ("This handles all error cases", "This is backward-compatible")
  • Assumptions — unstated beliefs ("Users will have X", "External service is fast")
  • Dependencies — things that must be true for the plan to work
  • Decisions — architectural choices made (and alternatives rejected)
  • Gaps — things not mentioned that should be

2. Generate Challenge Questions

For each extracted item, generate challenge questions targeting:

TargetQuestion Pattern
Unstated assumptions"What happens if {assumption} is false?"
Missing error paths"What does {component} do when {dependency} fails?"
Alternatives not considered"Why {this approach} instead of {alternative}?"
Scalability limits"What happens at 10x/100x current {metric}?"
Dependency risks"If {dependency} changes/breaks, what's the impact?"
Edge cases"What about {edge case}?"
Hidden complexity"What's the hardest part of implementing {this}?"
Success criteria gaps"How would you verify {claim} actually works?"
Cross-cutting concerns"How does this interact with {existing system}?"
Rollback"If this fails in production, how do you roll back?"

3. Present One Question at a Time

Ask exactly one question per turn and wait for the answer; a batch of questions lets the user answer the easy ones and skip the hard one.

AskUserQuestion:
  question: "{challenge question}"
  options:
    - label: "Answer"
      description: "Provide your answer or reasoning."
    - label: "Update plan"
      description: "I want to revise the plan based on this question."
    - label: "Skip"
      description: "Skip this question, move to next."
    - label: "Done grilling"
      description: "End the session and return to the gate."
  multiSelect: false

4. Analyze Response

After each answer:

  1. If the answer reveals a weakness: Note it as a finding. Offer to update the plan.
  2. If the answer is solid: Acknowledge it, move to next question.
  3. If the answer raises new questions: Ask a follow-up (still one at a time).
  4. If the user chooses "Update plan": Apply the change to the plan/design file, then continue grilling.

5. Loop Until Done

Continue until:

  • User types "Done grilling" or selects "Done grilling" option
  • Maximum 10 questions reached
  • 3 consecutive answers that reveal no weaknesses (the plan is solid)

6. Summary

After the loop ends:

GRILL ME — Summary
  Questions asked: {N}
  Weaknesses found: {N}
  Plan updates made: {N}

  Weaknesses:
    1. {description} — {how it was addressed}
    2. {description} — {still open}

  Plan updated: Yes/No
  Returning to {stage} gate...

Integration with Temper

This skill is invoked from the Plan and Design stage gates in the /temper unified command. When the user selects "Grill Me" at a gate, the orchestrator invokes this skill with the current plan.md or design.md as input.

After the grill session ends, the user returns to the original stage gate (Plan or Design). If the plan was updated during grilling, the gate shows the updated summary.

Download now (ZIP)

  • Other versions193 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 68

    1. langfuse/langfuse★ 37k20% same
    2. humanlayer/humanlayer★ 13k15% same
    3. openstatusHQ/openstatus★ 9.2k21% same
    4. webiny/webiny-js★ 8.1k21% same
    5. sanity-io/sanity★ 6.4k21% same
    6. camunda/camunda★ 4.3k21% same
    7. event-catalog/eventcatalog★ 3k21% same
    8. Akylas/OSS-DocumentScanner★ 2.6k21% same
    9. openstatusHQ/data-table-filters★ 2.3k21% same
    10. owid/owid-grapher★ 1.6k21% same

    58 more not listed

    Wrote their own version · 125

    1. mattpocock/skills★ 309ksame name
    2. QuivrHQ/quivr★ 40ksame name
    3. nrwl/nx★ 29ksame name
    4. windmill-labs/windmill★ 18ksame name
    5. GreyDGL/PentestGPT★ 16ksame name
    6. jaredpalmer/kev★ 9.8ksame name
    7. ArcReel/ArcReel★ 6ksame name
    8. vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
    9. pollinations/pollinations★ 5.3ksame name
    10. withcoral/coral★ 4.9ksame name

    115 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.
    • julianoczkowskiSkill

      brief-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

    • FabienDehopreSkill

      decision-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

    • LesaniSkill

      writing-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 62 projects that use this

    • simo97Skill

      migrate-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 68 projects that use this

    • simo97Skill

      request-refactor-plan

      Use this skill when user wants to create a refactor plan.

      Also in 43 projects that use this

    • LesaniSkill

      writing-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 61 projects that use this

    • +2 more from simo97
  • In this repository5 other files it gives its agents.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free