Generate a session handover document that captures progress, decisions, and context for seamless session continuity. This documentation shall serve Agents and Humans when working in consecutive sessions with the project. Use this skill at the end of a work session or when context transfer to a new session is needed.
This documentation shall serve Agents and Humans when working in consecutive sessions with the project.
Creates a session handover document (plans/<name>/handovers/session-<date>.md) that captures everything a new session needs to continue work seamlessly:
Do NOT generate handovers automatically. This skill is invoked manually by the user.
plans/<name>/handovers/.git status/git diff --stat interpretation or bulk file listing to doc-explorer, but keep narrative/decisions in the primary.Determine what to capture:
plans/ directoryplan.md and todo.mdCollect from the current session context:
Progress:
Decisions:
Implementation State:
git diff --stat or git statusIssues:
Create plans/<name>/handovers/session-<YYYY-MM-DD>.md:
If multiple handovers on the same day, append a counter: session-2025-02-14-2.md.
Fill in all sections from the template:
After creating the handover:
todo.md reflects the actual current stateUse the question tool to ask:
If there is no formal plan but a handover is needed:
docs/handovers/session-<date>.md (in the docs directory instead of plans)src/auth/refresh.ts, starting from the rotateToken function stub" is actionable.todo.md for task status. The handover captures session context (decisions, state, blockers), not a repeat of the task list.git status and git diff --stat to identify modified files rather than relying on memory.todo.md in Step 4, make simple status changes directly. For complex plan restructuring, the update-plan skill should be used instead.This skill includes a normative template as a bundled file. Only read the templates when processing them. Output MUST follow the template headings and frontmatter keys:
tpl-session-handover.md - Structure for handover documents