handoff

Summarize the current conversation into a handoff document saved to a temporary path.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/engineer-skills-tutorial --skill handoff-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/az9713/engineer-skills-tutorial/tree/main/skills/productivity/handoff
Command: npx skills add https://github.com/az9713/engineer-skills-tutorial --skill handoff-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compact the current conversation into a handoff document for another agent to pick up.

Core Features & Use Cases

  • Generate a concise summary of the discussion, decisions, and context for a new agent.
  • Reference relevant artifacts (PRDs, plans, ADRs, issues, commits) by path or URL.
  • Provide recommended next steps and skills to apply in the follow-up session.

Quick Start

Generate a handoff document from the current chat and save it to a temporary path.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer conversation context to a new agent session?

How do I generate a handoff document for agent onboarding? You generate a handoff document by summarizing the current chat into a markdown file saved to a temporary path, which provides the next agent with context, artifacts, and recommended next steps.

What is the best way to summarize a workflow for another agent to continue?

Summarizing a workflow for another agent involves compacting the current conversation into a handoff document that references relevant artifacts like PRDs, plans, ADRs, issues, and commits by path or URL.

Does the handoff document include recommended next steps for the follow-up session?

Yes, the handoff document includes recommended next steps and suggests specific skills to apply, ensuring the follow-up session has clear direction and context for ongoing work.

Where is the generated context transfer document saved?

The context transfer document is saved to a temporary markdown file path produced by mktemp -t handoff-XXXXXX.md, ensuring the summary is stored locally for the next agent to access.

Can I reference external documentation and issues when creating a session summary?

Yes, you can reference external documentation and issues when creating a session summary by including their paths or URLs so the new agent can access PRDs, plans, ADRs, and commits directly.