task-management
Scannednpx machina-cli add skill anthropics/knowledge-work-plugins/task-management --openclawTask Management
Tasks are tracked in a simple TASKS.md file that both you and the user can edit.
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
Dashboard Setup (First Run)
A visual dashboard is available for managing tasks and memory. On first interaction with tasks:
- Check if
dashboard.htmlexists in the current working directory - If not, copy it from
${CLAUDE_PLUGIN_ROOT}/skills/dashboard.htmlto the current working directory - Inform the user: "I've added the dashboard. Run
/productivity:startto set up the full system."
The task board:
- Reads and writes to the same
TASKS.mdfile - Auto-saves changes
- Watches for external changes (syncs when you edit via CLI)
- Supports drag-and-drop reordering of tasks and sections
Format & Template
When creating a new TASKS.md, use this exact template (without example tasks):
# Tasks
## Active
## Waiting On
## Someday
## Done
Task format:
- [ ] **Task title** - context, for whom, due date- Sub-bullets for additional details
- Completed:
- [x] ~~Task~~ (date)
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
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
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.
Source
git clone https://github.com/anthropics/knowledge-work-plugins/blob/main/productivity/skills/task-management/SKILL.mdView on GitHub Overview
This skill centralizes task tracking in a single TASKS.md file in the current working directory. It enables a living dashboard, auto-saves changes, and drag-and-drop reordering, ensuring commitments stay visible and up-to-date.
How This Skill Works
Tasks live in TASKS.md in the current directory. If the file doesn’t exist, it is created from a fixed template. On first use, a dashboard (dashboard.html) may be copied from CLAUDE_PLUGIN_ROOT and the system is then ready to operate, with changes auto-saved and synchronized if edited externally.
When to Use It
- You're reviewing what's on your plate and you want a quick summary of Active and Waiting On.
- You want to add a new task or reminder, optionally including who it’s for and a due date.
- You finish a task and need to mark it complete and move it to the Done section.
- You want to see what you’re waiting on and how long items have been pending.
- You’re extracting action items from a meeting or conversation and want to capture them in TASKS.md, with confirmation.
Quick Start
- Step 1: In the current directory, open TASKS.md if it exists; if not, create it using the exact template from the skill.
- Step 2: Add tasks using the format - [ ] **Task title** - context, for whom, due date, and include additional details as sub-bullets.
- Step 3: If this is your first run and a dashboard is needed, copy dashboard.html from CLAUDE_PLUGIN_ROOT and inform the user: "I've added the dashboard. Run `/productivity:start` to set up the full system."
Best Practices
- Bold the task title for quick scannability.
- Include who the task is for and a due date when applicable.
- Use the exact TASKS.md template (Active, Waiting On, Someday, Done) when creating a new file.
- Keep the Done section for about a week and then clear older items.
- Ask for confirmation before auto-adding extracted tasks and avoid auto-adding without approval.
Example Use Cases
- - [ ] **Prepare slides for client meeting** - for Acme Corp, due Mar 20
- - [ ] **Draft project plan** - for Team Beta, due Apr 5
- - [x] ~~Submit expense report~~ (2026-02-15)
- - [ ] **Follow up with vendor** - waiting on VendorX, due Apr 1
- - [ ] **Schedule backlog grooming** - for Product Team, due May 10
