agentleFS
walutani1walutani1/gtm-groundwork/.claude/skills/grill/SKILL.md

grill

Skill0 starsChanged 3 months agoMITView on GitHub

Stress-test any plan, decision, or idea by interviewing the user relentlessly until shared understanding - use when the user says "grill me", "stress-test this", "pull this apart", or wants a decision examined outside the PRD flow.

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-skill, root-cause 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.
  • NoaiRoxSkill

    write-skill

    Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment.

    Also in 5 projects that use this

  • Ingramradical235Skill

    root-cause

    Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.

    Also in 4 projects that use this

  • Neko-Catpital-LabsSkill

    prove-it

    Shared evidence rule for investigating, diagnosing, debugging, proving, or explaining what happened or why for any problem or situation: do not assert something is fixed, working, passing, merged, or running unless you personally observed it this turn and can show what you saw; do not assert it was caused by X until a repro and controlled isolation prove that cause.

    Also in 4 projects that use this

  • sahinSkill

    execute

    Also in 5 projects that use this

  • assisjpSkill

    file-pr

    Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.

    Also in 3 projects that use this

  • Arman-KudaibergenovSkill

    write-plan

    Этот скилл MUST быть вызван когда есть design.md и нужно разбить доработку на атомарные задачи (2-5 мин) с точными путями файлов и критериями проверки в tasks.md. SHOULD также вызывать как промежуточный шаг между brainstorm и subagent-dev. Do NOT использовать для обсуждения идеи — используй brainstorm; для выполнения задач — используй subagent-dev.

    Also in 3 projects that use this

The file

Files
SKILL.md

Grill

Interview the user relentlessly about the plan, decision, or idea at hand until you reach a shared understanding. Map it as a design tree: every decision branches into the decisions that hang off it.

Work in rounds (AskUserQuestion, max 4 questions per round, each with a recommended option). Each round, ask only the frontier: questions whose prerequisite decisions are already settled. A question that depends on another question still open this round belongs to a later round. Answers reshape the tree; recompute the frontier after every round.

Finding facts is your job, never the user's. If a question can be answered from the environment (codebase, configs, docs), look it up — dispatch a subagent if it would stall the conversation — and only the questions downstream of a running lookup wait. Decisions (tradeoffs, preferences, scope) go to the user.

Done when the frontier is empty: every branch visited, nothing left silently assumed. Summarize the resolved design in plain language and get the user's confirmation before acting on it. Write the outcome into whichever doc the grill was about (prd.md, tasks.md, or the file under discussion) so it survives the session.

This is the general-purpose version of the PRD interview (standards/prd-interview.md); use /refine-prd for full PRD work.

Adapted from Matt Pocock's "grilling" skill (MIT, github.com/mattpocock/skills).

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.