work

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- groove:managed — do not edit; changes will be overwritten by groove update -->
<!-- groove:managed — 请勿编辑;变更将被groove更新覆盖 -->

work

执行

The compound engineering loop — five discrete stages that systematically reduce rework by front-loading clarity and back-loading lessons. Each stage can be run independently or in sequence.
复合工程循环——通过前置明确需求、后置沉淀经验,系统性减少返工的五个独立阶段。每个阶段可独立运行或按顺序执行。

Git Root Detection

Git 根目录检测

Before running any command, detect the git root:
bash
git rev-parse --show-toplevel
在运行任何命令前,先检测git根目录:
bash
git rev-parse --show-toplevel

Commands

命令

CommandDescription
brainstorm
Clarify scope through dialogue, surface key decisions and open questions
plan
Research codebase, write concrete implementation plan
work
Execute the plan, track progress in task backend
review
Evaluate output, identify lessons, decide accept/rework
compound
Document lessons, update rules/templates/docs
命令描述
brainstorm
通过对话明确范围,梳理关键决策与待解决问题
plan
研究代码库,编写具体的实施计划
work
执行计划,在任务后端跟踪进度
review
评估输出内容,总结经验,决定接受/返工
compound
记录经验,更新规则/模板/文档

$ARGUMENTS Routing

$ARGUMENTS 路由

$ARGUMENTSAction
help
commands/help.md
brainstorm
commands/brainstorm.md
plan
commands/plan.md
work
commands/work.md
review
commands/review.md
compound
commands/compound.md
(empty)
commands/help.md
$ARGUMENTS操作
help
commands/help.md
brainstorm
commands/brainstorm.md
plan
commands/plan.md
work
commands/work.md
review
commands/review.md
compound
commands/compound.md
(空)
commands/help.md

Stage Task Naming

阶段任务命名

Each stage creates or updates a task in the configured backend (if
tasks != none
). Tasks follow the naming convention:
YYYY-MM-DD, <N>. <Stage>
e.g.
2026-02-28, 1. Brainstorm
,
2026-02-28, 2. Plan
Tasks are created under the relevant workstream epic if one exists.
每个阶段会在已配置的后端中创建或更新任务(若
tasks != none
)。任务遵循以下命名规范:
YYYY-MM-DD, <N>. <Stage>
例如:
2026-02-28, 1. Brainstorm
2026-02-28, 2. Plan
若存在相关的工作流史诗任务,新任务会创建在其下方。

Frustration Detection

挫败感检测

If the user shows signs of repeated fixes, confusion, or rework — proactively suggest running
work compound
even mid-stream. The value of compound is in capturing lessons before they fade.
如果用户出现重复修复、困惑或返工的迹象——即使在流程进行中,也应主动建议运行
work compound
。沉淀阶段的价值在于在经验遗忘前将其记录下来。

Design Note

设计说明

80% of the compound loop's value comes from
plan
and
review
.
work
is execution. Do not skip
plan
— scope creep and rework almost always trace back to an unclear plan.
复合工程循环80%的价值来自
plan
review
阶段。
work
阶段仅为执行环节。请勿跳过
plan
阶段——范围蔓延和返工几乎总是源于模糊不清的计划。