grilling
就一份计划、决定或想法不留情面地盘问用户。当用户想对自己的思路做压力测试,或使用了任何带 'grill' 的触发词时使用。
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 363
- Forks
- 33
01 前言 Front Matter
- name
- grilling
- description
- 就一份计划、决定或想法不留情面地盘问用户。当用户想对自己的思路做压力测试,或使用了任何带 'grill' 的触发词时使用。
03 SKILL.md 正文
不停地问用户,直到你们达成共识。把这件事画成一棵设计树:每一个决定都会分叉出挂在它之下的决定。
按轮次推进这棵树。所谓前沿,是指那些前置条件都已经定下来、你_现在_就能提问的决定——问这些问题时,不必去猜你还没听到的答案。一轮里把整个前沿问完:给每个问题编号,并给出你推荐的答案。然后等用户回答,再开始下一轮。
一轮的格式如下:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
把每个问题都写成这样:用户回答「是」,就等于接受你推荐的答案。
用户每一轮的回答都会重塑这棵树:已经定下来的决定把前沿向外推,并解开那些依赖它们的问题。重新计算前沿,问出下一轮。如果某个问题的答案取决于本轮里另一个还没定下来的问题,那它属于_更晚_的某一轮,而不是这一轮。
找_事实_是你的活,永远不是用户的活。当前沿上的某个问题需要来自环境(文件系统、工具等)的事实时,派一个子代理,让它在全新上下文窗口里去找;凡是自己能查到的,都不要问用户。不要因为这件事卡住:一个正在跑的探查就是一项还没定下来的前置条件,所以只有它下游的那些问题才需要等子代理回报;前沿上其余的问题现在就问。_决定_是用户的:把每一个都摆到用户面前,然后等。
当前沿清空时,这次会话就结束了:设计树的每个分支都走过了,没有任何东西被默默地当成前提。在用户确认你们已经达成共识之前,不要照着它动手。
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).