agentleFS
jcurbelojcurbelo/agent-seed/.claude/skills/grill-me/SKILL.md

grill-me

Skill8 starsChanged 8 months agoMITView on GitHub

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, says "grill me", or before any multi-step task where the path is ambiguous.

193 other projects use a version of this, 69 of them edited.

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 74 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 78 projects that use this

  • simo97Skill

    request-refactor-plan

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

    Also in 45 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 73 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 64 projects that use this

  • +1 more from simo97
  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask one question at a time: Wait for the user's answer before continuing.

    line 11
  2. Distinctive:

    Before a multi-file refactor — confirm the shape and the seam before coding

    line 18
  3. Distinctive:

    Before drafting any external message (email, PR description, RFC) where alignment matters

    line 19
  4. Very specific:

    Before invoking a heavyweight skill (/handoff, /eod) so the output captures the right decisions

    line 20
  5. Distinctive:

    When the user says "I want to do X" and the path has more than one reasonable approach

    line 21
  6. Distinctive:

    After grilling concludes, write a brief recap so the decisions don't evaporate:

    line 25

“Common” is measured: kept by at least 6 in 10 of the 179 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 - Relentless Plan Interview

Interview the user relentlessly about every aspect of this plan until you reach shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Rules

  • Ask one question at a time. Wait for the user's answer before continuing.
  • If a question can be answered by exploring (reading a file, an issue, a PR, prior context), explore instead of asking.
  • Always provide a recommended answer with each question so the user can confirm or redirect quickly.
  • Stop when the design tree is resolved, not when the user gets tired. If a branch is still ambiguous, say so and recommend deferring.

When this is most useful

  • Before a multi-file refactor — confirm the shape and the seam before coding
  • Before drafting any external message (email, PR description, RFC) where alignment matters
  • Before invoking a heavyweight skill (/handoff, /eod) so the output captures the right decisions
  • When the user says "I want to do X" and the path has more than one reasonable approach

Output

After grilling concludes, write a brief recap so the decisions don't evaporate:

## Decisions

1. <decision> — <rationale>
2. ...

## Open questions

- <anything still unresolved>

## Next step

<Concrete action — typically the actual work, or invoking another skill.>

Adapted from mattpocock/skills/productivity/grill-me. See memory/external-skill-sources.md.

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.