handover-writer

Capture session state into a structured Markdown handover document.

6|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill handover-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handover-writer
Source: https://github.com/anotherben/claude-harness/tree/main/skills/handover-writer
Command: npx skills add https://github.com/anotherben/claude-harness --skill handover-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This handover writer generates a structured handover document that preserves all essential session context, completion status, and next steps to enable a fresh session to continue work without ambiguity.

Core Features & Use Cases

  • Generate a comprehensive handover with what was done, what remains, critical context, and exact next steps.
  • Capture the current Git state (branch, last commit, changes) and the workspace info to ensure accurate resumption.
  • Save to a standardized location (docs/handovers/YYYY-MM-DD-<task-slug>.md) and reference it in MEMORY.md and relevant knowledge graphs.

Quick Start

Run handover-writer to create a new handover document when you approach session limits or need to pause a task.

Frequently Asked Questions about handover-writer

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

FAQPage Schema
How do I preserve context when a git workflow session approaches context limits?

To preserve context at session boundaries, a handover document captures all relevant state, completion status, and next steps. It records the current git branch, last commit, and workspace info, ensuring a fresh session resumes work without ambiguity.

What is the best way to document session handovers for paused development tasks?

The best way to document session handovers is generating a structured Markdown file at docs/handovers/YYYY-MM-DD-<task-slug>.md. This document details what was done, what remains, critical context, and exact next steps for accurate resumption.

How do I create a structured handover document that updates my knowledge graph?

Creating a structured handover document involves capturing session state and optionally recording decisions or notes for the knowledge graph. It simultaneously updates MEMORY.md and ties the captured context to the current worktree and last commit.

When should I generate a handover document for my coding session?

You should generate a handover document when a task is paused, context is nearing limits, or you explicitly request a handover. This ensures seamless continuation across sessions by saving standardized workspace and git state information.

Does the handover writer work with my current git branch and worktree?

Yes, the handover writer captures the current git branch, worktree, and last commit to ensure accurate resumption. It ties all preserved session context and next steps directly to this active workspace state.

Can I use handover documents to resume work across different sessions?

Yes, handover documents enable a fresh session to continue work without ambiguity. By referencing the generated Markdown file and updated MEMORY.md, the new session immediately retrieves what was done, what remains, and exact next steps.