agentleFS
Sign inStart free
jjillijjilli/fable-flow/skills/grilling/SKILL.md

grilling

Skill2 starsChanged 4 months agoMITView on GitHub

Relentless, one-question-at-a-time interview that stress-tests a plan or design before any code is written. Invoke ONLY when the user explicitly asks for it — they say "grill me", "grill the plan", "grilling", or otherwise ask to be grilled / to pressure-test the design. Do NOT auto-invoke it for ordinary planning or clarification; the default new-project brainstorm (card-based multiple-choice questions) is a separate, lighter thing. This is the opt-in deep interrogation.

194 other projects use a version of this, 36 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev 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.
  • The-Vibe-CompanySkill

    capture-learning-tools

    Turn technical conversations, bugs, CI failures, review comments,

    Also in 5 projects that use this

  • The-Vibe-CompanySkill

    design-frontend-dev

    Clean Impeccable frontend design skill. Use when the user wants to

    Also in 5 projects that use this

  • RoentekSkill

    loop-me

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

    Also in 58 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

  • 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

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 136 projects that use this

  • +3 more from The-Vibe-Company

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 68 edited versions we read keep these.

  • 3

    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 the questions one at a time, waiting for feedback on each before continuing.

    line 20
  2. Distinctive:

    If a *fact* can be found by exploring the codebase, look it up rather than asking — spend the user's attention only on decisions.

    line 23
  3. Distinctive:

    Do not enact the plan until the user confirms you have reached a shared understanding.

    line 27

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

Grilling

Invoke this only when the user explicitly asks to be grilled (or to grill the plan/design). It is intentionally heavier than normal clarification — a relentless interview, not a few questions. If the user hasn't asked for it, don't start it.

When they have:

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

Ask the questions one at a time, waiting for feedback on each before continuing. Asking multiple questions at once is bewildering.

If a fact can be found by exploring the codebase, look it up rather than asking — spend the user's attention only on decisions. The decisions are theirs: put each one to them and wait for the answer.

Do not enact the plan until the user confirms you have reached a shared understanding.

In this pipeline, grilling sits before /fable-flow:plan — it hardens the task and its design decisions so the architect plans against a settled intent rather than guesses. Once grilling ends in a shared understanding, feed the resolved decisions into the task (.fable-flow/task.md) and proceed to planning.

Adapted from Matt Pocock's grilling skill — https://github.com/mattpocock/skills/blob/main/skills/productivity/grilling/SKILL.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.

Check your setup, free