session-handoff

To document an agent session handoff, you capture the original goal, git state, completed work, decisions, and blockers into a durable markdown file. This persisted state allows a future agent or session to resume the multi-step task without context loss.

A git state snapshot for session handoff should include the current branch, repository status, last commit details, and any dirty files. Recording this exact git state alongside completed work and blockers ensures accurate continuity for the next agent.

You securely persist workflow documentation by writing the session handoff file to a durable path like docs/handoffs/YYYY-MM-DD-slug.md. The process enforces redaction of secrets from the handoff document and prevents automatic git commits unless explicitly requested.

Session handoff documentation does not automatically commit to your git repository by default. It only writes a durable file capturing your session state, requiring explicit user request to execute any git commits alongside the workflow handoff.

You need a compact session handoff document when working across multi-step tasks, long-running sessions, or agent collaboration. It preserves the original goals, decisions, and blockers in a concise file under 150 lines, linking to related issues and logs for depth.

Session handoff files are designed for long-running multi-step tasks to prevent context loss. By specifying the goal, git state, and blockers in a durable markdown file, another agent or future you can seamlessly resume the continuity of work.