handofflisted

# handoff **English** | [中文](#中文) Long-running development in a single Claude Code conversation eventually runs into a wall: the context window fills, the session must move to another machine or person, or you simply want a clean restart that does not throw away everything you learned. This skill produces **two artifacts** that together let a *fresh* conversation continue as if nothing was lost: 1. a **HANDOFF DOCUMENT** — an exhaustive, evidence-backed snapshot of the work; and 2. a **CONTINUATION PROMPT** — a ready-to-paste opening message that puts the new conversation into a disciplined "goal mode" aimed at a mergeable, community-grade result. The goal is *faithful transfer*, not a highlight reel. A good handoff lets a stranger (or a future you with an empty context window) rebuild the same mental model in minutes and take the next correct step without re-deriving it. ## When to use it - The conversation is long and context is close to full. - You are about to `/clear`, restart, or move to another session/host/person. - A task is paused and will be resumed later. - You want a durable checkpoint you can commit to the repo. ## What to produce Fill `templates/HANDOFF_TEMPLATE.md`. Every section must be answered from the actual conversation and repository state — never invented. If a section is empty, write `None` and say why, rather than leaving a blank that a reader will misinterpret as "unknown". The document must cover, in order: 1. **Objective & success c