brainstorm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

brainstorm

头脑风暴

Turn an existing roadmap item's intent (and any gathered research) into concrete design decisions, through open back-and-forth with the operator, written incrementally into the item's

## Design

section.

Judgment task — describe and decide; do not script it, do not write code, do not break work into tasks (that is

plan

, deferred).

将现有路线图项的意图（以及所有已收集的研究资料）通过与操作者的开放式双向讨论，转化为具体的设计决策，并逐步写入该项的

## Design

部分。

这是判断类任务——描述并决策；不要编写脚本、不要写代码、不要将工作拆分为任务（那是

plan

的职责，后续再处理）。

When to use

使用场景

Operator runs
```
/jackin-dev:brainstorm <slug>
```
to design an open roadmap item.

操作者运行
```
/jackin-dev:brainstorm <slug>
```
来设计一个开放的路线图项。

When NOT to use

禁用场景

Creating the item →
```
/jackin-dev:propose
```
.
Large external/codebase investigation →
```
/jackin-dev:research
```
.
Implementing →
```
/goal Implement <slug>.md
```
.

创建项 →
```
/jackin-dev:propose
```
。
大型外部/代码库调研 →
```
/jackin-dev:research
```
。
实现阶段 →
```
/goal Implement <slug>.md
```
。

Arguments

参数

```
--research
```
— run
```
/jackin-dev:research
```
first if the item looks thin.
```
--resume
```
— continue from the current
```
## Design
```
state.

```
--research
```
— 如果项内容不够完善，先运行
```
/jackin-dev:research
```
。
```
--resume
```
— 从当前
```
## Design
```
部分的状态继续。

Process

流程

Load context. Read
```
docs/content/docs/reference/roadmap/<slug>.mdx
```
— Problem, Why It Matters, Design-so-far, Related Files — plus any research already linked.
Discuss freeform. Open back-and-forth: surface alternatives, trade-offs, open questions. Pull in jackin' design principles and the relevant rule files (
```
ENGINEERING.md
```
,
```
HOST_AND_CONTAINER.md
```
, TUI/docs rules) as constraints. Prefer one question at a time; check in as each part settles.
Write incrementally. As each point settles, append or update the matching part of
```
## Design
```
in the
```
.mdx
```
— the decision plus a one-line why.
```
--resume
```
picks up from there.
Hit an unknown? Gather quickly (Explore/grep, or
```
deep-research
```
). Large investigation → spin a separate
```
/jackin-dev:research
```
dossier and link it from
```
## Design
```
. Then resume deciding.
Converge. When
```
## Design
```
covers the approach end to end, summarize and point at the implementation step (
```
/goal Implement <slug>.md
```
).
Commit + push.
```
docs:
```
per settled chunk (push after every commit).

加载上下文。 读取
```
docs/content/docs/reference/roadmap/<slug>.mdx
```
文件——包括Problem、Why It Matters、Design-so-far、Related Files部分——以及所有已关联的研究资料。
自由讨论。 开放式双向交流：提出替代方案、权衡利弊、明确待解决问题。将jackin'设计原则和相关规则文件（
```
ENGINEERING.md
```
、
```
HOST_AND_CONTAINER.md
```
、TUI/docs规则）作为约束条件。建议一次只讨论一个问题；每部分达成共识后进行确认。
逐步撰写。 每达成一个共识点，就在
```
.mdx
```
文件的
```
## Design
```
部分追加或更新对应内容——包括决策内容以及一行简短的原因说明。
```
--resume
```
参数将从此状态继续。
遇到未知问题？ 快速收集信息（使用Explore/grep，或
```
deep-research
```
）。若需要大型调研，则创建一个独立的
```
/jackin-dev:research
```
文档，并在
```
## Design
```
部分添加链接。之后继续决策。
达成共识。 当
```
## Design
```
部分完整涵盖整个方案时，进行总结并指向实现步骤（
```
/goal Implement <slug>.md
```
）。
提交并推送。 每完成一部分共识内容就提交一次（每次提交后推送），提交信息前缀为
```
docs:
```
。

Common mistakes

常见错误

Writing code, or filling
```
## Tasks
```
— out of scope.
Dumping a finished design without the back-and-forth, or asking many questions at once.
Recording decisions only in chat instead of into
```
## Design
```
(it must be resumable).
Restating rule-file content instead of referencing it by name.

编写代码或填充
```
## Tasks
```
部分——超出本任务范围。
未经过双向讨论就直接输出完整设计，或一次性提出多个问题。
仅在聊天中记录决策，而不写入
```
## Design
```
部分（必须保证可恢复性）。
重述规则文件内容，而非通过文件名引用。