Back to Details

grill-with-docs

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Grill With Docs

用文档质询方案

Load 
/intent-modeling
if it isn't already loaded.
Interview the author relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one.
Keep each turn to the next unresolved branch or a small cluster of related questions the author can answer in one reply, then wait. Provide your recommended answer for each question.
如果
/intent-modeling
尚未加载，请加载它。
针对方案的各个方面对作者进行全面质询，直到达成共识。梳理决策树的每个分支，逐一解决决策之间的依赖关系。
每次仅推进到下一个未解决的分支，或提出一组作者可一次性回答的相关小问题，然后等待回复。为每个问题提供你的建议答案。

Starting the Session

启动质询会话

Read the plan or proposed direction the author provides. Identify:
  • Decision branches — choices that gate other choices
  • Dependency order — which decisions must resolve first
  • Terms needing precision — vague, overloaded, or undefined vocabulary
  • Assumptions — things treated as given that may not be
Start with the highest-leverage unresolved dependency — the earliest branch point that unblocks the most downstream decisions.
阅读作者提供的方案或拟议方向，明确以下内容：
  • 决策分支 —— 会影响其他选择的关键决策点
  • 依赖顺序 —— 哪些决策必须优先解决
  • 需明确的术语 —— 模糊、多义或未定义的词汇
  • 假设前提 —— 被视为既定事实但可能不成立的内容
从影响最大的未解决依赖项开始——即能解锁最多下游决策的最早分支点。

Challenging Terminology

术语质疑

Check every significant term against the project's existing vocabulary where it exists:
  1. Vocabulary pages in the kb — 
    kb/vocab.md
    for project-wide terms, 
    kb/<domain>/vocab.md
    for domain-specific ones.
  2. Project conventions in 
    CLAUDE.md
    — established names and labels.
  3. Active work notes in 
    work/
    — terms already defined for the current effort.
  4. Prior decisions — terms established by earlier choices.
When the author's language conflicts with documented terms, call it out immediately. Name the conflict: "You said X, but the kb defines Y for this concept — which should we use?"
Sharpen vague or overloaded terms into canonical terms. Use concrete scenarios and edge cases to force precise boundaries — "Does 'sync' here mean the timeline beat, the character's realization, or something new?" See 
/shared-dao
for the vocabulary discipline.
对照项目现有词汇表检查每个重要术语：
  1. 知识库中的词汇页面——项目通用术语见
    kb/vocab.md
    ，领域特定术语见
    kb/<domain>/vocab.md
    。
  2. CLAUDE.md
    中的项目约定——已确立的命名和标签规则。
  3. work/
    中的活跃工作笔记——当前工作中已定义的术语。
  4. 过往决策——早期选择中确立的术语。
当作者使用的语言与已记录的术语冲突时，立即指出。明确冲突点：“你提到了X，但知识库中对该概念的定义是Y——我们应该使用哪一个？”
将模糊或多义的术语提炼为标准术语。通过具体场景和边缘案例来明确术语边界——比如：“这里的'sync'是指时间节点、角色的认知转变，还是新的概念？”参考
/shared-dao
中的词汇规范。

Gathering Evidence

收集证据

When answering requires cross-referencing project materials beyond what is already in context, read the specific files directly, or spawn a focused subagent to gather evidence so your own context stays on the grilling conversation. Scope each lookup to one question and target specific files or directories — chapters, kb entries, outlines, prior decisions.
Frame the lookup as an evidence-seeking question with file/path targets. Act on findings to sharpen your next question or to challenge the author's assumptions with evidence.
当回答需要交叉引用当前上下文之外的项目资料时，直接读取特定文件，或生成一个专注的subagent来收集证据，以便你能聚焦于质询对话。每次查询仅针对一个问题，并指定具体文件或目录——如章节、知识库条目、大纲、过往决策记录。
将查询表述为带有文件/路径目标的证据收集问题。根据发现的内容优化下一个问题，或用证据质疑作者的假设。

Updating Documentation

更新文档

Update artifacts inline as decisions crystallize. Reasoning flattens the longer you wait — capture it in the moment.
随着决策逐渐明确，即时更新相关文档。推理过程搁置越久越容易模糊——要及时记录。

Active work notes

活跃工作笔记

Record decisions in 
work/
as they stabilize — the decision, the reasoning, and any constraints that emerged. Keep open questions visible.
当决策趋于稳定时，在
work/
中记录决策内容、推理过程以及出现的任何约束条件。保留未解决的问题以便追踪。

KB vocabulary

知识库词汇

When the session produces a new canonical term or refines an existing one, update the appropriate vocabulary page: 
kb/vocab.md
for cross-cutting terms, 
kb/<domain>/vocab.md
for domain-specific ones. Follow 
/kb-management
for page structure.
当会话产生新的标准术语或优化现有术语时，更新相应的词汇页面：跨领域术语更新
kb/vocab.md
，领域特定术语更新
kb/<domain>/vocab.md
。遵循
/kb-management
中的页面结构规范。

Durable decisions

长效决策记录

Create durable decision records sparingly — only when the choice is hard to reverse, surprising without context, and involves a real tradeoff. Record it in the relevant kb page. Keep provisional decisions in 
work/
until they prove durable.
仅在以下情况下创建长效决策记录：选择难以逆转、脱离上下文会令人困惑，且涉及实际权衡。将其记录在相关的知识库页面中。临时决策先记录在
work/
中，直到被确认为长效决策。

Session Rhythm

会话节奏

Each cycle through a decision branch:
  1. State the branch and why it matters now (dependency context).
  2. Ask focused questions with your recommended answer for each.
  3. Wait for the author's response.
  4. If the answer raises a sub-question, drill into it before moving on.
  5. If the answer can be verified against project materials, check the relevant files and use what you find to confirm or challenge.
  6. When the branch resolves, update the relevant documentation surface immediately.
  7. Advance to the next branch.
The session ends when all branches of the decision tree are resolved and the documentation reflects the shared understanding.
每个决策分支的处理周期：
  1. 说明当前分支及其重要性（依赖关系背景）。
  2. 提出聚焦的问题，并为每个问题提供建议答案。
  3. 等待作者回复。
  4. 如果回复引出子问题，先深入探讨该子问题再推进。
  5. 如果回复可通过项目资料验证，检查相关文件并根据发现确认或质疑。
  6. 分支问题解决后，立即更新相关文档。
  7. 推进到下一个分支。
当决策树的所有分支都已解决，且文档反映出共识时，会话结束。