handover

Generate HANDOVER.md files with decisions, pitfalls, lessons, and next actions.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ebal5/agent-skills --skill handover-ebal5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/ebal5/agent-skills/tree/main/skills/handover
Command: npx skills add https://github.com/ebal5/agent-skills --skill handover-ebal5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

セッション終了時やコンパクト前に、セッションの要約をHANDOVER.mdに保存し、決定事項、落とし穴、学んだ教訓、次のアクションを記録して次回へスムーズに引き継ぐことを可能にします。 また、セッションで得た知見からHANDOVER.mdの改善案やCLAUDE.mdの更新点を提案します。

Core Features & Use Cases

  • セッション内容を要約して HANDOVER.md を作成
  • 決定事項・教訓・未解決タスクを構造化して次回へ持ち越す
  • HANDOVER.md から次の作業計画を抽出してCLAUDEの改善点を提案

Quick Start

Summarize the current session and save it to HANDOVER.md with decisions, pitfalls, lessons learned, and next actions.

Frequently Asked Questions about handover

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

FAQPage Schema
How do I document a session handover to preserve context for the next workflow?

Session handover synthesis automates the creation of a HANDOVER.md file that records decisions, pitfalls, lessons learned, and next actions to seamlessly guide the next session.

What is the best way to create a structured knowledge transfer record before a context compact?

The best way to create a knowledge transfer record before a compact is to synthesize the active session context, branch state, and actionable tasks into a structured HANDOVER.md file.

How do I extract next actions and improvement proposals from a session handover document?

You extract next actions and improvement proposals by analyzing the generated HANDOVER.md to identify structural updates and potential improvements for the CLAUDE.md configuration.

Does session handover documentation automatically prevent sensitive data leakage in the generated files?

Session handover documentation satisfies requirements for avoiding sensitive data leakage while structuring context, branch state, and actionable tasks in the generated HANDOVER.md file.

Can I use automated handover synthesis for end-of-session wrap-ups without manual formatting?

Yes, automated handover synthesis supports end-of-session wrap-ups and pre-compact handovers by structuring decisions and lessons learned into a HANDOVER.md file without manual formatting.

When do I need to generate a HANDOVER.md file for my workflow?

You need to generate a HANDOVER.md file during end-of-session wrap-ups or before context compaction to create a structured record of decisions, pitfalls, and actionable tasks for the next session.