handing-off

Write a handoff document so a fresh agent can continue the work without re-loading the entire conversation.

When to use

• Context is approaching its limit and the work isn't done.
• The next stage requires a different agent (different model, different tools, different scope) or a human.
• Wrapping up a session at the end of the day with work in flight.
• The user invokes /handing-off [focus] explicitly.

How to write the doc

1. Summarize, don't duplicate. Reference commits (<sha> — <message>), files (path:line), PRs, issues, ADRs, plans. The next agent can git log, Read, gh their way to detail. The doc carries the why and where things stand, not the contents.
2. Lead with state. What's done, what's in flight, what's blocked, what's next. Use bullet lists, not paragraphs.
3. Name suggested skills. If the next session should reach for reviewing-code, updating-lockstep, etc., list them by name with a one-line "use when" so the next agent doesn't have to discover them.
4. Tailor to the focus. If the user passed an argument (/handing-off SEA migration), shape the doc around that scope; drop unrelated work into a "deferred" section.
5. Stop at one screen. A handoff doc that takes longer to read than the work it summarizes has failed at its job.