skills.rest
tobyilee
tobyileeCOMMUNITY
Explore all skills by this author →
GitHub

handoff

Generate a timestamped markdown handoff document with file references and open questions.

24|6|Updated Mar 6, 2026
Search Tags:#workflow#documentation#handoff#session-management#claude-code#context-transfer
One-click install
npx skills add https://github.com/tobyilee/toby-plugins --skill handoff-tobyilee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/tobyilee/toby-plugins/tree/main/plugins/toby-session/skills/handoff
Command: npx skills add https://github.com/tobyilee/toby-plugins --skill handoff-tobyilee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill to write a forward-looking handoff document that prepares the NEXT Claude Code session to pick up where this one stops. The document is a hypothesis for the next session to verify, naming files and line numbers so the next session can confirm claims against live code.

Core Features & Use Cases

  • Generate a concise, state-based handoff that captures open work, decisions, and traps to avoid.
  • Reference targeted files and line numbers to guide the next session without re-explaining everything.
  • Produce a timestamped markdown handoff under .claude/reports/handoff for continuity across sessions.

Quick Start

Generate a forward-looking handoff document under .claude/reports/handoff with a timestamp.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer context between Claude Code sessions without re-explaining everything?▼

To transfer context between Claude Code sessions, generate a forward-looking handoff document that captures open work, decisions, and file references so the next session can resume immediately without re-explaining context.

What should a session handoff document include to help the next Claude Code session?▼

A session handoff document should include file references with line numbers, status summaries, decisions made, and open questions to guide the next Claude Code session in verifying claims against live code.

How do I create handoff documentation that references specific files and line numbers?▼

Create handoff documentation by generating a timestamped markdown file under .claude/reports/handoff that names targeted files and line numbers, allowing the next session to confirm claims against the live codebase.

When do I need to write a forward-looking handoff document for Claude Code?▼

You need a forward-looking handoff document when a Claude Code session is ending and you want the next session to pick up where you stopped, treating the document as a hypothesis for the next session to verify rather than a final plan.

Can I use handoff documentation to avoid losing workflow state across sessions?▼

Yes, handoff documentation captures workflow state including open work, decisions, and traps to avoid, producing a timestamped markdown report that ensures continuity across multiple Claude Code sessions.

What are the limitations of writing session handoff documents as implementation plans?▼

Writing session handoff documents as final implementation plans limits the next session because the document should instead be written as a hypothesis for the next session to verify against live code, preventing stale assumptions.

Related Skills

Explore More Content & Communication Skills→
Sh3rd3nSh3rd3n
3

pause

Save session context and stash modified files for future Claude Code sessions.

Community
Intermediate
robertgussrobertguss
103

handoff

Create structured Markdown session handoff documents with decisions and next steps.

Community
Basic
the-agency-aithe-agency-ai
39

Session Handoff

Generate session handoff files documenting progress, decisions, and pending issues.

Official
Basic
GongXLiangGongXLiang

remember

Generate a structured handoff note with state, next steps, and context.

Community
Basic