Task Management
AnthropicOfficialPublished by Anthropic
- Skill
- Workflow
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to tracking tasks, commitments, and follow-ups using a shared TASKS.md file. It supports manual task entry, status updates, and progress tracking, while offering an optional visual dashboard for drag-and-drop management. The system emphasizes clear formatting, status categorization, and proactive task extraction from conversations.
What it does
- Maintains a centralized TASKS.md file for tracking active, pending, and completed items.
- Supports a visual dashboard for drag-and-drop task reordering and management.
- Provides standardized formatting for task titles, deadlines, and context.
- Facilitates the extraction of action items and commitments from ongoing conversations.
- Automates the transition of tasks between status sections like Active, Waiting On, and Done.
When to use it
- When you need a lightweight, file-based system to track daily to-dos.
- When you want to capture commitments or follow-ups during a meeting or chat.
- When you prefer a visual interface for managing task priorities.
- When you need to keep track of items you are waiting on from others.
Advantages
- Simple, human-readable format that is easy to edit manually or via AI.
- Persistent storage within the local working directory.
- Supports both text-based CLI interaction and a visual dashboard.
- Encourages consistent documentation of deadlines and context.
Usage examples
- “What is on my plate today?”
- The agent reads the TASKS.md file and provides a summary of all items in the Active and Waiting On sections, highlighting any urgent or overdue tasks.
- “Remind me to email the project proposal to Sarah by Friday.”
- The agent adds a new task to the Active section of TASKS.md formatted as - [ ] **Email project proposal** - for Sarah, due Friday.
- “I finished the design review.”
- The agent locates the design review task in TASKS.md, marks it as complete with a strikethrough, adds the current date, and moves it to the Done section.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/task-management/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip task-management.zip -d .agents/skills
Documentation by Anthropic
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:
Check if
dashboard.htmlexists in the current working directoryIf not, copy it from
${CLAUDE_PLUGIN_ROOT}/skills/dashboard.htmlto the current working directoryInform 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.mdfileAuto-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
## DoneTask format:
- [ ] **Task title** - context, for whom, due dateSub-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**formatInclude 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer942 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md2.5 KiB
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · productivity/skills/task-management · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from productivity/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download task-management.zip