| name | task-management |
| description | Simple task management using a shared TASKS.md file. |
Task Management
Tasks live in TASKS.md in the current working directory.
File Rules
- Always use
TASKS.md
- If it does not exist, create it with this template:
# Tasks
## Active
## Waiting On
## Someday
## Done
Dashboard
On first task interaction:
- Check for
dashboard.html
- If missing, copy it from
./skills/dashboard.html
- Tell the user:
I've added the dashboard. Run /work-start to set up the full system.
Task Format
- Task:
- [ ] **Task title** - [Project X](memory/projects/project-x.md), follow up with [John Doe](memory/people/john-doe.md) _(added YYYY-MM-DD)_
- Executable subtask:
- [ ] Sub-step
- Context note:
- Context note
- Done:
- [x] ~~Task~~ (date)
Common Actions
List tasks
- Read
TASKS.md
- Summarize
Active and Waiting On
- Highlight overdue or urgent items
Add a task
- Add to
Active
- Include context if given: person, project, due date, waiting status
- Prefer linking to existing memory pages instead of duplicating long context in
TASKS.md
Complete a task
- Change
[ ] to [x]
- Add strikethrough and completion date
- Move it to
Done
Waiting on
- Use
Waiting On for dependencies or pending replies
- Include who or what is blocking progress when known
Conventions
- Bold the task title
- Prefer markdown links for project and person references when the corresponding memory page exists
- Include
for [person] when it is a commitment
- Include
due [date] for deadlines
- Include
since [date] for waiting items
- Prefer checkbox sub-steps for actionable work
- Use plain sub-bullets only for context or constraints
- Keep
Done to about one week of recent completions
Extracting Tasks
When summarizing meetings or conversations, offer to add:
- commitments the user made
- action items assigned to them
- follow-ups that clearly need tracking
If extracted task context reveals durable new people, projects, or terms, suggest /work-update to refresh memory.
Ask before adding extracted tasks.