create-handoff

Save current task, progress, decisions, modified files, and next steps to a handoff file.

41|3|Updated Jan 12, 2026

Search Tags:#workflow #context #resume #handoff #session #claude-code #save-state

Ready to run

npx skills add https://github.com/darkroomengineering/cc-settings --skill create-handoff-darkroomengineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-handoff
Source: https://github.com/darkroomengineering/cc-settings/tree/main/skills/create-handoff
Command: npx skills add https://github.com/darkroomengineering/cc-settings --skill create-handoff-darkroomengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save session state to enable seamless resumption of work.

Core Features & Use Cases

Save the current task, progress, decisions, modified files, next steps, contextual information, and learnings to a handoff file for later resumption.
Store handoffs in the standard ~/.claude/handoffs/ directory with a timestamped filename to avoid conflicts.

Quick Start

Create a handoff for the current session by running the handoff command to save the session state.

Frequently Asked Questions about create-handoff

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

FAQPage Schema

How do I save my Claude Code session state for later resumption?▼

To save your Claude Code session state, run the handoff command to capture the current task, progress, decisions, modified files, next steps, and learnings into a timestamped file for seamless later resumption.

What is the best way to preserve context when switching between coding tasks?▼

Preserving context during task switches requires saving your current progress and decisions to a handoff file. This captures modified files and next steps, enabling you to resume work later without losing contextual information.

Where are session handoff files stored on my system?▼

Session handoff files are stored in the standard ~/.claude/handoffs/ directory. The files use a timestamped naming convention to prevent conflicts when multiple handoffs are saved during different sessions.

When should I create a session handoff during my workflow?▼

You should create a session handoff during end-of-session, breaks, or context-switch scenarios. Saving your progress at these points ensures you can seamlessly resume work without losing track of decisions and modified files.

Can I resume a coding session after closing the terminal?▼

Yes, you can resume a coding session after closing the terminal if you saved a handoff file beforehand. The handoff preserves your task, progress, and next steps, allowing you to pick up exactly where you left off.

Does creating a handoff require any external dependencies or components?▼

No, creating a handoff requires no external dependencies or components. It independently saves your current session state directly to the local filesystem for later resumption.