---
name: Handover
slug: handover-3
category: Automation
description: Handover captures current objective, active work, blockers, and verification so a new peer can take over safely. Use it before changing direction or resuming after a closed session.
github: "https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/handover"
language: Go
stars: 260
forks: 34
install: "npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/handover ~/.claude/skills/handover"
installs_to: ~/.claude/skills/handover
source_path: daemon-go/cli/assets/orchestrator/.agents/skills/handover/SKILL.md
collection_size: 17
category_size: 1648
collection_url: "https://dirskills.com/collections/prassanna-ravishankar/repowire"
added: 2026-09-02T05:20:19.334Z
last_synced: 2026-09-02T05:20:19.334Z
canonical_url: "https://dirskills.com/skills/handover-3"
---

# Handover

Handover captures current objective, active work, blockers, and verification so a new peer can take over safely. Use it before changing direction or resuming after a closed session.

**Install:**

```bash
npx degit https://github.com/prassanna-ravishankar/repowire/tree/main/daemon-go/cli/assets/orchestrator/.agents/skills/handover ~/.claude/skills/handover
```

## README

# Handover

Use handover when continuity matters more than chat transcript detail.

## Write a handover

Capture:

- Current objective and why it matters.
- Active lanes, owners, worktrees, and ask/job IDs.
- What is done, what is blocked, and the next decision.
- Verification already run and verification still needed.
- Anything the next peer must not touch.

Prefer links to durable surfaces over pasted logs: job IDs, ask IDs, branch names, issue IDs, and file paths.

## Read a handover

Before acting, verify live state:

```bash
repowire peer list
repowire jobs list
git status --short --branch
```

Assume handover notes can be stale. Reconcile them against the repo, jobs, and active peers before dispatching new work.

## Avoid

- Treating handover as memory.
- Copying entire transcripts.
- Continuing stale implementation after the user has rerouted work.