Skill Tracer
Skills › Knowledge Work Plugins › task-management

task-management

skill · 91 lines · Apache-2.0 · productivity/skills/task-management/SKILL.md

The facts

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

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

This skill is not user-invocable, so it is not picked by a slash command; the agent pulls it in when the conversation turns to the user's own tasks — asking what is on their plate, adding or completing a task, or tracking a commitment to someone. It then works against a shared TASKS.md file in the current working directory.

Things a person might say (the model's guesses)

  • “What's on my plate today?”
  • “Remind me to send the contract to Dana by Friday.”
  • “I'm done with the vendor review, mark it off.”

A model's summary of when it is used.

A model's reading

Who can start it

Only the agent

Only the agent starts it. It's hidden from your commands.

From its settingsline 4

What it leads to

  • hands off to start on first run, once the dashboard has been added line 24

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

Apache-2.0, from productivity/LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: task-management
3description: 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.
4user-invocable: false
5---
6
7# Task Management
8
9Tasks are tracked in a simple `TASKS.md` file that both you and the user can edit.

Task Management

Tasks are tracked in a simple TASKS.md file that both you and the user can edit.

Raw lines 1 to 10
11## File Location
13**Always use `TASKS.md` in the current working directory.**
15- If it exists, read/write to it
16- If it doesn't exist, create it with the template below

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
Raw lines 11 to 17
18## Dashboard Setup (First Run)
20A visual dashboard is available for managing tasks and memory. **On first interaction with tasks:**
221. Check if `dashboard.html` exists in the current working directory
232. If not, copy it from `${CLAUDE_PLUGIN_ROOT}/skills/dashboard.html` to the current working directory
243. Inform the user: "I've added the dashboard. Run `/productivity:start` to set up the full system."
26The task board:
27- Reads and writes to the same `TASKS.md` file
28- Auto-saves changes
29- Watches for external changes (syncs when you edit via CLI)
30- Supports drag-and-drop reordering of tasks and sections

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
Raw lines 18 to 31
Names a skill start :24
32## Format & Template
34When creating a new TASKS.md, use this exact template (without example tasks):
36```markdown
37# Tasks
39## Active
41## Waiting On
43## Someday
45## Done
46```
48Task format:
49- `- [ ] **Task title** - context, for whom, due date`
50- Sub-bullets for additional details
51- Completed: `- [x] ~~Task~~ (date)`

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)
Raw lines 32 to 52
53## How to Interact
55**When user asks "what's on my plate" / "my tasks":**
56- Read TASKS.md
57- Summarize Active and Waiting On sections
58- Highlight anything overdue or urgent
60**When user says "add a task" / "remind me to":**
61- Add to Active section with `- [ ] **Task**` format
62- Include context if provided (who it's for, due date)
64**When user says "done with X" / "finished X":**
65- Find the task
66- Change `[ ]` to `[x]`
67- Add strikethrough: `~~task~~`
68- Add completion date
69- Move to Done section
71**When user asks "what am I waiting on":**
72- Read the Waiting On section
73- Note how long each item has been waiting

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
Raw lines 53 to 74
Uses an outside tool ~~task :67
75## Conventions
77- **Bold** the task title for scannability
78- Include "for [person]" when it's a commitment to someone
79- Include "due [date]" for deadlines
80- Include "since [date]" for waiting items
81- Sub-bullets for additional context
82- Keep Done section for ~1 week, then clear old items

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
Raw lines 75 to 83
84## Extracting Tasks
86When summarizing meetings or conversations, offer to add extracted tasks:
87- Commitments the user made ("I'll send that over")
88- Action items assigned to them
89- Follow-ups mentioned
91Ask before adding - don't auto-add without confirmation.

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.

Raw lines 84 to 91

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.