groove-utilities-task-update

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-utilities-task-update

Outcome

结果

A task's status, body, or metadata is updated in the configured backend. Progress notes are appended without overwriting existing content. When completing a task, a resolution (Summary of Changes or Reasons for Scrapping) is written to the task body before marking done.

在已配置的后端中更新任务的状态、正文或元数据。进度记录将被追加，不会覆盖现有内容。完成任务时，在标记为完成前，需在任务正文中写入解决方案（变更摘要或废弃原因）。

Acceptance Criteria

验收标准

Specified fields are updated in backend
Existing body content is preserved; new content is appended
Completed tasks have a "Summary of Changes" or "Reasons for Scrapping" section in body
User confirms before task is marked as completed or scrapped

在后端中更新指定字段
保留现有正文内容；追加新内容
已完成的任务正文中包含“变更摘要”或“废弃原因”部分
在任务标记为完成或废弃前需用户确认

Constraints

约束条件

Read
```
tasks:
```
from
```
.groove/index.md
```
to determine backend
If
```
tasks: none
```
, no-op with friendly message
Never mark a task completed without a resolution section in the body
Ask user to provide resolution if task body has none
User must explicitly confirm completion — do not auto-complete
Progress notes should be appended as dated bullets under a "Progress" section

Backend mappings:

beans

beans update <id> -s <status>

and

beans update <id> -d "<body>"

```
linear
```
: update issue via linear CLI or MCP

github

gh issue edit <number> --body "<body>"

and label/close commands

读取
```
.groove/index.md
```
中的
```
tasks:
```
配置以确定后端类型
如果
```
tasks: none
```
，则执行空操作并返回友好提示信息
任务正文中没有解决方案部分时，绝不能标记为完成
如果任务正文中没有解决方案，要求用户提供
必须由用户明确确认后才能完成任务——不得自动完成
进度记录应作为带日期的项目符号追加到“进度”部分下

后端映射：

beans

：使用

beans update <id> -s <status>

和

beans update <id> -d "<body>"

命令

```
linear
```
：通过linear CLI或MCP更新问题

github

：使用

gh issue edit <number> --body "<body>"

命令以及标签/关闭命令