tasks

Files (19)

• SKILL.md
• handler.test.ts · tools/checkpoint/
• handler.ts · tools/checkpoint/
• tool.json · tools/checkpoint/
• handler.test.ts · tools/plan/
• handler.ts · tools/plan/
• tool.json · tools/plan/
• handler.test.ts · tools/task-complete/
• handler.ts · tools/task-complete/
• tool.json · tools/task-complete/
• handler.test.ts · tools/task-create/
• handler.ts · tools/task-create/
• tool.json · tools/task-create/
• handler.test.ts · tools/task-list/
• handler.ts · tools/task-list/
• tool.json · tools/task-list/
• handler.test.ts · tools/task-update/
• handler.ts · tools/task-update/
• tool.json · tools/task-update/

SKILL.md (first lines)

## Task Management

You can defer, track, and resume work using your task skills.

**Decide, don't drop.** When work arrives that you cannot finish now, create a
task (`task-create`, optionally with `wake_at`) rather than cramming it into one
burst or abandoning it. Briefly tell the principal what you queued and why.

**Own the how.** When a clear goal is too big for one burst, decompose it and start —
with a one-line heads-up. Do not ask the principal how to execute (splitting, scheduling,
budgets); ask only about the goal itself, or a consequential or hard-to-reverse action.

**Decompose projects.** If work has more than one step, or any step cannot be done
right now, create a parent task whose `intent_anchor` states the durable goal, plus
the first wave of subtasks (`parent_task_id`, and `blocked_by_task_id` for ordering).
Plan the first wave only; add subtasks as you learn more.

**Make every subtask self-contained.** A woken subtask starts fresh with no memory of this
conversation — it has only its id, title, intent, and progress note. So its
`intent_anchor` and progress must fully re-establish the work: the goal, the resource
(e.g. a URL), and precise progress ("answered Q1-12 of 60"). A bare title like "Answer
Q13-36" strands the wake. For **web-browser** work, also record the exact `session_id` and
whether the session was `incognito`, and resume it with the same `incognito` value.

**Advance until blocked.** When you act on a task, do every step you can right now.
Stop only at a real blocker — waiting on a person, on the principal's approval, on a future
date, or on a prior task — or when your turn budget runs low. Then park each loose end:
set its status (`waiting`/`blocked`), add a progress note, and set a wake (a reply you
are expecting, or a `wake_at` timer). When a task's goal is achieved, call `task-complete`
with a note.

**Never promise without a task.** Before you send anything that commits to a future
action ("I'll follow up with X", "we'll send that over"), make sure a task backs that
promise. Prefer to resolve the dependency first and send a complete message. Only send
an interim "I'll follow up" when the recipient needs an acknowledgment now — and when
you do, create the follow-up task (yours if you can chase it; the principal's if only they
can, and tell them).

From josephfung/curia, MIT.

More from josephfung/curia