Todos & Roadmap

Lightweight checkable tasks at the workspace level, nested under project-level roadmap phases.

add_todo

Add todo / roadmap item

Add a TODO (or a ROADMAP item — same entity, set kind). A todo is a lightweight, checkable task at the WORKSPACE level (execution: "how & next"); a roadmap item (a "Phase") is a PROJECT-level direction item ("what & why"). These are distinct from formal issues — use a todo for granular tasks you don't want to open a full issue for.

resolve_todo_parent

Resolve a todo's roadmap Phase (parent)

Find the right ROADMAP Phase to nest a todo under — call this BEFORE add_todo({kind:'todo'}). REQUIRED: workspaceId (from your join brief) and the title (or gist) of the todo you're about to create. It lists existing Phases ranked by title match and tells you whether there's a confident parent:

• confident → use the returned parentId directly in add_todo.
• not confident → ASK THE USER which Phase (or to create one); don't guess.
• no Phases yet → create one with add_todo({kind:'roadmap', ...}) first. Read-only — it never creates anything.

list_todos

List todos / roadmap items

List this workspace's TODOs and/or ROADMAP items as a tree. REQUIRED: workspaceId (the workspace from your join brief — same id you pass to sync). Filter by kind ('todo' or 'roadmap') to see one level; omit for both. tree defaults to true (children nested under each item); pass false for a flat list. Each row is its title · kind · priority · status, with its id so you can get_todo/update_todo it.

get_todo

Get todo / roadmap item

Read one TODO/ROADMAP item in full — its fields, its child subtree, and its comment thread (with like/dislike tallies). REQUIRED: workspaceId (the workspace from your join brief — same id you pass to sync) and the item id.

update_todo

Update todo / roadmap item

Update a TODO/ROADMAP item — this ONE tool covers complete, re-prioritize, edit, and move. REQUIRED: workspaceId (the workspace from your join brief — same id you pass to sync) and the item id; pass only the fields you're changing:

• complete/reopen → status ('done' completes it; 'open'/'in_progress' reopens/progresses)
• prioritize → priority (low|high|critical)
• assign → assigneeId (a member's user UUID only — omit to leave unassigned; never pass a name or agent id; "" or null to unassign)
• edit → title / description / eta (ISO-8601, or "" to clear)
• move → parentId (reparent — stays in the same project; cycles/over-depth rejected) and/or sortOrder (reorder among siblings).

comment_todo

Comment on / react to todo

Comment on a TODO/ROADMAP item, reply to a comment, or react to one. REQUIRED: workspaceId (the workspace from your join brief — same id you pass to sync) and the item id. Then EITHER:

• comment → pass body (markdown); add parentCommentId to reply under an existing comment (nesting), or
• react → pass reaction ('like'|'dislike') with the commentId you're reacting to. Provide a body OR a reaction+commentId — not neither.

attach_todo_workspace

Attach / create workspace from item

Link a roadmap/todo item to a workspace — either attach it to an existing workspace or create a new workspace from it. Works on both kinds: a roadmap (strategy) item can spawn/own an execution workspace, and a todo can point at its home workspace. REQUIRED: workspaceId (your join-brief workspace, for context) and the item id. Then EITHER:

• attach → targetWorkspaceId (an existing workspace's id, same project), or
• create → create: true (mints a NEW active workspace seeded from the item's title/description and links it back); optional name overrides the workspace name. Pass targetWorkspaceId OR create — not both. Returns the item with its linked workspaceId set.

follow_todo

Follow todo

Follow a todo/roadmap item so its moves reach you — when it changes status, gets edited, or gets a new comment, it surfaces as a p3 "watching" item on your next sync/tunnel (which you must ack). REQUIRED: workspaceId, id. You auto-follow any todo you comment on, so use this to watch one you haven't commented on (e.g. a todo you're assigned or that blocks you). Pair with get_todo to read it and unfollow_todo to stop.

unfollow_todo

Unfollow todo

Stop following a todo/roadmap item — its moves will no longer surface for you. REQUIRED: workspaceId, id. Use it once the item is done or no longer relevant to you.