Generate a handoff prompt to pass context to another agent thread. Use when switching repos, handing off work, or sharing context between agents.
From jbarson-skillsnpx claudepluginhub jbarson/jbarson-claude-skills --plugin jbarson-skills/handoffGenerates structured Markdown handoff document with git status, session progress, learnings, files touched, and resume instructions for another Claude session. Supports --full and --compact modes.
/handoffEnds swarm session: summarizes work/blockers, persists state via hivemind_store and git, cleans agents/tasks/reservations, updates hive, generates handoff note.
/handoffGenerates a developer handoff package for the specified screen, feature, or component, including visual specs, interaction specs, QA checklist, assets, and notes.
/handoffSaves session state snapshot as structured JSON to docs/tasks/<branch>/session_logs/<timestamp>_handoff.json, capturing git status, progress summary, tasks, and context for resume.
/handoffCreates a detailed handoff plan summarizing conversation, technical details, code, decisions, and next steps for continuing work in a new session.
/handoffCreates handoff branch from main, scratchpad with analysis/plan/files/testing, PR, roadmap entry, and copy-paste worker prompt for task delegation.
Generate a structured prompt capturing the current conversation context so it can be pasted into another agent thread.
$ARGUMENTS - Optional: specific instructions about what to emphasize or who the target isgit rev-parse --show-toplevel 2>/dev/null | grep -oE '[^/]+$' | head -1git branch --show-currentgit log origin/HEAD..HEAD --oneline 2>/dev/null | head -15git status --short 2>/dev/null | head -20git diff --name-only origin/HEAD..HEAD 2>/dev/null | head -30Review the full conversation history and synthesize a handoff prompt. Use this format, omitting empty sections:
## Handoff: [brief title]
### Background
[1-3 sentences on what was being worked on and why]
### What Was Done
- [Completed work with specific file paths]
### Current State
[Branch state, what is working, what is not]
### Key Decisions
- [Decision]: [Rationale]
### Remaining Work
- [ ] [Specific actionable items]
### Important Context
- [Gotchas, constraints, or patterns the next agent needs]
- [Specific file paths, function names, code patterns]
### Files to Read First
- [Ordered list of files to get up to speed]
Keep it concise but complete enough that the receiving agent can continue without re-discovering context.
Print the handoff inside a fenced code block so the user can copy it.