Task Handoff Directions¶

How to write a structured session handoff prompt and package it as native task knowledge.

When to use¶

user wants to hand off in-progress work to a new agent session via a task

Slash command: /wb-task-handoff

tasks/task_create

Directions¶

Create a native task with a comprehensive handoff prompt in its Co-work knowledge document.

Write the handoff prompt¶

Consolidate into these exact sections:

This is a handoff prompt from session {WORK_BUDDY_SESSION_ID}.

Task -- What needs to be done. One concrete paragraph.¶

Context -- Why this exists. Motivation without needing to ask.¶

What I Already Know -- Decisions, approaches tried/abandoned, edge cases, constraints. Highest-value section.¶

Key Files -- Absolute paths with brief annotations.¶

System Notes -- Non-obvious environmental knowledge. Skip if nothing applies.¶

Suggested Approach -- If you have a clear idea. Omit if not.¶

Be specific. File paths absolute. Decisions include rationale.

Create the task¶

mcp__work-buddy__wb_run("task_create", {"task_text": "<concise summary>", "summary": "<full handoff prompt>"})

The summary parameter provisions the Co-work document. task_create carries a stable mutation ID, so a response-loss retry through the gateway replays the same native task instead of creating a duplicate. Do not use obsidian_retry.

Confirm¶

Show: task ID, brief summary, remind about /wb-task-assign .