groove-work-brainstorm

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-work-brainstorm

Outcome

成果

Scope is clarified through dialogue. Key decisions and open questions are surfaced. Output is captured as a brainstorm doc or task in the configured backend.

通过对话明确范围，梳理出关键决策和待解决问题，输出内容将作为头脑风暴文档或任务保存至配置的后端中。

Acceptance Criteria

验收标准

Scope is clearly defined and deliberately constrained (YAGNI applied)
Key decisions are listed with rationale
Open questions are listed (not resolved — resolution happens in plan)
Output exists either as a brainstorm doc or as a task body in the backend
Stage task created in backend:
```
YYYY-MM-DD, Brainstorm
```

范围已明确定义且经过刻意约束（应用YAGNI原则）
关键决策及其制定依据已列出
待解决问题已列出（无需在此处解决——解决过程在规划阶段完成）
输出内容以头脑风暴文档或后端中的任务正文形式存在
后端已创建阶段任务：
```
YYYY-MM-DD, Brainstorm
```

Constraints

约束条件

Read
```
tasks:
```
from
```
.groove/index.md
```
to determine backend

Use template at

skills/groove-work-brainstorm/templates/brainstorm-doc.md

for doc output

Enforce YAGNI — scope is deliberately constrained at this stage; push back on scope creep
Do not start planning implementation here — that belongs in
```
/groove-work-plan
```
Ask clarifying questions before finalising scope; do not assume
If user provides $ARGUMENTS, use as the topic/title for the brainstorm

Create stage task via

/groove-utilities-task-create

tasks != none

(title

YYYY-MM-DD, Brainstorm

)

读取
```
.groove/index.md
```
中的
```
tasks:
```
字段以确定后端

文档输出使用

skills/groove-work-brainstorm/templates/brainstorm-doc.md

路径下的模板

强制执行YAGNI原则——此阶段需刻意约束范围，抵制范围蔓延
不要在此处开始规划实现方案——该工作属于
```
/groove-work-plan
```
的范畴
在最终确定范围前询问澄清问题，不要主观假设
如果用户提供$ARGUMENTS，将其用作本次头脑风暴的主题/标题

如果

tasks != none

，通过

/groove-utilities-task-create

创建阶段任务（标题为

YYYY-MM-DD, Brainstorm

）