Summarize an ongoing conversation and launch a fresh background agent to continue the work. The handoff includes the next focus, references to existing documents, and suggested skills, with sensitive information removed.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
claude-handoff summarizes an ongoing conversation and passes it to a fresh background agent so work can continue. It saves the summary in your operating system’s temporary directory and uses it as the new agent’s starting instructions. The summary includes suggested skills for the next agent. Rather than repeating information already recorded in specifications, plans, or other documents, it references them by path or URL.
Use it when you want another agent to take over during a conversation, or when the next session should focus on a narrower task. The new agent starts in the current working directory, allowing it to resume in the same workspace. It receives a descriptive name so you can distinguish it in the job list.
Your environment must support launching background agents with claude --bg. After launch, manage them with claude agents. Because the summary becomes instructions for another agent, API keys, passwords, personally identifiable information, and other sensitive details are removed before handoff.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Write a handoff summary of the current conversation so a fresh agent can continue the work. Save it to the temporary directory of the user's OS, then launch a background agent seeded with it as its prompt: claude --bg --name "<descriptive name>" -- "$(cat <summary file>)". Passing the file keeps the shell from running backticks or expanding $ in the summary. It starts in the current working directory and returns immediately; the user manages it with claude agents.
Always pass -n/--name with a descriptive name (e.g. --name "Fix login bug"); it sets the display name shown in the job list, session picker, and terminal title.
Include a "suggested skills" section in the summary, naming which skills the next agent should call the Skill tool for.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information, since the summary becomes the agent's prompt.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the summary accordingly.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
Clarify a project's business concepts and terminology through concrete scenarios and comparisons with code. Record agreed definitions in a glossary and document significant design trade-offs in ADRs, records explaining why a decision was made.