handoff

Generate a structured conversation summary and respawn Claude with preserved context.

2|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/badri/wt --skill handoff-badri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/badri/wt/tree/main/examples/handoff-skill
Command: npx skills add https://github.com/badri/wt --skill handoff-badri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides Claude conversations through a structured handoff to a fresh session while preserving context, ensuring seamless continuity when a discussion becomes long or a session ends.

Core Features & Use Cases

  • Generate a concise, structured summary of the current conversation.
  • Invoke wt handoff with the generated summary to preserve context.
  • Respawn a new Claude session that continues with the preserved context.
  • Ideal for long-running threads, end-of-session handoffs, or context-renewal across sessions.

Quick Start

Invoke the /handoff action in Claude Code, then provide a SUMMARY via wt handoff -m "SUMMARY: ...". The handoff data is stored at ~/.config/wt/handoff.md and a fresh Claude session is started with the preserved context.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I preserve context when starting a fresh Claude session?

To preserve context in a fresh Claude session, you can use the handoff action to generate a structured conversation summary and respawn Claude with the preserved context stored at ~/.config/wt/handoff.md.

What is the best way to continue a long-running Claude thread without losing context?

The best way to continue a long-running Claude thread is to trigger a context renewal via handoff, which creates a concise summary of the ongoing conversation and automatically starts a new session with that context.

How do I hand off an ongoing Claude conversation before ending a work session?

You can hand off an ongoing conversation by invoking the /handoff command in Claude Code, which executes wt handoff with a generated summary to seamlessly transfer your session context.

Does the Claude conversation handoff process require any external dependencies?

No external dependencies are required for the Claude conversation handoff process, as it relies solely on the built-in wt workflow tool to manage the context preservation and session respawn.

Where is the preserved context data stored during a Claude session handoff?

During a Claude session handoff, the preserved context data is stored locally as a structured markdown file at the ~/.config/wt/handoff.md file path for the new session to access.

When should I use a context handoff instead of continuing a single Claude thread?

You should use a context handoff when a discussion becomes long-running, when you need to end a work session, or when the existing context needs renewal to maintain seamless continuity across sessions.