task-management
npx machina-cli add skill nsalvacao/nsalvacao-claude-code-plugins/task-management --openclawTask 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
Cockpit Dashboard
The cockpit dashboard provides a visual task board. Launch it with /productivity-cockpit:start — it reads and writes the same TASKS.md file and auto-syncs external changes.
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.
Source
git clone https://github.com/nsalvacao/nsalvacao-claude-code-plugins/blob/main/plugins/productivity-cockpit/skills/task-management/SKILL.mdView on GitHub Overview
Task management using a shared TASKS.md file keeps commitments transparent and synchronized between you and the user. It uses a four-section template (Active, Waiting On, Someday, Done) and a cockpit dashboard to visualize progress.
How This Skill Works
The skill reads and writes TASKS.md in the current directory; if the file doesn’t exist it creates it from the exact template. Tasks are added as - [ ] **Task title** - context, for whom, due date, with sub-bullets for details; completing a task converts it to - [x] ~~Task~~ (date) and moves it to the Done section.
When to Use It
- When the user asks what's on their plate or wants to see their current tasks.
- When the user wants to add a new task or reminder and capture context like who it’s for and due date.
- When the user marks a task as done and wants it archived with a completion date.
- When the user asks what they’re waiting on and wants to view the Waiting On list.
- When summarizing meetings or conversations and extracting tasks, with explicit confirmation before adding any new items.
Quick Start
- Step 1: Ensure TASKS.md exists in the current working directory; if not, the skill will create it from the template.
- Step 2: Open the cockpit dashboard with /productivity-cockpit:start to view and sync the TASKS.md task board.
- Step 3: Ask for task-related actions (e.g., 'what's on my plate', 'add a task', 'done with X') and the skill will update TASKS.md accordingly.
Best Practices
- Always use the exact TASKS.md template when creating a new file (the template includes Active, Waiting On, Someday, Done).
- Bold the task title in - [ ] **Task** for quick scanning, and include who it’s for and due date in the line.
- Add supporting details as sub-bullets and keep the Done section for about one week to stay focused.
- Keep items in Waiting On annotated with since [date] and track how long they’ve been waiting.
- Review and summarize Active and Waiting On regularly, and ask for confirmation before extracting or auto-adding tasks.
Example Use Cases
- - [ ] **Prepare Q2 budget** - for Finance Team, due 2026-03-15
- - [ ] **Awaiting client approval** - for Acme Co, since 2026-02-25
- - [ ] **Learn advanced SQL topics**
- - [x] ~~Finalize onboarding doc~~ (2026-02-20)
- - [ ] **Draft recap email** - for Team, due 2026-03-08
