Task Manager
Use this skill for task capture and task lifecycle updates.
Trigger
{
"activation": {
"anyPhrases": [
"add a task",
"create a task",
"track this task",
"task status",
"mark this done",
"block this task",
"what tasks do we have"
]
},
"movement": {
"target": "desk",
"skipIfAlreadyThere": true
}
}
Also use this skill even when those exact phrases are absent if the latest user message is an actionable work request. If the user asks the agent to do something, that request must become a task before the agent proceeds.
Storage location
The authoritative task file is:
${OPENCLAW_STATE_DIR}/claw3d/task-manager/tasks.json when OPENCLAW_STATE_DIR is set.~/.openclaw/claw3d/task-manager/tasks.json otherwise.
Always treat that file as the shared source of truth for the Kanban board.
Required workflow
- Read the task file before handling an actionable request.
- If the file does not exist, create it with the schema in this document.
- If the latest user message is actionable and no matching active task exists, create one immediately.
- Before starting execution, ensure the task is
todo or move it to in_progress.
- If work cannot continue, set the task to
blocked and record a short reason in notes.
- When work is finished, set the task to
done.
- When work needs user review or confirmation, set the task to
review.
- After every mutation, write the full updated JSON back to disk.
Matching rules
- Match first by
externalThreadId when the request comes from a stable thread or conversation.
- Otherwise match by a concise normalized title that preserves user intent.
- Avoid creating duplicate active tasks for the same request.
Task fields
Each task must include:
idtitledescriptionstatussourcesourceEventIdassignedAgentIdcreatedAtupdatedAtplaybookJobIdrunIdchannelexternalThreadIdlastActivityAtnotesisArchivedisInferredhistory
Status rules
- New actionable requests start as
todo unless work has already begun.
- Move to
in_progress when the agent is actively working.
- Move to
blocked when progress depends on missing input, credentials, approvals, or failures.
- Move to
review when the work is ready for inspection or handoff.
- Move to
done only when the requested work is complete.
File format
{
"schemaVersion": 1,
"updatedAt": "2026-03-30T00:00:00.000Z",
"tasks": [
{
"id": "research-mtulsa-com",
"title": "Research mtulsa.com",
"description": "Review mtulsa.com and summarize the site, positioning, and improvement opportunities.",
"status": "in_progress",
"source": "claw3d_manual",
"sourceEventId": null,
"assignedAgentId": "main",
"createdAt": "2026-03-30T00:00:00.000Z",
"updatedAt": "2026-03-30T00:10:00.000Z",
"playbookJobId": null,
"runId": null,
"channel": "telegram",
"externalThreadId": "telegram:direct:6866695577",
"lastActivityAt": "2026-03-30T00:10:00.000Z",
"notes": [],
"isArchived": false,
"isInferred": false,
"history": [
{
"at": "2026-03-30T00:00:00.000Z",
"type": "created",
"note": "Task created.",
"fromStatus": null,
"toStatus": "todo"
},
{
"at": "2026-03-30T00:10:00.000Z",
"type": "status_changed",
"note": null,
"fromStatus": "todo",
"toStatus": "in_progress"
}
]
}
]
}
Response rules
- Briefly confirm which task was created or updated.
- If the request is ambiguous, ask a clarifying question instead of guessing.
- Do not claim work is complete without updating the task status.
1---2name: task-manager3description: Capture actionable user requests as persistent tasks, update task status as work progresses, and keep a shared task store in sync. Use when a user asks an agent to do work, check progress, block a task, complete a task, or manage the Kanban board.4---5
6# Task Manager
7
8Use this skill for task capture and task lifecycle updates.
9
10## Trigger
11
12```json
13{
14 "activation": {
15 "anyPhrases": [
16 "add a task",
17 "create a task",
18 "track this task",
19 "task status",
20 "mark this done",
21 "block this task",
22 "what tasks do we have"
23 ]
24 },
25 "movement": {
26 "target": "desk",
27 "skipIfAlreadyThere": true
28 }
29}
30```
31
32Also use this skill even when those exact phrases are absent if the latest user message is an actionable work request. If the user asks the agent to do something, that request must become a task before the agent proceeds.
33
34## Storage location
35
36The authoritative task file is:
37
38- `${OPENCLAW_STATE_DIR}/claw3d/task-manager/tasks.json` when `OPENCLAW_STATE_DIR` is set.
39- `~/.openclaw/claw3d/task-manager/tasks.json` otherwise.
40
41Always treat that file as the shared source of truth for the Kanban board.
42
43## Required workflow
44
451. Read the task file before handling an actionable request.
462. If the file does not exist, create it with the schema in this document.
473. If the latest user message is actionable and no matching active task exists, create one immediately.
484. Before starting execution, ensure the task is `todo` or move it to `in_progress`.
495. If work cannot continue, set the task to `blocked` and record a short reason in `notes`.
506. When work is finished, set the task to `done`.
517. When work needs user review or confirmation, set the task to `review`.
528. After every mutation, write the full updated JSON back to disk.
53
54## Matching rules
55
56- Match first by `externalThreadId` when the request comes from a stable thread or conversation.
57- Otherwise match by a concise normalized title that preserves user intent.
58- Avoid creating duplicate active tasks for the same request.
59
60## Task fields
61
62Each task must include:
63
64- `id`
65- `title`
66- `description`
67- `status`
68- `source`
69- `sourceEventId`
70- `assignedAgentId`
71- `createdAt`
72- `updatedAt`
73- `playbookJobId`
74- `runId`
75- `channel`
76- `externalThreadId`
77- `lastActivityAt`
78- `notes`
79- `isArchived`
80- `isInferred`
81- `history`
82
83## Status rules
84
85- New actionable requests start as `todo` unless work has already begun.
86- Move to `in_progress` when the agent is actively working.
87- Move to `blocked` when progress depends on missing input, credentials, approvals, or failures.
88- Move to `review` when the work is ready for inspection or handoff.
89- Move to `done` only when the requested work is complete.
90
91## File format
92
93```json
94{
95 "schemaVersion": 1,
96 "updatedAt": "2026-03-30T00:00:00.000Z",
97 "tasks": [
98 {
99 "id": "research-mtulsa-com",
100 "title": "Research mtulsa.com",
101 "description": "Review mtulsa.com and summarize the site, positioning, and improvement opportunities.",
102 "status": "in_progress",
103 "source": "claw3d_manual",
104 "sourceEventId": null,
105 "assignedAgentId": "main",
106 "createdAt": "2026-03-30T00:00:00.000Z",
107 "updatedAt": "2026-03-30T00:10:00.000Z",
108 "playbookJobId": null,
109 "runId": null,
110 "channel": "telegram",
111 "externalThreadId": "telegram:direct:6866695577",
112 "lastActivityAt": "2026-03-30T00:10:00.000Z",
113 "notes": [],
114 "isArchived": false,
115 "isInferred": false,
116 "history": [
117 {
118 "at": "2026-03-30T00:00:00.000Z",
119 "type": "created",
120 "note": "Task created.",
121 "fromStatus": null,
122 "toStatus": "todo"
123 },
124 {
125 "at": "2026-03-30T00:10:00.000Z",
126 "type": "status_changed",
127 "note": null,
128 "fromStatus": "todo",
129 "toStatus": "in_progress"
130 }
131 ]
132 }
133 ]
134}
135```
136
137## Response rules
138
139- Briefly confirm which task was created or updated.
140- If the request is ambiguous, ask a clarifying question instead of guessing.
141- Do not claim work is complete without updating the task status.
iamlukethedev