Skip to content

Task Assign Directions

How to assign a task — presentation format, completion tracking, state change protocol

When to use

user runs /wb-task-assign or asks to assign a task to the current session

Slash command: /wb-task-assign

  • tasks/task_assign
  • tasks/task_change_state

Directions

Assign via mcp__work-buddy__wb_run("task_assign", {"task_id": "<id>"}). Do NOT use Python code.

If no argument provided, ask for the task ID.

Presentation after assignment

  1. Task: text and current state/urgency
  2. Contract: which contract it serves (if any)
  3. Note: preview of note content (if exists) + file path
  4. Sessions: how many sessions have worked on this task

State

Task state is NOT changed by assignment. To mark focused, use task_change_state separately.

Completion tracking

After committing code (or completing the deliverable), proactively ask: "Task looks complete -- should I mark it done?"

On approval: mcp__work-buddy__wb_run("task_change_state", {"task_id": "<id>", "state": "done"})

Do not silently mark the task done -- always confirm first.