| name | tasks |
| description | Global multi-step task tracking. Create, update, and monitor long-running tasks across threads. Tasks persist across restarts and are visible in all conversations. |
| allowed-tools | ["Bash"] |
Tasks Skill
Track complex, multi-step tasks globally. Unlike todos (per-thread), tasks are shared across ALL threads and persist across restarts.
When to Use
- Starting a complex task with 3+ steps
- User asks you to do something that will take multiple turns
- You need to track progress on ongoing work
- You want to remember what you were doing after a restart
Commands
List active tasks
alma tasks list
alma tasks list all
alma tasks list done
Create a task
alma tasks add "Build People settings page"
Update a task (set steps, progress, status)
alma tasks update <id> --steps "Design API,Build backend,Build frontend,Test,Deploy"
alma tasks update <id> --step 2 --status in_progress
alma tasks update <id> --thread <threadId>
alma tasks update <id> --title "New title"
Mark done
alma tasks done <id>
Show details
alma tasks show <id>
Delete
alma tasks delete <id>
Status Values
pending — Created but not started
in_progress — Currently being worked on
done — Completed
blocked — Waiting on something
Workflow Example
alma tasks add "Add Discord chat logging"
alma tasks update t1abc --steps "Add log method to bridge,Log user messages,Log bot replies,Test,Release"
alma tasks update t1abc --status in_progress --step 0
alma tasks update t1abc --step 1
alma tasks update t1abc --step 2
alma tasks done t1abc
Rules
- ALWAYS create a task when starting multi-step work (3+ steps)
- Update progress as you complete each step
- Mark done immediately when finished — don't leave stale tasks
- Keep task titles concise but descriptive
- Steps should be actionable and specific
- Clean up completed tasks periodically (or let them stay for history)
Storage
Tasks are stored at ~/.config/alma/tasks.json and injected into your context automatically. You can always see your active tasks.