handover

Merge session context into HANDOVER.md with decisions, lessons, and project state.

Updated Dec 22, 2025

Search Tags:#documentation #handover #knowledge-management #session-context #project-state #lessons-learned

Ready to run

npx skills add https://github.com/senior-sigan/llm-skills --skill handover-senior-sigan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/senior-sigan/llm-skills/tree/main/skills/handover
Command: npx skills add https://github.com/senior-sigan/llm-skills --skill handover-senior-sigan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Saves and merges session context into HANDOVER.md to preserve decisions, lessons, rules, and project state for future sessions.

Core Features & Use Cases

Auto-merges current session notes into HANDOVER.md, preserving prior content.
Aggregates decisions, lessons, and rules with project state for continuity.
Provides a ready reference for next-session context and onboarding.

Quick Start

Create or update HANDOVER.md with the latest session context and lessons from tasks/lessons.md.

Frequently Asked Questions about handover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I preserve session context and project state for future sessions?▼

The handover process automates saving session context by merging current decisions, lessons, rules, and project state into a HANDOVER.md file, ensuring continuity across future sessions and tasks.

What is the best way to manage knowledge and lessons learned across multiple tasks?▼

Managing lessons learned is achieved by aggregating decisions and rules from task notes, merging new data with existing HANDOVER.md to maintain a single source of truth for project continuity.

Does saving session context overwrite previous project documentation?▼

Saving session context auto-merges current notes into HANDOVER.md while preserving prior content and existing references, ensuring previous project documentation remains intact.

How do I onboard new sessions with existing project decisions and rules?▼

Onboard new sessions by using HANDOVER.md as a ready reference, which consolidates prior decisions, rules, and lessons learned to establish project context and ensure continuity.

When do I need to update my session context for project continuity?▼

Update session context when current tasks generate new decisions or lessons, triggering a merge into HANDOVER.md to maintain an accurate project state for future use.

Are there limitations to using a single markdown file for knowledge management?▼

A single markdown file for knowledge management relies entirely on HANDOVER.md, requiring consistent merging to prevent scattered task notes and lost decisions across sessions.