groove-work-compound

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-work-compound

Outcome

成果

Lessons, root causes, and fixes are documented. Relevant project files are updated (rules, templates, docs, task bodies). A checklist of compound actions with done/pending status is produced.

经验教训、根本原因及修复方案均已记录。更新相关项目文件（规则、模板、文档、任务主体）。生成包含已完成/待处理状态的复合操作清单。

Acceptance Criteria

验收标准

Lessons are documented with root cause analysis (not just what went wrong, but why)
Relevant project files are updated: rules files, templates, docs, task bodies
Checklist is produced with each action marked done or pending
If user frustration patterns were detected, they are specifically captured
"No new lessons" is an explicit acceptable outcome — capture it rather than skipping

经验教训需包含根本原因分析（不仅记录问题本身，还要说明原因）
更新相关项目文件：规则文件、模板、文档、任务主体
生成清单，每项操作标记为已完成或待处理
若检测到用户受挫的模式，需专门记录
"无新经验教训"是明确可接受的结果——需记录该情况，而非跳过

Constraints

约束条件

Read
```
tasks:
```
from
```
.groove/index.md
```
to determine backend
Output goes into existing project files — do not create new files unless necessary
Always run even if it seems like "nothing to capture" — capture that explicitly
Compound actions checklist must include why each action matters, not just what it is
If user showed repeated fixes, confusion, or rework: capture the pattern and its trigger
Create stage task in backend if
```
tasks != none
```
via
```
/groove-utilities-task-create
```
with a descriptive title so multiple compounds per day are distinct:
```
YYYY-MM-DD, Compound — <brief topic>
```
(topic from the work just closed, e.g. release, feature, or session summary). Do not number stages in task titles.
After producing the compound actions checklist, identify any lesson that is about AI workflow, agent behaviour, tool usage, or engineering process — not specific to the codebase or product
If any such lesson is found:
- Propose: "Workflow learning detected — add to .groove/memory/learned/<suggested-topic>.md?"
- Suggest a topic name based on the content (e.g.
```
patterns
```
  ,
```
tools
```
  ,
```
anti-patterns
```
  ,
```
hooks
```
  )
- Wait for user to confirm, pick a different topic, or skip
- If confirmed: append the lesson as a bullet under a
```
## <YYYY-MM-DD>
```
  heading in the file; create the file with a
```
# <Topic>
```
  heading if it does not exist; create the dated heading if absent
- Add to compound checklist: "workflow learning → .groove/memory/learned/<topic>.md" (done/pending)
If no workflow lessons, skip this step entirely — no prompt, no noise

从
```
.groove/index.md
```
读取
```
tasks:
```
字段以确定后端
输出内容写入现有项目文件——除非必要，否则不要创建新文件
即使看起来"无内容可记录"，也必须执行此流程——明确记录该情况
复合操作清单必须包含每项操作的重要性原因，而非仅记录操作内容
若用户出现重复修复、困惑或返工的情况：记录该模式及其触发因素
若
```
tasks != none
```
，通过
```
/groove-utilities-task-create
```
在后端创建阶段任务，标题需具描述性，以便区分每日的多个复合任务：
```
YYYY-MM-DD, Compound — <简要主题>
```
（主题来自刚结束的工作，例如发布、功能或会话总结）。任务标题中不要包含阶段编号。
生成复合操作清单后，识别任何关于AI工作流、Agent行为、工具使用或工程流程的经验教训——而非针对代码库或产品的特定内容
若发现此类经验教训：
- 提出："检测到工作流学习内容——是否添加到.groove/memory/learned/<建议主题>.md？"
- 根据内容建议主题名称（例如
```
patterns
```
  、
```
tools
```
  、
```
anti-patterns
```
  、
```
hooks
```
  ）
- 等待用户确认、选择其他主题或跳过
- 若确认：将经验教训作为项目符号添加到文件中
```
## <YYYY-MM-DD>
```
  标题下；若文件不存在，则创建带
```
# <Topic>
```
  标题的文件；若日期标题不存在，则创建该标题
- 在复合清单中添加："工作流学习内容 → .groove/memory/learned/<topic>.md"（标记为已完成/待处理）
若无工作流相关经验教训，完全跳过此步骤——不要提示，不要产生冗余内容