SkillHub

Skills anthropics knowledge-work-plugins Productivity

task-management

Use it when:
You want the agent to keep your to-do list: what's on my plate, add a task, done with X, what am I waiting on.
It keeps:
One TASKS.md in the working folder, with Active, Waiting On, Someday and Done sections, created from its template if missing.
It also:
Offers to add the commitments and action items it finds when summarizing meetings or conversations, and asks before adding any.
Board:
On first use it copies the plugin's dashboard.html, a drag-and-drop task board that syncs with TASKS.md.
Runs:
On its own when you talk about tasks; user-invocable: false hides it from the slash menu.

Skill 2 of 4 in the Productivity bundle, after start and before memory-management.

Its task board, dashboard.html, ships with the productivity plugin outside the skill's folder, so a skill-only install gets TASKS.md tracking without the board.

TL;DR

Task tracking from the productivity plugin of Anthropic's knowledge-work plugins, in a plain Markdown file that you and the agent both edit. It always uses TASKS.md in the current folder. Asking what's on your plate gets a summary of Active and Waiting On, with anything overdue or urgent highlighted. A new task goes under Active as a bold title with who it's for and when it's due. A finished one is checked, struck through, dated and moved to Done, which is cleared after about a week. Asking what you're waiting on says how long each item has waited. On first use it copies dashboard.html into the folder, a board that reads and writes the same file, auto-saves, picks up edits made outside it and supports drag-and-drop reordering, and points you to /productivity:start for the full set-up.

Summarizes the skill at ab4cb1c.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill task-management

skills.sh pageSource on GitHubAll skills from anthropics/knowledge-work-plugins

Total Downloads
7,400 on skills.sh, Nov 9, 2026
Repo stars
35,234 anthropics/knowledge-work-plugins
First seen
Jan 31, 2026 on skills.sh
Weekly Downloads
62
-30% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 2189
Sep 2854
Oct 553
Oct 1259
Oct 1963
Oct 2667
Nov 262
Nov 962
Category
category:documents

Office files, notes and suites like Lark and Google Workspace.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:local

Its own steps create or change files, git state or local tools.
Needs
needs:none

Instructions only. Works in any agent that supports skills.
Publisher
by:official

A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics
notes

SKILL.md

From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.

Frontmatter
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):

# 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.