knowledge-context-session-handover

What problem does it solve? When a work session ends or is interrupted, context about progress, decisions, and blockers is lost, forcing the next session or agent to re-derive everything. This Skill captures that context in a structured handover document so work resumes without re-litigating settled decisions. ## Core Features & Use Cases - Structured handover template: Fills a fixed template covering summary, progress, key decisions with rationale, modified files, blockers, and ordered next steps. - Git-grounded state capture: Derives the changed-file list from git status and git diff --stat rather than memory, and notes uncommitted changes and pending tests. - Plan-aware placement: Writes handovers under an active plan's handover area or a standalone docs/handovers/ path, with dated filenames that are never overwritten. - Use Case: Before ending a session mid-way through an auth refactor, ask for a handover; the next session reads session-2024-06-01.md and immediately knows the JWT rotation decision, which files changed, and the exact next step. ## Quick Start Ask the agent to create a session handover capturing where we left off before ending this work session.