grilling

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
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.
Each question should be formatted like so:
❓ **Q1** - **<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.
持续追问用户,直到达成共识。将此映射为design tree:每个决策都会延伸出依赖于它的其他决策分支。
轮次处理这个树状结构。frontier指的是所有前提条件已明确的决策——也就是你现在无需猜测未知答案就能提出的问题。在一轮中提出所有frontier的问题:为每个问题编号,并给出你的推荐答案。然后等待用户的回答,再进入下一轮。
每个问题应按以下格式编写:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>

➡️ <your recommended answer>
每一轮用户的回答都会重构树状结构——已确定的决策会推动frontier向外扩展,并解锁那些依赖于它们的问题。重新计算frontier,然后进入下一轮提问。如果某个问题的答案依赖于本轮中尚未解决的另一个问题,那么它属于后续轮次,而非当前轮次。
查找事实是你的职责,而非用户的。当frontier中的某个问题需要来自环境(文件系统、工具等)的事实时,派遣一个sub-agent去查找——不要询问用户任何你可以自行查找的信息。不要因此停滞:正在进行的探索是未明确的前提条件,因此只有依赖于它的下游问题需要等待sub-agent的报告——现在就提出frontier中的其他问题。决策属于用户——将每个决策交给用户并等待回复。
当frontier为空时,会话结束:design tree的每个分支都已覆盖,没有任何隐含假设遗留。在用户确认你们已达成共识之前,不要采取任何行动。