governance/handoff-to-agent

Record structured YAML handoff artifacts between agent roles within a session.

Updated Jan 11, 2026

Search Tags:#audit #agent #yaml #handoff #telemetry #session

Ready to run

npx skills add https://github.com/venikman/fpf-foundry --skill governance-handoff-to-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: governance/handoff-to-agent
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/governance/handoff-to-agent
Command: npx skills add https://github.com/venikman/fpf-foundry --skill governance-handoff-to-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill records a structured handoff artifact to transfer context and responsibility between agent roles within a session, enabling clear traceability and repeatable governance.

Core Features & Use Cases

Deterministic handoffs: generates a consistent handoff record path runtime/contexts/<context>/handoffs/<session_id>.<to_agent_type>.<n>.handoff.yaml with an incremented counter.
Audit-ready artifacts: produces a YAML handoff that captures context, session, participants, instructions, decisions, and notes for later review.
Telemetry integration: emits a U.Work log when telemetry/log-work is available to reflect the handoff action.

Quick Start

Run the handoff workflow by supplying required inputs to generate the handoff artifact. Example: provide context, session_id, and to_agent_type to produce a deterministic handoff file at runtime/contexts/<context>/handoffs/<session_id>.<to_agent_type>.<n>.handoff.yaml.

Frequently Asked Questions about governance/handoff-to-agent

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

FAQPage Schema

How do I record an agent handoff within a session for audit purposes?▼

To record an agent handoff, the skill generates a structured YAML artifact capturing context, participants, and instructions for deterministic traceability. This ensures your session handoffs are repeatable and audit-ready.

What is deterministic handoff sequencing and how does it work?▼

Deterministic handoff sequencing generates a consistent file path using an incremented counter for each YAML artifact within a bounded context. This mechanism ensures every agent role transition is sequentially logged and uniquely identifiable.

Can I use telemetry logging with session handoffs?▼

Yes, telemetry logging is supported by emitting a U.Work log when telemetry or log-work is available. This integrates your handoff artifacts directly into your broader observability and telemetry tracking systems.

How do I generate a YAML handoff file for a specific agent role?▼

Provide the required inputs—context, session_id, and to_agent_type—to produce a deterministic handoff file named <session_id>.<to_agent_type>.<n>.handoff.yaml. This file captures all decisions and notes for later review.

Do I need any dependencies or specific components to create a handoff artifact?▼

No dependencies are required to create a handoff artifact, as the skill performs input validation and naming independently. Telemetry logging via log-work is strictly optional and only used if available.