handover

Generate a HANDOVER.md summarizing session work at .claude/HANDOVER.md.

Updated Aug 14, 2024
One-click install
npx skills add https://github.com/kokatsu/dotfiles --skill handover-kokatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/kokatsu/dotfiles/tree/main/.config/claude/skills/handover
Command: npx skills add https://github.com/kokatsu/dotfiles --skill handover-kokatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a concise HANDOVER.md that captures the current session's work to preserve context when you switch tasks or end a session.

Core Features & Use Cases

  • Generate a HANDOVER.md summarizing completed tasks, current progress, next steps, and key technical decisions.
  • Scan existing HANDOVER files under .claude/HANDOVER-*.md to inform the new summary.
  • Overwrite or create .claude/HANDOVER.md with a structured, ready-to-share document.

Quick Start

Run /handover to generate or update the HANDOVER.md with a concise summary of the current session.

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 when switching tasks with an AI assistant?

A handover summary preserves session context by capturing completed tasks, current progress, next steps, and key technical decisions into a structured HANDOVER.md file, ensuring seamless context recovery when work resumes.

How do I document my current progress and next steps for a development session?

Document current progress by generating a structured summary that records completed tasks, ongoing work, and next steps. This creates a ready-to-share document that captures the current session's technical decisions and problem-solving context.

Does generating a session handover document overwrite existing context files?

Generating a handover document overwrites the existing HANDOVER.md file at .claude/HANDOVER.md. It also scans existing HANDOVER-*.md files in the same directory to inform the new summary and preserve continuity.

When should I create a handover document for my workflow?

Create a handover document when switching tasks, ending a work session, or handing off progress to another developer. It applies across developer notes, project planning, and problem-solving sessions to maintain continuous context.

Can I maintain multiple handover files for different tasks or sessions?

You can maintain multiple session handover files using the HANDOVER-*.md naming convention. The generation process scans these existing files to inform the new summary, though the primary output always overwrites the single .claude/HANDOVER.md file.