agentleFS
nagi-studionagi-studio/skills/skills/pondering/grill/SKILL.md

grill

Skill470 starsChanged 14 days agoMITView on GitHub

分轮追问用户的计划、决定或想法,直到重要未知暴露出来,再动手执行。适用于任何领域,不限于写代码。当用户想理清思路、给想法做压力测试,或者说出这些话时使用:拷打我、追问我、帮我想清楚、帮我理一理、挑挑毛病、有什么没想到的、grill me、stress-test this、poke holes in this、interview me。

87 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 9 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

  • 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

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

The file

Files
SKILL.md

先问拷打强度,以及要不要留决策记录(decision log)。用户已说明的不再问。

  1. 浅问:只补最关键的缺口
  2. 常规:把明显没想清楚的地方问明白
  3. 细问:检查目标、约束、取舍和默认假设
  4. 深挖:主动寻找风险、遗漏和边界情况
  5. 拷打:严格挑战前提,直到重要未知基本暴露

用户可以随时调整强度。

要留记录时,每定一条就追加「结论 + 理由」,另列待定问题。能写文件就新建 docs/decisions-<英文主题>.md;不能就每隔几轮贴出完整版供复制。

分轮进行。每轮询问当前已经具备前提的问题,可以是一条,也可以是多条。依赖尚未确定答案的问题,留到下一轮。

优先追问会明显影响后续方案的内容:

  • 真正想解决什么问题
  • 哪些事情已经确定
  • 哪些事情还没有决定
  • 哪些前提只是用户默认成立
  • 有没有用户尚未意识到的重要问题
  • 哪些取舍会改变后续方向

能自己查清楚的事实不要交给用户;涉及用户的目标、偏好、成本和取舍时,再让用户决定。必要时提供选项和建议,但不要替用户决定。

每个问题使用:

❓ Q1|问题标题
问题内容。需要时给出选项。
➡️ 建议:简短给出你的推荐和理由。

同一轮有多个问题时继续 Q2、Q3。问题保持具体、容易回答。不要一次堆出大量低价值问题。

强度决定追问深度,不只是问题数量:

  • 浅问只处理会卡住下一步的问题。
  • 常规补齐明显缺口。
  • 细问开始检查隐含假设和重要取舍。
  • 深挖主动寻找边界情况、风险和遗漏。
  • 拷打会挑战模糊回答、未经验证的前提和互相冲突的要求。

不要为了「拷打」而无限追问。当剩余未知已经不足以明显改变下一步时停止。

最后简短总结:

  • 已确定
  • 暂未确定
  • 下一步

等待用户确认后再开始重要执行。

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.