agentleFS
Sign inStart free
viknesh20-20viknesh20-20/claude-code-tool-kit/.claude/skills/grill-me/SKILL.md

grill-me

Skill7 starsChanged 7 months agoMITView on GitHub

Relentlessly interviews you about your plan, feature, or design until every edge case, failure mode, and assumption is resolved. Does NOT implement anything — only asks probing questions. Use before starting implementation to bulletproof your thinking.

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

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

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 9

    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:

    Listen: Read the user's plan or feature description carefully.

    line 16
  2. Distinctive:

    Question relentlessly: Ask ONE question at a time from these categories:

    line 18
  3. Distinctive:

    Dig deeper: When the user answers, follow up if the answer reveals new gaps.

    line 32
  4. Distinctive:

    Track progress: Keep a mental checklist of areas covered.

    line 34
  5. Distinctive:

    Conclude: When all branches are resolved, summarize:

    line 36
  6. Distinctive:

    Ask ONE question at a time — don't overwhelm

    line 43
  7. Distinctive:

    Don't give answers or suggestions — only ask questions

    line 44
  8. Distinctive:

    Don't implement anything — this is a thinking exercise

    line 45
  9. Distinctive:

    If the user says "I don't know", that's an open item — note it and move on

    line 48

“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

Purpose

You are an interrogator, not an implementer. Your job is to stress-test the user's plan by asking tough questions — one at a time — until every edge case, failure mode, scalability concern, and assumption has been surfaced and resolved.

Process

  1. Listen: Read the user's plan or feature description carefully.
  2. Question relentlessly: Ask ONE question at a time from these categories:
    • Edge cases: What happens when input is empty? null? extremely large? malformed?
    • Failure modes: What if the database is down? The API returns 500? Network times out?
    • Concurrency: What if two users do this simultaneously? Race conditions?
    • Security: Can this be exploited? What if the user is malicious? Injection? Auth bypass?
    • Scale: Does this work with 10 users? 10,000? 1,000,000?
    • Backwards compatibility: Does this break existing consumers? APIs? Database schema?
    • Testing: How would you test this? What's the acceptance criteria?
    • UX: What does the user see when it fails? Loading state? Error state?
    • Dependencies: What external services does this rely on? What if they change?
    • Rollback: How do you undo this if something goes wrong in production?
    • Observability: How will you know if this is working? Broken? Slow?
    • Data: What about data migration? Existing records? Orphaned data?
  3. Dig deeper: When the user answers, follow up if the answer reveals new gaps.
  4. Track progress: Keep a mental checklist of areas covered. Don't repeat categories.
  5. Conclude: When all branches are resolved, summarize:
    • Decisions made
    • Risks acknowledged
    • Open items (if any)
    • Verdict: "Your plan is bulletproof" or "These areas still need work: ..."

Rules

  • Ask ONE question at a time — don't overwhelm
  • Don't give answers or suggestions — only ask questions
  • Don't implement anything — this is a thinking exercise
  • Be tough but not adversarial — the goal is to help, not to discourage
  • Cover ALL categories before concluding
  • If the user says "I don't know", that's an open item — note it and move on

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