Task Management
Track commitments in a shared TASKS.md with optional dashboard.html sync when the user asks what is on their plate or wants tasks added or completed.
Overview
Task Management is a journey-wide agent skill that maintains TASKS.md (and optional dashboard.html) so solo builders and agents share one lightweight task board across any project phase.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill task-managementWhat is this skill?
- Single source of truth: TASKS.md in the current working directory with Active, Waiting On, Someday, and Done sections
- First-run dashboard copy from plugin bundle with auto-save and external change watch
- Structured task lines with title, context, owner, and due date; completed tasks struck through with date
- User-invocable false—agent references skill when user asks about tasks or commitments
- Points users to `/productivity:start` for full productivity system setup when dashboard is added
- 4 task sections (Active, Waiting On, Someday, Done)
Adoption & trust: 4.6k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You lose track of promises scattered across chat threads with no shared file the agent and you both update.
Who is it for?
Solo builders using Claude knowledge-work plugins who want markdown-native tasks co-edited with the agent in the repo cwd.
Skip if: Teams needing multi-project OKRs, Gantt charts, or external PM SaaS sync without a local TASKS.md convention.
When should I use this skill?
User asks about their tasks, wants to add or complete tasks, or needs help tracking commitments.
What do I get? / Deliverables
You get a consistent TASKS.md (and optional visual board) reflecting active, blocked, someday, and done work the agent can read on every status check.
- TASKS.md with standardized sections
- Optional dashboard.html task board
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Capture scope and research todos before committing to a full build.
Maintain Active vs Waiting On while the agent implements features from the same repo.
Run a launch checklist section without losing done history.
Revisit Someday items and close recurring maintenance tasks with dated completions.
How it compares
File-local TASKS.md plus optional HTML board—not a standalone MCP project server or issue tracker integration.
Common Questions / FAQ
Who is task-management for?
Indie developers and operators using Anthropics knowledge-work plugins who want the agent to manage a simple TASKS.md alongside them.
When should I use task-management?
During build for implementation backlog, at validate when tracking scope tasks, at ship for launch checklists, and in operate when monitoring recurring commitments—anytime the user asks about tasks or tracking.
Is task-management safe to install?
It writes local markdown and may copy dashboard.html; review the Security Audits panel on this page and avoid pointing it at sensitive directories you do not want the agent to modify.
SKILL.md
READMESKILL.md - Task Management
# 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.