烧烤
- 作者仓库星标 0
- 作者更新于 2026年8月24日 14:19
- 作者仓库 skills
- 领域
- 效率工具
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @mattpocock · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
Format a round like so:
```
❓ **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>
```
Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one.
Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The _decisions_ are the user's: put each to them and wait.
The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.
章节与文件索引
按说明文件中的顺序排列。
文件/命令 -> 原文未列出明确文件或命令
内容校验值 -> 8f146d9f1c7e
当前原文的自动摘译,尚未人工审校。
轮流对树进行作业。前沿是先决条件已经解决的每一个决定:你现在可以提出的问题,而不必猜测你还没有听到的答案。一轮询问整个前沿:对每个问题进行编号并给出建议的答案。然后等待用户的回答后再进行下一轮。
像这样格式化一个回合:
用户的每一轮答案都会重塑树的形状:既定的决策将边界向外推,并解锁依赖于它们的问题。重新计算边界并询问下一轮。如果一个问题的答案取决于本轮中仍悬而未决的另一个问题,则该问题属于_稍后_一轮,而不是本轮。
查找_事实_是您的工作,而不是用户的工作。当前沿问题需要来自环境(文件系统、工具等)的事实时,调度一个子代理来查找它;不要向用户询问任何您可以自行查找的内容。不要阻止它:正在运行的探索是一个未解决的先决条件,因此只有其下游的问题等待子代理报告;现在就去问问边境的其他人吧。 _决定_是用户的:将每个决定交给他们并等待。
当边界为空时,会议就完成了:访问了设计树的每个分支,没有留下任何默默假设的东西。在用户确认你们已达成共识之前,不要采取行动。