workflow/generate-handoff

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/.

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.

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.

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.

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.

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.