This is the executable version of a tip we already publish — write a handoff, not a summary. If you only read one thing here, read that; this does it for you.
/handoff finish wiring the Kafka audit eventsYou get a document written for the next to act on, not a recap for you to read. The argument matters: tell it what the next is for and the document is scoped to that.
What it does that a summary doesn’t
- Saves outside your . The file lands in your OS temp directory, so you don’t session notes by accident.
- Refuses to duplicate. If a decision already lives in a spec, an ADR, a commit or a diff, it references the path instead of restating it — so the document stays short enough to actually be read.
- Names the skills. It includes a “suggested skills” section telling the next session which skills to load.
Why not just /compact
/compact keeps the session alive but loses specifics — that trade-off is covered in compact and clear. A handoff is the right move when the work matters and you’re willing to spend one deliberate step to carry it cleanly into a fresh .
Worth knowing
- It’s user-invoked only — Claude won’t decide to hand off on its own.
- Do it before things degrade, not after. The document is only as good as the context still in the window.
- Installing gives you the whole set —
/teachand/grill-mearrive in the same .
Access
Public — no access request needed. It ships in ’s official marketplace, so there is no marketplace add step.