groove-work-exec
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesegroove-work-exec
groove-work-exec
Outcome
成果
Code, tests, and artifacts are written per the plan. The work task is created/updated in the backend with progress notes. Output is ready for review.
按照计划编写代码、测试用例和相关工件。在后端创建/更新工作任务并添加进度备注。输出内容已准备好用于评审。
Acceptance Criteria
验收标准
- Implementation matches the plan from
/groove-work-plan - Work task body tracks progress with dated notes
- Output (code, tests, docs) is complete enough to hand off to
/groove-work-review - Stage task created/updated in backend:
YYYY-MM-DD, Work
- 实现内容与中的计划一致
/groove-work-plan - 工作任务主体中包含带日期的进度备注以跟踪进度
- 输出内容(代码、测试、文档)已足够完善,可移交至
/groove-work-review - 在后端创建/更新阶段任务:
YYYY-MM-DD, Work
Constraints
约束条件
- Read from
tasks:to determine backend.groove/index.md - If no prior plan exists, warn the user and ask them to confirm scope before proceeding
- Append progress notes to task body as work proceeds — do not overwrite
- Do not mark task as completed during this stage — that happens after review
- Create stage task via if
/groove-utilities-task-create(titletasks != none)YYYY-MM-DD, Work
- 从中读取
.groove/index.md字段以确定后端系统tasks: - 如果没有预先制定的计划,需向用户发出警告,并在继续前请用户确认范围
- 工作推进过程中,将进度备注追加到任务主体中——请勿覆盖原有内容
- 在此阶段请勿标记任务为已完成——完成标记需在评审后进行
- 如果,通过
tasks != none创建阶段任务(标题为/groove-utilities-task-create)YYYY-MM-DD, Work