Writes a structured end-of-session handover as a session.handover LogEntry — capturing current state, open threads, next recommended action, and git context — so the next session can resume without losing track. Use when the user says "write a handover", "prepare for shutdown", "save context before closing", or when a container restart is imminent.
A session handover is a structured snapshot written at the end of a work
session — before a container restarts, a laptop closes, or a context window
ends. It is the primary mechanism for continuity across sessions. The
handover is a session.handover LogEntry, not a flat Markdown file: it
lives in context/logs/ and is queryable by any downstream skill.
Two trigger patterns exist — both are valid:
Pattern A — container restart / shutdown handover The user is about to stop the container or close the session and wants the next session to pick up exactly where this one left off. This is the primary use case. The handover may be read days or weeks later.
Pattern B — regular evening cadence
The user writes a handover at the end of every work session as a habit.
morning-briefing reads the most recent handover and weights it by age:
a same-day handover is the primary "what happened" source; an old handover
is context only.
Both patterns use identical handover content. The difference is only in how frequently the skill is invoked.
Work through these sections before writing the entry:
1. Current state (2–4 sentences) What is the overall state of the project right now? What was the last significant thing completed? Is the codebase in a clean, broken, or in-flight state?
2. Open threads
Every item that is in-progress, blocked, or needs a decision. Query
workitem-management for state: in_progress and state: blocked items.
Include informal threads that are not yet WorkItems — anything the next
session needs to know about.
3. Next recommended action The single most important thing the next session should do first. Be