handover
Generate a handover document for transferring work to another developer or spawning an async agent
Best use case
handover is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate a handover document for transferring work to another developer or spawning an async agent
Teams using handover should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/handover/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How handover Compares
| Feature / Agent | handover | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate a handover document for transferring work to another developer or spawning an async agent
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /handover - Generate Session Handover Document
Generate a handover document for transferring work to another developer or spawning an async agent.
## Usage
```bash
/handover # Standard handover
/handover "notes about current work" # With notes
/handover --agent-spawn "task desc" # For spawning agent
```
## Modes
### Standard Handover (default)
For transferring work to another human or resuming later:
- Current session health
- Task progress and todos
- Technical context
- Resumption instructions
### Agent Spawn Mode (`--agent-spawn`)
For passing context to spawned agents:
- Focused on task context
- Technical stack details
- Success criteria
- Files to modify
## Implementation
### Detect Mode
```bash
MODE="standard"
AGENT_TASK=""
NOTES="${1:-}"
if [[ "$1" == "--agent-spawn" ]]; then
MODE="agent"
AGENT_TASK="${2:-}"
shift 2
fi
```
### Generate Timestamp
```bash
TIMESTAMP=$(date +"%Y-%m-%d-%H-%M-%S")
DISPLAY_TIME=$(date +"%Y-%m-%d %H:%M:%S")
FILENAME="handover-${TIMESTAMP}.md"
PRIMARY_LOCATION="{{TOOL_DIR}}/session/${FILENAME}"
BACKUP_LOCATION="./${FILENAME}"
mkdir -p "{{TOOL_DIR}}/session"
```
### Standard Handover Content
```markdown
# Handover Document
**Generated**: ${DISPLAY_TIME}
**Session**: $(tmux display-message -p '#S' 2>/dev/null || echo 'unknown')
## Current Work
[Describe what you're working on]
## Task Progress
[List todos and completion status]
## Technical Context
**Current Branch**: $(git branch --show-current)
**Last Commit**: $(git log -1 --oneline)
**Modified Files**:
$(git status --short)
## Resumption Instructions
1. Review changes: git diff
2. Continue work on [specific task]
3. Test with: [test command]
## Notes
${NOTES}
```
### Agent Spawn Handover Content
```markdown
# Agent Handover - ${AGENT_TASK}
**Generated**: ${DISPLAY_TIME}
**Parent Session**: $(tmux display-message -p '#S' 2>/dev/null || echo 'unknown')
**Agent Task**: ${AGENT_TASK}
## Context Summary
**Current Work**: [What's in progress]
**Current Branch**: $(git branch --show-current)
**Last Commit**: $(git log -1 --oneline)
## Task Details
**Agent Mission**: ${AGENT_TASK}
**Requirements**:
- [List specific requirements]
- [What needs to be done]
**Success Criteria**:
- [How to know when done]
## Technical Context
**Stack**: [Technology stack]
**Key Files**:
$(git status --short)
**Modified Recently**:
$(git log --name-only -5 --oneline)
## Instructions for Agent
1. Review current implementation
2. Make specified changes
3. Add/update tests
4. Verify all tests pass
5. Commit with clear message
## References
**Documentation**: [Links to relevant docs]
**Related Work**: [Related PRs/issues]
```
### Save Document
```bash
# Generate appropriate content based on MODE
if [ "$MODE" = "agent" ]; then
# Generate agent handover content
CONTENT="[Agent handover content from above]"
else
# Generate standard handover content
CONTENT="[Standard handover content from above]"
fi
# Save to primary location
echo "$CONTENT" > "$PRIMARY_LOCATION"
# Save backup
echo "$CONTENT" > "$BACKUP_LOCATION"
echo "✅ Handover document generated"
echo ""
echo "Primary: $PRIMARY_LOCATION"
echo "Backup: $BACKUP_LOCATION"
echo ""
```
## Output Location
**Primary**: `{{TOOL_DIR}}/session/handover-{timestamp}.md`
**Backup**: `./handover-{timestamp}.md`
## Integration with spawn-agent
The `/spawn-agent` command automatically calls `/handover --agent-spawn` when `--with-handover` flag is used:
```bash
/spawn-agent codex "refactor auth" --with-handover
# Internally calls: /handover --agent-spawn "refactor auth"
# Copies handover to agent worktree as .agent-handover.md
```
## Notes
- Always uses programmatic timestamps (never manual)
- Saves to both primary and backup locations
- Agent mode focuses on task context, not session health
- Standard mode includes full session stateRelated Skills
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.
tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
test-ainb
Run tests for the ainb (agents-in-a-box) Rust workspace via a 5-layer strategy — unit, insta snapshot, mock-plugin compositing, real-plugin spawn, vhs recording. Wraps cargo + insta + vhs into one CLI. Use when Stevie says "/test-ainb", "test ainb", "run ainb tests", "snapshot <component>", "regenerate vhs tapes", or any phrasing about validating ainb test layers. The skill autodetects which ainb-tui worktree the cwd sits in and dispatches to scripts/run.sh.
sync-learnings
Sync user-level agent config changes back to toolkit repository (works for Claude, Codex, Copilot)