jackin-brainstorm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

jackin-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-brainstorm <slug>
```
to design an open roadmap item.

操作者运行
```
jackin-brainstorm <slug>
```
来设计一个待推进的路线图项。

When NOT to use

非使用场景

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

创建路线图项 → 使用
```
jackin-propose
```
。
大型外部/代码库调研 → 使用
```
jackin-research
```
。
实施开发 → 使用
```
/goal Implement <slug>.md
```
。

Arguments

参数

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

```
--research
```
— 若路线图项内容不够完善，先运行
```
jackin-research
```
。
```
--resume
```
— 从当前
```
## Design
```
章节的状态继续推进。

Process

流程

Load context. Read
```
docs/content/docs/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-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/roadmap/<slug>.mdx
```
文件中的问题、重要性说明、现有设计、相关文件，以及所有已关联的研究资料。
自由讨论。进行开放式双向沟通：提出替代方案、分析利弊、梳理待解决问题。将jackin❯设计原则及相关规则文件（
```
ENGINEERING.md
```
、
```
HOST_AND_CONTAINER.md
```
、TUI/docs规则）作为约束条件。建议每次只讨论一个问题，待每个部分确定后再推进下一部分。
逐步撰写。每当一个要点确定后，在
```
.mdx
```
文件的
```
## Design
```
章节中追加或更新对应内容——需包含决策内容及一行简短的决策原因。使用
```
--resume
```
参数可从此状态继续推进。
**遇到未知问题？**快速收集信息（探索/搜索，或使用
```
deep-research
```
）。若需大型调研 → 创建独立的
```
jackin-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
```
章节（必须保证任务可恢复）。
重复规则文件内容，而非通过文件名引用。