handoff

Generates a handoff document summarizing the current conversation for a fresh agent session.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill handoff-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/j172/bid/tree/main/agent/skills/handoff
Command: npx skills add https://github.com/j172/bid --skill handoff-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a conversation grows long or needs to move to a new agent session, context is lost and the next agent starts blind. This Skill compacts the current conversation into a structured handoff document so a fresh agent can continue the work without re-reading the entire history. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current conversation into a handoff document saved to the operating system's temporary directory, keeping the workspace clean. - Suggested Skills Section: Includes recommendations for which skills the next agent should invoke to continue the work. - Artifact Referencing & Redaction: References existing specs, plans, ADRs, issues, commits, and diffs by path or URL instead of duplicating them, and redacts sensitive data such as API keys, passwords, and personally identifiable information. - Use Case: Before ending a long debugging session, invoke the handoff skill with a note like "next session: implement the fix" so the next agent receives a focused, sanitized summary with pointers to the relevant commits and plans. ## Quick Start Ask the agent to create a handoff document for the next session, optionally describing what the next session should 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 a conversation to a new agent session?

Invoke the handoff skill to summarize the current conversation into a handoff document. The document is saved to your operating system's temporary directory, and you can pass arguments describing what the next session should focus on.

Where is the handoff document saved?

The handoff document is saved to the temporary directory of the user's operating system, not the current workspace. This keeps the project workspace free of transient session files.

Does the handoff document include sensitive information like API keys?

No. The skill explicitly redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the handoff document.

Does the handoff duplicate existing specs, plans, or commits?

No. Content already captured in artifacts like specs, plans, ADRs, issues, commits, and diffs is referenced by path or URL instead of being duplicated in the handoff document.

Can I customize the handoff for what the next session will do?

Yes. If you pass arguments when invoking the skill, they are treated as a description of the next session's focus, and the handoff document is tailored accordingly, including a suggested skills section.