handoff

Generates a compact handoff document summarizing session state for the next agent.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill handoff-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/productivity/handoff
Command: npx skills add https://github.com/reddb-io/red-skills --skill handoff-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation ends or context runs out, the next agent session starts blind and repeats work. This Skill compacts the current conversation into a structured handoff document so another agent can pick up exactly where you left off. ## Core Features & Use Cases - State Summarization: Captures what was done, what is in progress, and what is blocked. - Reference-Based Handoff: Points to existing Specs, plans, ADRs, issues, commits, and diffs by path or URL instead of duplicating their content. - Secret Redaction: Removes API keys, passwords, tokens, and personally identifiable information before writing the document. - Use Case: You are ending a long debugging session and want a fresh agent to continue tomorrow. Invoke the handoff skill to produce a Markdown file with the current state, the first concrete next step, recommended skills to invoke, and links to relevant artifacts. ## Quick Start Ask the agent to create a handoff document for the next session, optionally describing what that session will focus on.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off context between agent sessions?▼

Invoke the handoff skill to write a Markdown document covering current state, the first concrete next action, skills the next session should invoke, and references to existing artifacts. The file is written to a temporary path created with mktemp.

What should a handoff document include for the next agent?▼

Include what was done, what is in progress, what is blocked, the first concrete next step, any skills to invoke, and paths or URLs to Specs, plans, ADRs, issues, commits, or diffs. Reference artifacts rather than reproducing their content.

Does the handoff document protect API keys and secrets?▼

Yes. The skill instructs redaction of API keys, passwords, tokens, and personally identifiable information before the document is written, so sensitive values are not carried into the handoff file.

Can I tailor the handoff for a specific next task?▼

Yes. Pass an argument describing what the next session will focus on, and the handoff document is tailored accordingly, emphasizing the state and references most relevant to that goal.

When should I not use a handoff document?▼

Avoid it when the work is fully complete with nothing in progress or blocked, or when all context already lives in committed artifacts like issues and ADRs that the next session can read directly.