task-management — Claude Code skill: what it does, how to install
Tracks commitments, active work, and follow-ups in a local TASKS.md file. Useful when managing project to-dos directly from the AI coding chat.
npx skills add anthropics/knowledge-work-plugins --skill task-management -a claude-codeWhat task-management does
The skill maintains a TASKS.md file in your current working directory. It uses four sections: Active, Waiting On, Someday, and Done. On the first run, it copies dashboard.html to the project folder. This provides a drag-and-drop board that syncs with CLI edits and saves changes automatically.
The assistant extracts commitments and deadlines when reviewing meeting notes. It will never add tasks silently. The agent asks for confirmation first. Completed items receive a strikethrough and a completion date before moving to Done. Because the skill strictly targets the current working directory, switching folders creates a fresh tracking file.
What it helps with
- track project tasks in a local markdown file
- extract follow-up commitments from meeting summaries
- monitor pending items and waiting durations
- archive completed tasks with completion dates
Example prompts for the agent
- What tasks are currently on my plate, and is anything overdue?
- Add a task: draft release notes for Alex due Friday
- Finished the database migration, mark it done
How to install task-management
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill task-management -a claude-code2Manually: put the files in place
~/.claude/skills/task-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/task-management/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill task-management -a codex2Manually: put the files in place
.agents/skills/task-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill task-management -a cursor2Manually: put the files in place
.cursor/skills/task-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins task-management2Manually: put the files in place
.github/skills/task-management/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill task-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path productivity/skills/task-managementManually: put the files in place
.devin/skills/task-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill task-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set133
The whole set →Similar
Questions about task-management
How do I install task-management in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill task-management -a claude-code. Alternatively, copy the skill definition manually to ~/.claude/skills/task-management/SKILL.md.
What does the task-management skill do?
It manages a TASKS.md file in the current working directory across Active, Waiting On, Someday, and Done sections. It also deploys a visual dashboard.html interface for managing tasks.
Does the skill automatically record tasks from discussions?
No, while the assistant identifies commitments and action items in conversations, it always asks for confirmation before adding anything to TASKS.md.
Source text
SKILL.md · Apache-2.0
---
name: task-management
description: Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
user-invocable: false
---
# Task 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:**
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
## Format & Template
When creating a new TASKS.md, use this exact template (without example tasks):
```markdown
# 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.
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins