agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/frontier-ghcp-ttt-rvas/sessions/session-m3-05-agent-skills/lab/solution/grill-me/SKILL.md

grill-me

Skill3 starsChanged 2 months agoMITView on GitHub

Interview the user about a plan, idea, or design before any code is written. Use when the user says "grill me", "interview me", "stress-test this plan", or shares a rough idea and wants it pressure-tested. Do not use for questions that have a factual answer.

193 other projects use a version of this.

Adopted by

Most recently taken up by

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

  • 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 66 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

  • 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 71 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 65 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • +2 more from simo97

The file

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 177 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 any file the user points to.

    line 12
  2. Distinctive:

    Ask one question at a time.

    line 13
  3. Distinctive:

    Follow the answer. If it opens a new gap, go there before moving on.

    line 15
  4. Distinctive:

    Stop when you could hand the plan to a colleague and they would not need to ask you anything.

    line 21
  5. Distinctive:

    Ask the user to correct the summary before you finish.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 177 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 until the plan is clear enough to build. Don't write code or a plan until the interview is done.

How to interview

  1. Read any file the user points to. Never ask what the file already answers.
  2. Ask one question at a time. Wait for the answer.
  3. For each question, give your recommended answer so the user can reply "yes" or correct you.
  4. Follow the answer. If it opens a new gap, go there before moving on.
  5. Cover these areas, skipping what's already settled: goal and audience, scope and non-goals, owner, data and inputs, failure cases, how to tell it worked.
  6. Push back once on vague answers ("soon", "everyone", "somehow"). Ask for a concrete example.

When to stop

Stop when you could hand the plan to a colleague and they would not need to ask you anything. Then write a summary with:

  • Decisions made, one line each
  • Open questions that remain, with an owner if known
  • Next step

Ask the user to correct the summary before you finish.

Download now (ZIP)

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