Skip to main content
skill CX Codex

handover · phuryn — Claude Code skill: what it does and how to install

This Claude Code skill writes a handover for the next agent session. It checks the project against the files on disk and records verified facts, unfinished work, and a concrete next step.

MIT ★ 741 updated 2026-11-14

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/product-engineering
/plugin install agent-harness@product-engineering
Open on GitHub

What handover does

handover prepares a note for the agent session that picks up the work. Before writing, it checks git status, the branch, commits, and changed files, then checks any background jobs the session started. It also corrects project status files when they conflict with the actual state.

The note covers the objective, current state, observed command results and exit codes, remaining tasks, open decisions, and one specific first action. The skill follows the project’s existing handover format; if there is none, it rewrites HANDOVER.md at the repository root. Secrets stay out of the note: it can name where they are kept, but not include keys or passwords.

For work spanning hours, multiple sessions, or background jobs, the instructions point to the flight-deck skill, its status board, and its log.

What it helps with

  • hand the next session a verified project state
  • record uncommitted changes and running processes
  • preserve command results and exit codes
  • turn remaining work into concrete next actions

Example prompts for the agent

  • Create a handover for the next session after checking the project state against disk.
  • /agent-harness:handover — the next session will finish the billing stage.
  • $agent-harness:handover — record verified results and the first action.

How to install handover

1Plugin marketplace

/plugin marketplace add phuryn/product-engineering
/plugin install agent-harness@product-engineering

This installs the whole agent-harness plugin with all its skills

2Skills CLI (Vercel)

npx skills add phuryn/product-engineering --skill handover -a claude-code

3Manually: put the files in place

~/.claude/skills/handover/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/handover/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about handover

How do I install handover in Claude Code?

Add the marketplace with /plugin marketplace add phuryn/product-engineering, then install the plugin with /plugin install agent-harness@product-engineering.

What does handover do?

It checks the project’s current state and writes a note for the next agent session, covering verified work, outstanding tasks, decisions, and where to begin.

What does handover record about tests and commands?

It records what was actually run and observed, including the command and its exit code. Unverified details are marked as such.

Source text

SKILL.md · MIT
---
name: handover
description: "Write the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what is left, the open decisions and the next concrete action, reconciled with the disk first. Started by name only: /agent-harness:handover in Claude Code, $agent-harness:handover in Codex."
argument-hint: "<optional: what the next session will do>"
disable-model-invocation: true
---

# Handover — what the next session starts from

**Write the one note the next session reads first.** The session is ending, or its context is; work continues tomorrow, in a fresh session, or with another agent. Start that session from what is true rather than what this session remembers.

## Invocation

```
/agent-harness:handover                          Claude Code, plugin installed
/agent-harness:handover the next session finishes the billing stage
$agent-harness:handover                          Codex, plugin installed
/handover   ·   $handover                        the skill folder copied into a repository
```

## Steps

### 1. Reconcile with reality first

**Check what this session believes against reality before writing a word.**

- **Check the disk and name uncommitted work as uncommitted.** Read `git status`, the branch, commits made this session, and files the work touched.
- **Check every background job, server, watcher and build this session started.** Each is still running, finished with its exit code read from its log, or gone.
- **Correct project state files where the disk contradicts them.** Check the plan's status, status board, backlog and earlier handover; correct those lines rather than copying them.

**An inherited report is a claim, this session's own memory included.**

### 2. Write what the next session needs

| Section | Holds |
|---|---|
| Objective | what the work is for, in a line, and who asked |
| Where it stands | what is true now: built, committed, pushed, deployed, each said plainly |
| Evidence | what was actually run and observed: the command, its exit code, the number, the verdict. Not what was intended. Anything unverified says so |
| Left to do | in order, each small enough to start on |
| Open decisions | each with its options, a recommendation, and whose decision it is |
| Where things are | branches, worktrees, files, logs, URLs, processes still running and how to stop them |
| Next action | one concrete first step: a command to run, a file to open. Never "continue" |

**Keep it short enough to stay true, preserving the evidence.** Evidence costs most to lose. A re-run experiment costs money; restating a number from memory is how a wrong one reaches the owner.

### 3. Put it where the project keeps such things

**Use the project's own handover convention before creating a new file.** Use its status board, plan's status lines or existing handoff file. With none, keep one `HANDOVER.md` at the repository root, rewritten in place each time. It says what is true now, not the history.

**Use the `flight-deck` skill for hours, multiple sessions or background jobs.** That work wants its status board and log instead of a single note. A few lines are enough for a short session.

**Name where secrets are kept without putting them in the handover.** No keys, tokens, passwords or connection strings.

### 4. Tell the owner how to start the next session

**End with the next session's starting line and anything left running.** For example: *Read `HANDOVER.md` and start from its next action.*

Each rule's origin, the case that taught it, is in `receipts.md` beside this file; read it when a rule's edge is unclear.

## How you can tell it worked

A fresh session given only the note can say what the work is for, what is verified and what is not, and run the next action without asking what happened.

© Paweł Huryn · MIT · phuryn/product-engineering

Similar skills

SKILL.md skills catalog →

handover by other authors comes first.

handover adobe Generates handover documentation for an AEM Edge Delivery Services project: separate guides for content authors, developers and site administrators. CX Codex +1 1,600installs handover Open-RUA The handover Claude Code skill transfers an object held by one robot hand to another. It is triggered for hand-to-hand transfers, not ordinary placement with a single arm. CX Codex +1 ★ 488repo stars handover-developer adobe handover-developer generates technical handover guides for AEM Edge Delivery Services codebases. Useful when onboarding engineers or documenting block architecture. CX Codex +1 773installs handover-admin adobe handover-admin is a Claude Code skill that creates admin documentation for AEM Edge Delivery Services projects. It runs for an admin handoff, a new site administrator’s onboarding, or procedure writing. CX Codex +1 770installs account-handover PostHog account-handover drafts structured handover briefings when transferring PostHog accounts between TAMs or CSMs. CX Codex +1 193installs seat-continuity-and-handover mvschwarz The seat-continuity-and-handover skill for Claude Code covers replacing an agent while keeping its seat identity stable. It separates creating a successor from binding it to the seat and recording the transition. CX Codex +1 ★ 8,928repo stars find-skills vercel-labs find-skills is a Claude Code skill that locates agent skills for a task and helps assess the results. It activates when someone asks for a capability that may already be installable. CX Codex +1 4,400,000installs frontend-design official anthropics The frontend-design skill guides intentional visual design for new interfaces and redesigns. Use it when a generic generated UI is not enough. CX Codex +1 1,025,790installs agent-browser vercel-labs This Claude Code skill automates browser interaction for tasks like navigating sites, filling forms, and testing web apps. It also supports exploratory QA and Electron app automation. CX Codex +1 1,600,000installs design-taste-frontend Leonxlnx The design-taste-frontend Claude Code skill sets design rules and checks for websites. It activates for new pages, redesigns, and requests to fix a generic-looking site. CX Codex +1 802,600installs

From the same set51

The whole set →
market-segments The market-segments Claude Code skill identifies 3–5 customer segments and assesses how well a product fits each one. Run it to explore an audience or evaluate a new market. CX Codex +1 ★ 741repo stars intended-vs-implemented The intended-vs-implemented Claude Code skill checks whether code follows documented requirements and spots gaps in access control and data boundaries. It audits AI-built features for security and correctness issues. CX Codex +1 ★ 741repo stars value-proposition This Claude Code skill shapes a value proposition with a six-part JTBD structure. It covers a customer segment, its task, the current approach and alternatives. CX Codex +1 ★ 741repo stars competitor-analysis competitor-analysis — a Claude Code skill for mapping market rivals and product substitutes. It analyzes five direct competitors, flags functional gaps, and highlights strategic differentiation points. CX Codex +1 ★ 741repo stars growth-loops This Claude Code skill evaluates product growth loops. Ask it to compare viral sharing, referrals, collaboration, or user-generated content and map out an implementation plan. CX Codex +1 ★ 741repo stars beachhead-segment The beachhead-segment Claude Code skill scores candidate customer segments and selects a first market to pursue. It weighs customer pain, willingness to pay, winnable share and referral potential. CX Codex +1 ★ 741repo stars retro The retro Claude Code skill reviews session friction and turns verified causes into changes to the agent setup. Start it by name at the end of a session. CX Codex +1 ★ 741repo stars value-curve This Claude Code skill maps a product’s value curve for one customer segment. It compares key needs, competing offers and relative price. CX Codex +1 ★ 741repo stars

Project sponsors

Companies that keep this analytics open