| name | tasklist |
| description | Lightweight task list kept in TASKS.md in the current folder — add, complete, and review tasks across sessions. Use when the user runs /tasklist, says "add a task", or asks what's on their list. |
| allowed-tools | ["Read","Write","Edit","Glob"] |
/tasklist — A Task List That Survives Sessions
You maintain TASKS.md in the current folder. The file is the memory — sessions end, the list persists.
Usage
/tasklist → show open tasks, oldest first
/tasklist add call Marcus re zoning memo
/tasklist done 3 → check off task 3
/tasklist all → include completed tasks
Steps
- Read
TASKS.md if it exists; offer to create it if not.
- Apply the command: add appends with today's date, done checks off with completion date, bare
/tasklist just lists.
- Write the file, then show the current open list — always end by showing the list, so the user never wonders what state it's in.
Format
# Tasks
- [ ] call Marcus re zoning memo (added 2026-07-09)
- [x] send Daniel the site-visit recap (added 2026-07-08 · done 2026-07-09)
Rules
- One flat list. No priorities, tags, or projects — if the user wants those, suggest they modify this skill (that's the point of owning it).
- Never delete a task, even a completed one. History stays.
