handoff

Standardize inter-agent handoffs with a canonical wire-format contract.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The HANDOFF skill provides a canonical, observable contract for moving work, state, and messages across coherence cells, ensuring inter-agent and inter-repo handoffs are traceable, auditable, and boundary-respecting.

Core Features & Use Cases

  • Canonical wire-format contract for inter-agent handoffs across cells.
  • Sub-surface skills for cross-repo coordination (cross-repo, dispatch, mid-flight, artifact-channel, receipt-stream) that plug into the loader with explicit interfaces.
  • Ensures coherence by aligning boundary responsibilities and enabling audit trails during cycle transitions and releases.
  • Use cases include transferring work between cells, handoff of memory and state, and coordinating with operator-human interventions during cycles.

Quick Start

Load the HANDOFF skill and its sub-skills to enable inter-agent handoffs across coherence cells.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I standardize inter-agent handoffs across multiple repositories?

Inter-agent handoffs across multiple repositories are standardized using a canonical wire-format contract that ensures boundary crossing is traceable, auditable, and consistent. This contract governs cross-repo synchronization and artifact-channel sequencing.

What is a canonical wire-format contract for cross-repo coordination?

A canonical wire-format contract for cross-repo coordination is an explicit implementation contract that standardizes how work, state, and messages move across coherence cells. It provides observable boundary governance and delta enrichment rules for cycle transitions.

How do I transfer memory and state between cells during cycle transitions?

Memory and state are transferred between cells during cycle transitions using sub-surface skills like dispatch and receipt-stream that plug into the loader. These skills provide explicit interfaces ensuring coherence and enabling audit trails during releases.

Can I use handoff contracts for mid-flight rescue pathways during agent coordination?

Handoff contracts provide a guarded mid-flight rescue pathway specifically for agent coordination during cycles. This pathway enables operator-human interventions and ensures boundary responsibilities are respected while maintaining coherence.

Does the handoff wire-format support intra-cycle coordination alongside cross-repo synchronization?

The handoff wire-format supports both intra-cycle coordination and cross-repo synchronization through a suite of sub-skills. These include dispatch, mid-flight, artifact-channel, and receipt-stream components that plug into the loader with explicit interfaces for consistent boundary crossing.

When do I need explicit implementation contracts for boundary governance?

Explicit implementation contracts for boundary governance are needed when transferring work between coherence cells, handing off memory and state, or coordinating operator-human interventions. They ensure handoffs remain traceable and auditable during cycle transitions and releases.