handoff

Compress active agent session context into a structured markdown document.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill handoff-iuliandita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/iuliandita/skills/tree/main/skills/handoff
Command: npx skills add https://github.com/iuliandita/skills --skill handoff-iuliandita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the issue of context degradation and session bloat by allowing you to compress the current state of an agent's work into a concise, actionable document that a new session can immediately resume.

Core Features & Use Cases

  • Context Compression: Summarizes complex, multi-step workflows into a single, portable markdown document.
  • Decision Preservation: Records not just what was decided, but the rationale behind it, preventing the next session from relitigating settled issues.
  • Use Case: When switching from a planning phase to an implementation phase, use this skill to pass off verified state, blocked items, and specific pointers to the next agent session, ensuring a clean and focused start.

Quick Start

Invoke the handoff skill to compress the current session context into a disposable document for a fresh start.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I transfer context between agent sessions without losing state?

To transfer context between agent sessions, you compress the active session state into a structured markdown document that captures locked decisions, current state verification, and artifact pointers for immediate downstream resumption.

What is context compression and when do I need it for agent workflows?

Context compression summarizes complex, multi-step workflows into a portable markdown document to prevent context degradation and session bloat when switching between independent task sessions.

How do I prevent a new agent session from relitigating decisions made in a previous session?

You prevent relitigation by recording not just what was decided but the rationale behind it in a handoff document, ensuring the next session inherits verified state without reopening settled issues.

Does the handoff skill require a specific markdown schema for session context?

Yes, the handoff skill requires adherence to a specific markdown schema to ensure high-attention window compatibility and prevent context drift when a new session resumes the work.

What's the best way to pass blocked items and pointers to a downstream agent session?

The best way to pass blocked items and pointers is to invoke a context compression skill that encodes the current state, blockers, and artifact references into a disposable markdown document for a clean start.