handoff

Create a handoff document summarizing session state with suggested skills and redacted sensitive information.

5|Updated May 21, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/pi-package-goal --skill handoff-trebuchetdynamics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/TrebuchetDynamics/pi-package-goal/tree/main/skills/handoff
Command: npx skills add https://github.com/TrebuchetDynamics/pi-package-goal --skill handoff-trebuchetdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handing off a partially completed task between agents often loses context, decisions, and constraints, causing duplicated work or incorrect next steps.

Core Features & Use Cases

  • Conversation compaction into a handoff document: Summarizes what happened and what matters so a fresh agent can continue efficiently.
  • Actionable next-step guidance: Includes a "suggested skills" section that points the next agent to relevant follow-up skills.
  • Artifact-aware referencing: Avoids duplicating existing outputs (like PRDs, plans, ADRs, issues, commits, diffs) by referencing them by path or URL instead.
  • Safety and privacy guardrails: Redacts sensitive information such as API keys, passwords, and personally identifiable information.

Quick Start

Use the handoff skill to generate a continuation brief for another agent to pick up, tailored to the next session’s focus.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a continuation brief for another agent to pick up my work?▼

To create a continuation brief, you need a session handoff document that captures the project state, decisions, and constraints. This skill packages multi-step work session context into a concise brief for a fresh agent to continue efficiently.

What is the best way to summarize a session without losing project continuity?▼

Session summaries for project continuity require compacting conversations into actionable handoff documents. This approach captures what happened and what matters, while suggesting relevant follow-up skills for the next agent's focus.

Does agent collaboration context packaging redact sensitive information like API keys?▼

Agent collaboration context packaging includes safety guardrails that redact sensitive information such as API keys, passwords, and personally identifiable information. This ensures the generated handoff document is safe to share across agents.

How do I reference existing deliverables in a next-agent brief without duplicating work?▼

To reference existing deliverables in a next-agent brief without duplication, use artifact-aware referencing. This method points to existing outputs like PRDs, plans, ADRs, issues, commits, and diffs by path or URL instead of recreating them.

Can I use session handoff documents for ongoing multi-step projects?▼

Session handoff documents are designed for ongoing multi-step projects where context transfer is needed. They apply directly to requests for continuation briefs or next-agent context, preventing duplicated work and incorrect next steps.