claude-codehandofflisted

# Handoff Hand the current work to a fresh background agent seeded with a summary of this conversation. The agent starts immediately in the current directory and returns control, so you can walk away and check on it later. Nothing is written to disk: the summary becomes the new agent's opening prompt. Use this to make backgrounding a natural next step, not a special ceremony. When the work is well-scoped and the user wants to step away or parallelize, offer the handoff. ## Write the Summary Synthesize the conversation into a prompt that lets an agent with zero prior context resume without asking questions. Cover: - **Goal**: what the work is trying to achieve, in one or two sentences. - **State**: what is done, what is in progress, what is untouched. - **Decisions**: choices already made and the reasoning, so the agent does not relitigate them. - **Next steps**: the concrete actions to take, in order. - **Anchors**: the branch, PR, issue, plan doc, or key files by path or URL. Point at these rather than restating them. - **Suggested skills**: a short list of skills the agent should invoke for this work (e.g. `pull-request:create`, `review:code`, a project skill). This is the biggest lever on whether the agent picks up your conventions. - **Constraints**: anything that would surprise a fresh agent, such as test commands, gotchas, or things not to touch. Keep it dense and specific. Do not duplicate content that already lives in an artifact (a plan, an ADR, an issue, a dif