workflow/generate-handoff

Generate structured handoff YAML artifacts with guard rails for multi-agent workflows.

Updated Jan 11, 2026

Search Tags:#workflow #context #handoff #telemetry #U.Work #guard-rails #deterministic-naming

Ready to run

npx skills add https://github.com/venikman/fpf-foundry --skill workflow-generate-handoff

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized way to create structured handoff artifacts with explicit guard rails, enabling consistent handoffs between agents and auditable traces.

Core Features & Use Cases

Guarded handoff generation: validates inputs, enforces constraints, and writes deterministic handoff records to runtime/contexts/<context>/handoffs/<session_id>.<to_agent_type>.<n>.handoff.yaml.
U.Work logging integration: optionally emits a work log entry when telemetry/log-work is available, facilitating traceability in workflows.
Use Case: when handing off work between strategist and executor roles within a bounded context; ensures the recipient receives clear instructions, guard rails, and a verifiable artifact.

Quick Start

Run the generate-handoff skill with your inputs to produce a handoff artifact at runtime/contexts/<context>/handoffs/... Provide the following fields: context, session_id, to_agent_type, and instructions.

Frequently Asked Questions about workflow/generate-handoff

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

FAQPage Schema

How do I generate structured handoff artifacts for multi-agent workflows?▼

To generate a structured handoff artifact, you provide context, session_id, to_agent_type, and instructions. The skill validates these inputs and writes a deterministic YAML file to runtime/contexts/<context>/handoffs/.

What are agent handoff guard rails and why do I need them?▼

Agent handoff guard rails are enforced constraints and input validations that ensure clear instructions and auditable traces across bounded contexts. They prevent invalid data transfer and ensure recipient agents receive verifiable instructions.

How do I log telemetry for agent handoffs in a bounded context?▼

You can log telemetry for agent handoffs by integrating with the U.Work logging system. When the telemetry/log-work skill is available, the skill optionally emits a work log entry during the handoff generation process.

How does deterministic naming work for multi-agent handoff records?▼

Deterministic naming for handoff records uses the pattern <session_id>.<to_agent_type>.<n>.handoff.yaml. This ensures every generated artifact has a predictable, traceable file path within the runtime/contexts/<context>/handoffs/ directory.

Can I use this handoff generation skill for transferring work between strategist and executor roles?▼

Yes, you can use this skill to transfer work between strategist and executor roles. It explicitly supports handing off work within bounded contexts by ensuring the executor receives clear instructions, guard rails, and a verifiable artifact.

What inputs are required to create a verifiable agent handoff trace?▼

Creating a verifiable agent handoff trace requires providing the context, session_id, to_agent_type, and instructions fields. These inputs are validated to produce the final structured YAML handoff artifact.