groove-work-plan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-work-plan

Outcome

产出

The codebase is researched for relevant patterns and constraints. A concrete implementation plan is written with ordered steps, file paths, and function names. Plan is captured as a task or doc.

完成代码库相关模式和约束的调研。编写包含有序步骤、文件路径和函数名称的具体实现方案。方案会以任务或文档的形式留存。

Acceptance Criteria

验收标准

Plan references actual code patterns found in the codebase (not assumptions)
Steps are ordered and specific enough to execute without ambiguity
File paths and function names are named where known
Edge cases are identified and handling is specified
Stage task created in backend:
```
YYYY-MM-DD, Plan
```

方案引用代码库中实际存在的代码模式（而非假设）
步骤有序且足够具体，执行时无歧义
已知的文件路径和函数名称都已明确标注
识别出边界情况并指定了处理方式
在后端创建阶段任务：
```
YYYY-MM-DD, Plan
```

Constraints

约束条件

Read
```
tasks:
```
from
```
.groove/index.md
```
to determine backend
Use Explore agent for codebase research before writing the plan
Use template at
```
skills/work/templates/plan-doc.md
```
for doc output
Warn if no prior brainstorm exists — ask user to confirm scope before proceeding
Do not write code during plan — plan only

Create stage task via

/groove-utilities-task-create

tasks != none

(title

YYYY-MM-DD, Plan

)

读取
```
.groove/index.md
```
中的
```
tasks:
```
字段来确定后端
编写方案前使用Explore agent完成代码库调研
文档输出使用
```
skills/work/templates/plan-doc.md
```
模板
如果没有预先的头脑风暴记录则发出警告——继续操作前询问用户确认范围
方案阶段不编写代码——仅完成方案规划

如果

tasks != none

则通过

/groove-utilities-task-create

创建阶段任务（标题为

YYYY-MM-DD, Plan

）