groove-utilities-task-analyse

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

groove-utilities-task-analyse

Outcome

输出结果

Tasks are summarised by status. Milestones and epics are summarised. Completed tasks include enough resolution detail for memory population bullets. Output is suitable for daily end and daily memory.

按状态汇总任务。汇总里程碑和史诗任务。已完成任务包含足够的解决详情，用于填充每日日志要点。输出内容适用于每日结束时撰写每日日志。

Acceptance Criteria

验收标准

Tasks grouped by status: in-progress, todo/ready, blocked, completed, scrapped
Milestones/epics show progress (X of Y tasks done)
Completed tasks include resolution summary (not just title)
Output contains enough detail to write meaningful daily memory bullets without re-reading tasks

按状态分组任务：进行中、待办/就绪、阻塞、已完成、已废弃
里程碑/史诗任务显示进度（已完成Y个任务中的X个）
已完成任务包含解决摘要（不仅仅是标题）
输出内容包含足够细节，无需重新查看任务即可撰写有意义的每日日志要点

Constraints

约束条件

Read

tasks:

and

task.analyse_limit

(optional; default 30) from

.groove/index.md

If
```
tasks: none
```
, no-op with friendly message
Backend mappings:
- ```
beans
```
  : (1) run
```
skills/groove-utilities-task-list/scripts/list-tasks-by-priority.sh [LIMIT]
```
  for active tasks (LIMIT from
```
task.analyse_limit
```
  or 30); (2) run
```
beans list --json --status completed
```
  and
```
beans list --json --status scrapped
```
  for completed/scrapped; merge, group by status, then summarise (milestones/epics and resolution detail as per acceptance criteria)
- ```
linear
```
  : fetch all assigned issues via linear CLI or MCP, group by state
- ```
github
```
  :
```
gh issue list --state all --assignee @me
```
  , group by label/state
For completed tasks: include the body's "Summary of Changes" section if present
If a completed task has no resolution, note that it is missing — do not omit the task
Output format should be scannable markdown (headers per status group, bullet per task)

从
```
.groove/index.md
```
中读取
```
tasks:
```
和
```
task.analyse_limit
```
（可选；默认值为30）
如果
```
tasks: none
```
，则不执行操作并返回友好提示信息
后端映射：
- ```
beans
```
  ：(1) 运行
```
skills/groove-utilities-task-list/scripts/list-tasks-by-priority.sh [LIMIT]
```
  获取活跃任务（LIMIT取自
```
task.analyse_limit
```
  或默认30）；(2) 运行
```
beans list --json --status completed
```
  和
```
beans list --json --status scrapped
```
  获取已完成/已废弃任务；合并结果，按状态分组，然后汇总（按验收标准要求的里程碑/史诗任务和解决详情）
- ```
linear
```
  ：通过Linear CLI或MCP获取所有已分配的问题，按状态分组
- ```
github
```
  ：执行
```
gh issue list --state all --assignee @me
```
  ，按标签/状态分组
对于已完成任务：如果存在正文的“Summary of Changes”部分，则包含该部分内容
如果已完成任务没有解决详情，需注明缺失——不要省略该任务
输出格式应为易于扫描的Markdown（每个状态组对应一个标题，每个任务对应一个项目符号）