Back to Details

groove-utilities-task-archive

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

groove-utilities-task-archive

groove-utilities-task-archive

Outcome

结果

All completed and scrapped tasks are archived in the configured backend. The count of archived tasks is reported to the user.
所有已完成和已取消的任务都会被归档到已配置的后端中，系统会向用户反馈已归档的任务数量。

Acceptance Criteria

验收标准

  • All completed/scrapped tasks are moved to archived state in backend
  • User is shown the scope of what will be archived and confirms before running
  • Count of archived tasks is reported after completion
  • 所有已完成/已取消的任务都会在后端被移至归档状态
  • 执行归档操作前会向用户展示待归档内容的范围，用户确认后才会执行
  • 操作完成后会反馈已归档的任务数量

Constraints

约束条件

  • Read 
    tasks:
    from 
    .groove/index.md
    to determine backend
  • If 
    tasks: none
    , no-op with friendly message
  • Always show user what will be archived and ask for confirmation before proceeding
  • Never run automatically during daily end — only when user explicitly requests
  • Backend mappings: 
    • beans
      : 
      beans archive
      (archives all completed/scrapped — no single-task option)
    • linear
      : mark filtered issues as archived via linear CLI or MCP
    • github
      : close resolved issues via 
      gh issue close
  • Report count of archived tasks after completion
  • 从 
    .groove/index.md
    中读取 
    tasks:
    配置来确定后端
  • 如果 
    tasks: none
    ，不执行任何操作并返回友好提示
  • 执行操作前必须向用户展示待归档内容并请求确认
  • 禁止在每日结束时自动运行 —— 仅在用户明确发起请求时执行
  • 后端映射规则： 
    • beans
      : 
      beans archive
      （归档所有已完成/已取消任务 —— 无单任务归档选项）
    • linear
      : 通过linear CLI或MCP将筛选出的issue标记为已归档
    • github
      : 通过
      gh issue close
      关闭已解决的issue
  • 操作完成后反馈已归档的任务数量