agentleFS
Sign inStart free
valtterimelkkovaltterimelkko/agent-workflow-skills/skills/grill-me/SKILL.md

grill-me

Skill2 starsChanged 45 days agoMITView on GitHub

Interview the user relentlessly about a plan, project, workflow, or design until you reach shared understanding. Make sure to use this whenever the user wants to be grilled, stress-test an idea, clarify a new project, surface missing context, or think through decisions before execution.

193 other projects use a version of this, 68 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 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

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

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 6

    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:

    Ask questions one at a time.

    line 10
  2. Distinctive:

    If a question can be answered by exploring the codebase, existing docs, available memory, or context already present in the session, …

    line 12
  3. Distinctive:

    When relevant, begin by identifying what kind of project this is and what context already exists.

    line 14
  4. Distinctive:

    Do not depend on any specific file path or agent harness.

    line 19
  5. Distinctive:

    Keep the process lean. Do not turn this into a giant framework or a long lecture.

    line 28
  6. Distinctive:

    Stop when the important branches have been covered and there is a solid, practical shared understanding.

    line 30

“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

Interview me relentlessly about every important aspect of this plan until we reach a shared understanding.

Walk down each branch of the decision tree, resolving dependencies one by one. For each question, provide your recommended answer, but stay open to correction.

Ask questions one at a time.

If a question can be answered by exploring the codebase, existing docs, available memory, or context already present in the session, explore that first instead of asking me to repeat it.

When relevant, begin by identifying what kind of project this is and what context already exists. Distinguish between:

  • what is already decided
  • what is assumed but unverified
  • what is still open

Do not depend on any specific file path or agent harness. Use whatever context is available in the current environment. If important context is missing, ask me to provide it.

As the discussion progresses, periodically checkpoint the emerging understanding in a lightweight way. Keep track of:

  • key decisions made
  • important constraints
  • assumptions
  • unresolved questions
  • items that need external verification

Keep the process lean. Do not turn this into a giant framework or a long lecture. The goal is to uncover the missing context that will make downstream execution much stronger.

Stop when the important branches have been covered and there is a solid, practical shared understanding. Finish with a concise synthesis of:

  • the project or plan
  • the key decisions
  • the main open questions or risks
  • the most sensible next step

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