write-agent-handoff

Transfer transient task state between agents using mode-specific handoff payloads.

6|Updated May 23, 2026
One-click install
npx skills add https://github.com/Daaaaave/agentic-workspace-core --skill write-agent-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-agent-handoff
Source: https://github.com/Daaaaave/agentic-workspace-core/tree/main/payload/.agents/skills/write-agent-handoff
Command: npx skills add https://github.com/Daaaaave/agentic-workspace-core --skill write-agent-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables safe transfer of temporary task state between agents, sessions, or workspaces to ensure continuity without leaking durable memory or changing ownership.

Core Features & Use Cases

  • Supports multiple handoff modes (Resume, Delegation, Debug, Review, Compaction, Coordination) to fit different continuation needs.
  • Enforces a Handoff Contract with fields like Objective, Audience, Creation Snapshot, State, Evidence, and Boundaries, plus guidance on verification steps.
  • Stores handoff artifacts under .context/handoffs/ and provides a safe template for reporting results to the next agent.

Quick Start

Create a handoff file under .context/handoffs/ detailing objective, audience, and current state to hand off to the next agent.

Frequently Asked Questions about write-agent-handoff

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

FAQPage Schema
How do I transfer task state between AI agents safely?

To transfer task state safely between agents, create a handoff file under .context/handoffs/ detailing the objective, audience, and current state. This enforces a strict handoff contract to ensure seamless continuation without leaking durable memory or changing ownership.

What is a handoff contract for agent workflow delegation?

A handoff contract is a structured payload enforcing safe state transfer between agents or sessions. It requires specific fields like Objective, Audience, Creation Snapshot, State, Evidence, and Boundaries to preserve accountability and minimize risk during temporary task handoffs.

How do I resume a paused debug session across different repositories?

You can resume a paused debug session across repositories by using a mode-specific handoff payload. This Skill supports Debug and Resume modes, storing artifacts under .context/handoffs/ to enable seamless continuation of transient task state across workspaces or teams.

Can I use this for agent workflow coordination without leaking durable memory?

Yes, this Skill is specifically designed to transfer transient task state without leaking durable memory or changing ownership. It enforces strict evidence requirements and mode-specific payloads to ensure safe continuation across sessions, subagents, or workspaces.

What handoff modes are supported for context transfer between subagents?

Supported handoff modes include Resume, Delegation, Debug, Review, Compaction, and Coordination. Each mode uses a specific payload format to fit different continuation needs while enforcing the handoff contract and strict evidence requirements.

Why does my agent context transfer fail to preserve accountability?

Context transfers fail to preserve accountability when missing required handoff contract fields like Evidence, State, or Boundaries. This Skill enforces these strict evidence requirements and structured payloads to minimize risk and maintain accountability during task handoffs.