agentleFS
Sign inStart free
PaulRBergPaulRBerg/dot-agents/skills/grill-me/SKILL.md

grill-me

Skill6 starsChanged 6 days agoMITView on GitHub

This skill is coordination-exempt: skip the ai-coord gate for its declared work. Stress-test the plan in question rounds until every material branch is resolved and the user confirms shared understanding. User instructions take precedence over this skill. 1. Extract the current objective, constraints, assumptions, and already-made decisions. Map the design tree: each decision branches into dependent decisions. Investigate facts discoverable from the codebase, environment, or supplied evidence instead of asking the user. Put decisions to the user and wait for…

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

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

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When fact-finding benefits from delegation and subagents are available, delegate the investigation to a subagent that starts with a fresh …

    line 24
  2. Very specific:

    After each answer, acknowledge ✅ Recorded: <choice> — <consequence>.

    line 32
  3. Very specific:

    When no material open branches or required investigations remain, return ### ✅ Decision record with a decision/choice/rationale/consequence …

    line 36

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

This skill is coordination-exempt: skip the ai-coord gate for its declared work.

Stress-test the plan in question rounds until every material branch is resolved and the user confirms shared understanding. User instructions take precedence over this skill.

Workflow

  1. Extract the current objective, constraints, assumptions, and already-made decisions. Map the design tree: each decision branches into dependent decisions. Investigate facts discoverable from the codebase, environment, or supplied evidence instead of asking the user. Put decisions to the user and wait for their answers.
  2. Maintain a running decision record with: decision, chosen option, rationale, dependencies, and consequences. Update it after every answer. Reopen a recorded decision only when new evidence conflicts with it or the user corrects it.
  3. When fact-finding benefits from delegation and subagents are available, delegate the investigation to a subagent that starts with a fresh context window. Otherwise, investigate directly. Treat pending fact-finding as an unsettled prerequisite. Defer only dependent questions while asking the rest of the currently answerable questions.
  4. Work in rounds. The frontier contains every unresolved decision whose prerequisites are settled. Ask the entire frontier in each round. A question that depends on another open question belongs in a later round. Number each question as ### 🔥 Decision <N> — <topic>, then give Recommended, Why, Tradeoff, and Question. Separate question cards with a horizontal rule. Word each Question so "yes" accepts its Recommended choice. Wait for the user's answers before the next round.
  5. After each answer, acknowledge ✅ Recorded: <choice> — <consequence>. Recompute the frontier after each round. When useful, show settled and currently open counts. Never show a percentage because the decision tree can grow.
  6. Continue through scope, users, interfaces, data/state, failure modes, security, operations, migration, testing, rollout, ownership, and stopping criteria only where they are material to this design.
  7. When no material open branches or required investigations remain, return ### ✅ Decision record with a decision/choice/rationale/consequence table. Then give ### ⚠️ Risks, accepted unknowns with owner/resolution point, rejected alternatives that matter, and ### 🏁 Completion criteria. Ask the user to explicitly confirm that the report reflects shared understanding. Wait for that confirmation before acting on the plan. If the user corrects the report, reopen the affected branches and continue the interview.

Completion requires every material branch to have a recorded decision or an explicitly accepted unknown with an owner and resolution point, followed by the user's explicit confirmation of shared understanding. The final report alone does not complete the workflow. After confirmation, act only within the user's authorized scope.

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