task-management

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Task Management

任务管理

Tasks are tracked in a simple
TASKS.md
file that both you and the user can edit.
任务通过一个简单的
TASKS.md
文件进行追踪,你和用户都可以编辑该文件。

File Location

文件位置

Always use
TASKS.md
in the current working directory.
  • If it exists, read/write to it
  • If it doesn't exist, create it with the template below
请始终使用当前工作目录下的
TASKS.md
  • 如果文件已存在,直接对其进行读写操作
  • 如果文件不存在,使用下方模板创建它

Dashboard Setup (First Run)

仪表板设置(首次运行)

A visual dashboard is available for managing tasks and memory. On first interaction with tasks:
  1. Check if
    dashboard.html
    exists in the current working directory
  2. If not, copy it from
    ${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html
    to the current working directory
  3. Inform the user: "I've added the dashboard. Run
    /productivity:start
    to set up the full system."
The task board:
  • Reads and writes to the same
    TASKS.md
    file
  • Auto-saves changes
  • Watches for external changes (syncs when you edit via CLI)
  • Supports drag-and-drop reordering of tasks and sections
我们提供了一个可视化仪表板用于管理任务和记忆。首次处理任务相关交互时:
  1. 检查当前工作目录中是否存在
    dashboard.html
  2. 如果不存在,将
    ${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html
    复制到当前工作目录
  3. 告知用户:“我已添加了仪表板。运行
    /productivity:start
    来完成完整系统的设置。”
任务看板特性:
  • 读写同一个
    TASKS.md
    文件
  • 自动保存更改
  • 监控外部更改(当你通过CLI编辑时会自动同步)
  • 支持任务和板块的拖放重排序

Format & Template

格式与模板

When creating a new TASKS.md, use this exact template (without example tasks):
markdown
undefined
创建新的TASKS.md时,请严格使用以下模板(不含示例任务):
markdown
undefined

Tasks

Tasks

Active

Active

Waiting On

Waiting On

Someday

Someday

Done

Done


Task format:
- `- [ ] **Task title** - context, for whom, due date`
- Sub-bullets for additional details
- Completed: `- [x] ~~Task~~ (date)`

任务格式:
- `- [ ] **任务标题** - 背景信息,对接人,截止日期`
- 使用子项目符号添加额外细节
- 已完成任务格式:`- [x] ~~任务内容~~ (完成日期)`

How to Interact

交互方式

When user asks "what's on my plate" / "my tasks":
  • Read TASKS.md
  • Summarize Active and Waiting On sections
  • Highlight anything overdue or urgent
When user says "add a task" / "remind me to":
  • Add to Active section with
    - [ ] **Task**
    format
  • Include context if provided (who it's for, due date)
When user says "done with X" / "finished X":
  • Find the task
  • Change
    [ ]
    to
    [x]
  • Add strikethrough:
    ~~task~~
  • Add completion date
  • Move to Done section
When user asks "what am I waiting on":
  • Read the Waiting On section
  • Note how long each item has been waiting
当用户询问“我有哪些待办任务” / “我的任务情况”时:
  • 读取TASKS.md文件
  • 总结“Active(进行中)”和“Waiting On(等待中)”板块的内容
  • 突出显示任何逾期或紧急的任务
当用户说“添加一个任务” / “提醒我做某事”时:
  • 使用
    - [ ] **任务内容**
    格式将任务添加到“Active(进行中)”板块
  • 如果用户提供了相关背景信息(如对接人、截止日期),请一并包含
当用户说“我完成了X任务” / “结束X任务”时:
  • 找到对应的任务
  • [ ]
    修改为
    [x]
  • 添加删除线格式:
    ~~任务内容~~
  • 添加完成日期
  • 将任务移动到“Done(已完成)”板块
当用户询问“我在等待哪些事项”时:
  • 读取“Waiting On(等待中)”板块的内容
  • 记录每个事项的等待时长

Conventions

约定规范

  • Bold the task title for scannability
  • Include "for [person]" when it's a commitment to someone
  • Include "due [date]" for deadlines
  • Include "since [date]" for waiting items
  • Sub-bullets for additional context
  • Keep Done section for ~1 week, then clear old items
  • 任务标题使用加粗格式以提升可读性
  • 如果是对他人的承诺,请包含“对接人:[姓名]”
  • 有截止日期的任务请包含“截止日期:[日期]”
  • 等待中的事项请包含“开始等待日期:[日期]”
  • 使用子项目符号添加额外背景信息
  • “Done(已完成)”板块的内容保留约1周,之后清理旧任务

Extracting Tasks

任务提取

When summarizing meetings or conversations, offer to add extracted tasks:
  • Commitments the user made ("I'll send that over")
  • Action items assigned to them
  • Follow-ups mentioned
Ask before adding - don't auto-add without confirmation.
在总结会议或对话内容时,可以主动提出提取任务:
  • 用户做出的承诺(如“我会把文件发过去”)
  • 分配给用户的行动项
  • 提及的后续跟进事项
添加前请先询问用户,不要未经确认就自动添加。