session-handover

Maintain context continuity by generating a concise handover snapshot at session end that captures current focus, decisions, and next actions for the next instance. This prevents context loss and duplication of work.

Automate workflow state persistence by creating a lightweight, human-readable handover file at session boundaries. This file stores your current progress, ensuring rapid handovers and seamless continuity for multi-day developer tasks.

Create a handover document by ending your current session to automatically generate and store a snapshot at SESSION_HANDOVER.md. This file surfaces context at session start to minimize context switching.

Yes, a handover document prevents context loss during frequent session boundaries by capturing concise summaries of your current focus and next actions. It fits developer-centric workflows needing rapid handovers and collaboration.

You need session handover automation when managing multi-day tasks or collaboration that involves frequent session boundaries. It generates a concise snapshot at session end to ensure smooth transitions between instances.

No dependencies are required to generate session handover summaries. The skill operates independently to create a lightweight handover file located at SESSION_HANDOVER.md for quick review and continuity.