handoff

Generate a structured handoff document summarizing conversation goals, steps, and context.

7|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/borkweb/skills --skill handoff-borkweb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/borkweb/skills/tree/main/skills/core/handoff
Command: npx skills add https://github.com/borkweb/skills --skill handoff-borkweb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps automate the creation of handoff documents, ensuring a smooth transition between agents.

Core Features & Use Cases

  • Handoff Document Generation: Automates the creation of handoff documents from a current conversation.
  • Target Path Customization: Allows specifying a target path for the handoff document.
  • Structure and Sections: Ensures that the handoff document includes necessary sections such as goals, state, steps, questions, context, pointers, and suggested skills.

Quick Start

Run the command to create a handoff document: /handoff --what "What will the next session be used for?"

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I generate a conversation summary for task continuity between agents?

To generate a conversation summary for task continuity, you can use a structured handoff document that captures goals, steps, and context. This ensures critical information is transferred smoothly by summarizing the current session.

What is the best way to automate agent communication handoffs?

Automating agent communication handoffs is best achieved by generating a structured document that outlines goals, state, steps, and questions. This approach ensures all critical context is automatically transferred between agents.

What sections should be included in a handoff document for task continuity?

A handoff document for task continuity should include sections for goals, state, steps, questions, context, pointers, and suggested skills. These sections ensure all critical information is structured for the next agent.

Can I specify a target path for the handoff document generated from my conversation?

Yes, you can specify a target path for the handoff document generated from your conversation. This allows you to control where the conversation summary and task continuity context are saved for the next agent.

How do I create a handoff document for my next session?

You create a handoff document for your next session by running a command that prompts the system to summarize the current conversation context. This generates a structured summary outlining goals, steps, and context for continuation.

When do I need to generate a handoff document for agent communication?

You need to generate a handoff document for agent communication when transitioning tasks between sessions or agents. It ensures critical information like goals, state, and steps is transferred, preventing context loss during continuation.