Skill

handoff

Compacts the current session into a handoff document so another agent or fresh session can continue the work. Use when handing off, transferring context, or starting a parallel agent.

developer-tools

npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skills

Popularity

Stars

Forks

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/frontend-skills:handoff What should the next session focus on?

User invocable

Model invocable

Inline context

Default effort

Argument hintWhat should the next session focus on?

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Create a concise handoff document for another agent/session to continue from here.

SKILL.md

69 lines · ~571 tokens

Similar Skills

handoff

Compacts the current conversation into a handoff document for a fresh agent to continue mid-task. Use when ending a session with work in progress.

handoff

456

Compacts the current conversation into a handoff document for another Claude Code agent to continue work. Saves to OS temp directory, redacts sensitive info, and references existing artifacts by path.

mattpocock-skills

code-handoff

Summarizes the current Claude Code conversation into a handoff document for another agent to continue work. Useful when context switching or passing tasks between agents.

python

Stats

LanguageShell

Stars30

Forks2

MaintenanceExcellent

Last CommitJun 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Handoff

Create a concise handoff document for another agent/session to continue from here.

When to Use

Use when the user wants to:

continue work in a fresh session

hand work to another agent

run a prototype or parallel line of work elsewhere

preserve actionable context without carrying the whole transcript

Procedure

Create a temp file:

handoff_file=$(mktemp -t handoff-XXXXXX.md)
cat "$handoff_file" >/dev/null

Write the handoff to that path.

Keep it compact. Do not duplicate artifacts already captured in PRDs, plans, ADRs, issues, commits, diffs, or docs. Reference them by path or URL.

If the user provided arguments, treat them as the next session focus and tailor the handoff around that work.

Redact sensitive information: API keys, passwords, tokens, secrets, personal data, customer data, and any other confidential values. Mention redaction only when it affects continuation.

Suggest skills the next session should use, if any.

Return only the handoff path plus a 1-2 sentence summary.

Handoff Template

# Handoff ## Next session focus <What the next agent/session should do first.> ## Current state <Only facts needed to resume. Include branch, cwd, PR/issue links if relevant.> ## Decisions made <Bullets. Link to ADRs/plans/issues instead of restating them.> ## Open questions <Bullets, or "None".> ## Next actions 1. <First concrete action> 2. <Second concrete action> 3. <Verification or shipping step> ## Relevant artifacts - <path or URL>: <why it matters> ## Suggested skills - </skill-name>: <why>

Guardrails

Do not use handoff as a hidden summary of everything. Include only continuation context.

Prefer paths and URLs over pasted content.

Redact secrets and personal data.

Call out uncertainty explicitly.

If no useful work has happened yet, say so and write a short starter brief.

Handoff

Create a concise handoff document for another agent/session to continue from here.

When to Use

Use when the user wants to:

continue work in a fresh session
hand work to another agent
run a prototype or parallel line of work elsewhere
preserve actionable context without carrying the whole transcript

Procedure

Create a temp file:

handoff_file=$(mktemp -t handoff-XXXXXX.md)
cat "$handoff_file" >/dev/null

Write the handoff to that path.
Keep it compact. Do not duplicate artifacts already captured in PRDs, plans, ADRs, issues, commits, diffs, or docs. Reference them by path or URL.
If the user provided arguments, treat them as the next session focus and tailor the handoff around that work.
Redact sensitive information: API keys, passwords, tokens, secrets, personal data, customer data, and any other confidential values. Mention redaction only when it affects continuation.
Suggest skills the next session should use, if any.
Return only the handoff path plus a 1-2 sentence summary.

Handoff Template

# Handoff

## Next session focus
<What the next agent/session should do first.>

## Current state
<Only facts needed to resume. Include branch, cwd, PR/issue links if relevant.>

## Decisions made
<Bullets. Link to ADRs/plans/issues instead of restating them.>

## Open questions
<Bullets, or "None".>

## Next actions
1. <First concrete action>
2. <Second concrete action>
3. <Verification or shipping step>

## Relevant artifacts
- <path or URL>: <why it matters>

## Suggested skills
- </skill-name>: <why>

Guardrails

Do not use handoff as a hidden summary of everything. Include only continuation context.
Prefer paths and URLs over pasted content.
Redact secrets and personal data.
Call out uncertainty explicitly.
If no useful work has happened yet, say so and write a short starter brief.

handoff

Popularity

Invocation

Context Preview

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

handoff

Popularity

Invocation

Context Preview

SKILL.md

Handoff

When to Use

Procedure

Handoff Template

Guardrails

Similar Skills

Help us improve

Handoff

When to Use

Procedure

Handoff Template

Guardrails