Skip to content
SkillModel-led761 tokens in use

Handover

Write the one note a fresh agent session starts from, after checking the disk, the running jobs and git against what the session remembers.

680 stars on the repository MIT Licensephuryn/product-engineering · agent-harness/skills/handover
npx skills add phuryn/product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Handover costs

73tokens idle
761tokens in use
824tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure17/25
  • Examples9/15
  • Output5/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

Handover writes the note the next session reads first, when a session or its context is ending and work continues later or with another agent. You start it by name: /agent-harness:handover in Claude Code or $agent-harness:handover in Codex.

It first reconciles the session’s beliefs with reality: git status, the branch, background jobs and project state files. Then it writes objective, where things stand, evidence, work left, open decisions, locations and one concrete next action.

What You Get

  • A handover note with objective, current state, evidence, work left, open decisions, locations and a next action
  • State files corrected where the disk disagreed with them
  • A HANDOVER.md at the repository root when the project has no handover convention
  • The exact line to give the next session, plus a list of anything left running

Common Use Cases

  • Ending a long session before the context fills up
  • Passing work from one agent vendor to another
  • Pausing a build overnight with background jobs still running
  • Resuming a stage after a break with the evidence of what was run

What Makes It Unique

The note is built from what the disk and the processes show, with this session’s own memory treated as a claim to check. The evidence section records commands, exit codes and numbers, and says so when something is unverified. The next action must be a concrete command or file, never the word continue. The skill runs only when you name it, so it never fires by itself.

Under The Hood

The skill is a single instruction file with no scripts. When it runs, the agent runs shell and git commands such as git status to check the branch and uncommitted files, reads logs of background jobs, and writes or rewrites a handover file or the project’s status file in the repository. It fetches no web pages and calls no APIs, and it tells the agent to name where secrets are kept without copying them into the note.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers