通过逐轮提问深入检验计划或想法，为问题附上建议答案，整理决策之间的依赖关系，确认模糊前提和待定事项，在行动前建立共同理解。
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
grilling 通过提问深入探讨计划、决策或想法，确认模糊的前提和尚未决定的事项。它将一项决策引出后续决策的分支关系整理为“设计树”，把前提已经确定的问题集中提出。每个问题都附有建议答案，并根据用户的回答重新组织下一轮问题。
适合在执行前检查计划的薄弱之处，或进一步明确想法的细节。面对某项判断依赖另一项判断的复杂讨论，也能在不假定未获回答的情况下继续推进。可以从环境中查明的事实由智能体调查，需要作出选择的事项则交给用户回答。
这是需要等待用户回答、逐步推进的交互式技能。事实核查流程包含使用子智能体。即使所有决策都已确认，也要等用户确认双方已达成共同理解后，才会开始执行。
本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。
AI 仅根据 SKILL.md 的内容，从 4 个方面进行了评估。星标数和热度不计入评估。
总分按每项 A=25 分、B=15 分、C=5 分相加。 由 AI（OpenAI Codex）于 2026年10月19日 评估。仅供参考，安装前请同时查看原文。
安装前可以查看交给 AI 代理的指令内容。
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>
Word each question so "yes" accepts 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.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
中文简介正在准备中。当前显示英语简介。
在单次会话中协调承担不同任务的子智能体，推进长期目标。后台工作与用户对话同时进行，并改进共享规范、工作环境和后续任务所需的信息访问条件。
将进行中的对话整理为交接摘要，移除敏感信息，明确后续重点、参考资料和建议技能，再启动新的后台智能体，从当前工作目录继续处理任务。
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
中文简介正在准备中。当前显示英语简介。
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
中文简介正在准备中。当前显示英语简介。
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
中文简介正在准备中。当前显示英语简介。