Skill · Slash command

Hand Off to Your Next Session

A slash command that turns a session into a note the next one can pick up cold.

TypeSlash command

The session ends — context runs out, the day ends, you switch machines. Tomorrow a fresh session opens with no memory of any of it. So you spend the first twenty minutes re-explaining what you were doing, what already works, and what you were about to try — reconstructing, from your own fading memory, the state the last session knew perfectly.

An agent's session is disposable; the state it built up is not. The fix is to spend the last thirty seconds of a session capturing that state, so the next one starts from it instead of from scratch. Make it a command, so you never have to remember to:

✕ Without the command

Session ends, the context is gone with it

▼

Next session opens blind

▼

Twenty minutes re-deriving where you were

✓ With the command

One command dumps the state in thirty seconds

▼

Next session reads it cold

▼

Picks up exactly where this one stopped

Save it under .claude/commands/ and run it before you close a session — or before the context compacts. It's worth the most exactly when work spans more than one sitting: the long migration, the multi-day feature, the thing you hand to someone else. Keep the note short enough to read in one breath — state, not narration.

Save under .claude/commands/

---
description: Summarize this session into a handover note for the next one
---
Write a concise handover note for whoever picks this up next — a fresh session, or someone else:
- **Done**: what changed this session, in a line or two.
- **State**: what works now, and what is half-finished.
- **Next**: the single next action, concretely.
- **Gotchas**: anything that will trip up the next session.
Keep it short enough to read in thirty seconds. State, not narration — skip the thought process.

Prefer your agent install it?

Add this rule to my CLAUDE.md, verbatim:

---
description: Summarize this session into a handover note for the next one
---
Write a concise handover note for whoever picks this up next — a fresh session, or someone else:
- **Done**: what changed this session, in a line or two.
- **State**: what works now, and what is half-finished.
- **Next**: the single next action, concretely.
- **Gotchas**: anything that will trip up the next session.
Keep it short enough to read in thirty seconds. State, not narration — skip the thought process.

Did this help?

Tags#context #workflow #skill

Other skills

01Verify Before You Call It Done 02Plan First, Then Code 03Map the Blast Radius Before You Edit 04If It's Deterministic, Don't Make It Guess 05Diagnose From the Symptom, Not the Guess 06Make It Argue Against Its Own Plan 08A Review That Doesn't Rubber-Stamp 09Run to the gate, then stop — not step-by-step 10A CLAUDE.md skeleton — turn a description into operating law 11The weekly review prompt — five minutes that turn experience into skill 12Split the work into focused slices, each with clean context 13Is this even worth an agent — ask before you open the chat 14Probe with a small task before you trust it in a new domain

Back to skills

The author

Each story here wraps a lesson paid for in full.

craftagentsomeone building and learning at once

What are you building with agents? Want to trade notes, push back, or build something together — drop a line.

Write hello@craftagent.cloud

58pieces12clustersVI·ENbilingual

✕ Without the command

✓ With the command

Get new pieces by email