agentleFS
devcxldevcxl/mattpocock-skills-zh/skills/productivity/grilling/SKILL.md

grilling

Skill522 starsChanged 37 days agoMITView on GitHub

对用户的计划、决策或想法进行层层盘问。当用户想要压力测试自己的思考,或使用任何 'grill' 触发短语时使用。

193 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev and 4 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

  • 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

  • +3 more from The-Vibe-Company

The file

Files
SKILL.md

持续盘问用户,直到你们达成共识。将讨论映射为一棵设计树(design tree):每个决策都会分支出一系列依赖它的子决策。

以**轮次(rounds)**推进这棵树。**前沿(frontier)**是所有前提已确定的决策:即你现在可以问的问题,无需猜测尚未听到的答案。每一轮问完整个前沿:为每个问题编号,并给出你的推荐答案。然后等待用户的回答,再进行下一轮。

每个问题格式如下:

❓ **Q1** - **<问题标题>**:<问题正文,可以是多段,包括多个选项>

➡️ <你的推荐答案>

---

❓ **Q2** - **<问题标题>**:<问题正文,可以是多段,包括多个选项>

➡️ <你的推荐答案>

每个问题的措辞都应确保回答“是”就代表接受你的推荐答案。

每一轮用户的回答都会重塑这棵树:已确定的决策把前沿向外推,解锁依赖它们的问题。重新计算前沿,进入下一轮。某个问题的答案依赖本轮中另一个仍未回答的问题时,它属于更晚的轮次,而不是本轮。

寻找事实是你的工作,永远不是用户的。当前沿问题需要来自环境的事实(文件系统、工具等)时,派一个使用全新上下文窗口的子代理去查;不要问用户任何你自己能查到的东西。不要阻塞等待:正在进行的探查是一个未解决的前提,只有它下游的问题需要等子代理回报;现在就把前沿其余部分问完。决策是用户的:把每个决策摆给他们,然后等待。

当前沿为空时,会话结束:设计树的每条分支都已遍历,没有任何东西被默默假设。在用户确认你们达成共识之前,不要付诸行动。

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.