session-handoff

To generate a session handoff document, request a handoff during your active task. The system produces a lightweight Markdown file capturing task-relevant continuity, including goals, touched artifacts, open questions, and suggested next-session prompts.

Session continuity preserves task-relevant context across agent transitions. You need a handoff during BLOCKED or IDLE transitions, or when transferring work to another session, ensuring the next agent receives goals, scope, and verification state without context loss.

Transfer open questions and operational notes by generating a structured Markdown handoff file. This document safely captures active contracts, decisions, risks, and blocker reasons while excluding raw logs and irrelevant conversation history.

A session handoff Markdown file does not store secrets, raw logs, full file contents, or irrelevant history. It avoids promoting sensitive durable memory by default, preserving only task-relevant continuity for safe operational handoffs.

The best way to preserve task context without durable memory is generating an on-demand Markdown handoff. It captures scope boundaries, verification states, and next-session prompts only when explicitly requested or required by approved workflow contracts.

Yes, you can use a handoff document for BLOCKED and IDLE transitions. It applies to these specific workflow states by capturing the blocker reason and suggested next-session prompt, ensuring seamless task transfer when work resumes.