handover

Generates a session handover document summarizing task state and next steps.

2|Updated Sep 25, 2011

Search Tags:#workflow #documentation #markdown #context #continuity #session #handover

One-click install

npx skills add https://github.com/pokutuna/dotfiles --skill handover-pokutuna

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: handover
Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/handover
Command: npx skills add https://github.com/pokutuna/dotfiles --skill handover-pokutuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends, context about decisions, errors, and remaining tasks is lost, forcing the next session to redo work or repeat mistakes. This Skill captures the current session state into a structured handover document saved in the working directory. ## Core Features & Use Cases - Timestamped Handover Files: Creates a Markdown file named HANDOVER-<timestamp>.md in the current working directory. - Structured Five-Section Format: Records task overview, current state, important discoveries, next steps, and context to preserve. - Use Case: Before ending a long debugging or refactoring session, invoke the Skill so the next session can resume immediately with full knowledge of completed work, failed approaches, and pending actions. ## Quick Start Ask the assistant to create a handover document for the current session so work can resume later.

Frequently Asked Questions about handover

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

FAQPage Schema

How do I create a handover document for the next session?▼

Invoke the handover Skill at the end of your session. It writes a timestamped Markdown file named HANDOVER-<yymmddThhmm>.md into the current working directory containing task status, discoveries, and next steps.

What should a session handover document include?▼

A handover document should include the task overview and success criteria, completed work with file paths, technical discoveries and failed approaches, concrete next steps with priorities, and user preferences or commitments to preserve.

Where is the handover file saved?▼

The file is saved in the current working directory with the name HANDOVER-<timestamp>.md, where the timestamp is generated using the date command in yymmddThhmm format.

When should I not use a handover document?▼

Skip it for trivial single-step tasks that complete within one session. The handover format is designed for multi-session work where context loss would cause duplicated effort or repeated mistakes.