discuss

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Discuss

讨论

$ARGUMENTS

is what to talk about — a question, an idea, a design on the table, or a piece of the codebase. If it is empty, ask the user what they want to discuss before you start.

The run is read-only and the deliverable is prose in the chat:

git status

at the end shows the tree you started with.

$ARGUMENTS

是讨论的内容——可以是一个问题、一个想法、待定方案，或代码库中的一段代码。如果为空，请在开始前询问用户想讨论什么。

本次运行是只读的，交付物是聊天中的文字说明：最后执行

git status

，确认工作树与开始时保持一致。

Run Flow

运行流程

1. Read the domain docs

1. 阅读领域文档

Read the repo's domain documentation before you open any code —

docs/agents/domain.md

says which files those are and how to use them. The words in

CONTEXT.md

are the words your reply uses.

打开任何代码之前，先阅读仓库的领域文档——

docs/agents/domain.md

会说明需要阅读哪些文件以及如何使用它们。回复时应使用

CONTEXT.md

中的术语。

2. Do the legwork

2. 做好基础工作

Then open the code the question turns on. Glob and Grep to find it, Read each file in full, and follow it out to its callers and its tests. Go wide enough that the shape of the answer stops changing as you read.

Done when: every claim you are about to make is grounded — you can name the

file_path:line_number

it came from. What the code does not answer is named as an unknown, never filled in from memory.

然后打开问题涉及的代码。使用 Glob 和 Grep 查找代码，完整 Read 每个文件，并继续追踪到调用方及其测试。阅读范围要足够广，直到答案的轮廓不会因继续阅读而发生变化。

完成标准：你即将提出的每一项论断都必须有依据——能够指出它来自哪个

file_path:line_number

。代码无法回答的内容应明确列为未知项，绝不能凭记忆补充。

3. Reply

3. 回复

Answer what was asked, in the vocabulary of

CONTEXT.md

, and cite the

file_path:line_number

behind each claim.

Talk about the code — its shape, its trade-offs, what would have to move. When the answer wants to be code, describe the shape in prose and name the skill that would build it.

Done when: the question is answered, every unknown is named, and the tree is untouched.

使用

CONTEXT.md

中的术语回答所提出的问题，并在每项论断后标注对应的

file_path:line_number

。

围绕代码展开讨论——说明其结构、权衡取舍，以及哪些部分需要调整。如果答案需要以代码形式实现，请用文字描述实现结构，并指出负责构建该实现的 skill。

完成标准：问题已得到回答，所有未知项均已明确，且工作树未被改动。

Where it hands off

后续交接

This skill ends at the reply. When the talk settles into something else, name the skill and leave the call to the user.

Ready to build it —
```
plan-create
```
for a feature,
```
run
```
for a task
Wants their own thinking stress-tested —
```
grilling
```
The question is about a package or an external API, not this codebase —
```
research
```
A term got settled, or a decision that would be hard to undo — offer
```
domain-modeling
```
to record it in
```
CONTEXT.md
```
or as an ADR under
```
docs/adr/
```

这个 skill 在回复完成后结束。如果讨论转向其他事项，请指出相应的 skill，并将调用决定权留给用户。

准备构建——功能使用
```
plan-create
```
，任务使用
```
run
```
希望为自己的思路进行压力测试——使用
```
grilling
```
问题涉及 package 或 external API，而非当前代码库——使用
```
research
```
某个术语已经确定，或某项决策难以撤销——可建议使用
```
domain-modeling
```
，将内容记录到
```
CONTEXT.md
```
或
```
docs/adr/
```
下的 ADR 中