agent-handoff-governance

Manages AI agent-to-sub-agent task delegation with ownership, criteria, and traceability.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Umbral-Bot/umbral-agent-stack --skill agent-handoff-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-handoff-governance
Source: https://github.com/Umbral-Bot/umbral-agent-stack/tree/main/openclaw/workspace-templates/skills/agent-handoff-governance
Command: npx skills add https://github.com/Umbral-Bot/umbral-agent-stack --skill agent-handoff-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that when work is delegated between agents or sub-agents, crucial context, ownership, acceptance criteria, and traceability are maintained, preventing lost information and ensuring accountability.

Core Features & Use Cases

  • Contextual Handoffs: Guarantees that delegated tasks retain essential context, minimizing the need for re-explanation.
  • Explicit Ownership: Clearly defines who is responsible for each stage of a task, from delegation to final integration.
  • Traceability: Records handoffs in systems like Linear and Notion for auditing and progress tracking.
  • Use Case: When an agent encounters a complex issue it cannot resolve, it uses this skill to formally hand off the task to a specialized sub-agent, documenting the problem, expected outcome, and acceptance criteria, ensuring the original agent can integrate the solution later.

Quick Start

Use the agent-handoff-governance skill to create a traceable handoff for a blocked task, specifying the expert owner and acceptance criteria.

Frequently Asked Questions about agent-handoff-governance

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

FAQPage Schema
How do I maintain context preservation during AI agent handoffs?

Context preservation during AI agent handoffs is maintained by explicitly defining the expert owner, acceptance criteria, and task problem details before delegating. This ensures minimal context is lost and the original agent can later integrate the returned solution.

What is the best way to govern task delegation between sub-agents?

Governing task delegation between sub-agents requires assigning explicit ownership and defining acceptance criteria before the handover occurs. This approach prevents premature closures and ensures accountability throughout the workflow management process.

How do I record agent handovers in Linear and Notion for traceability?

You record agent handovers in Linear and Notion by logging the delegation event with its context and acceptance criteria. This creates an auditable trail for progress tracking and prevents premature task closures.

Why do my sub-agent tasks lose ownership and context when blocked?

Sub-agent tasks lose ownership and context when blocked if the handover lacks a formal governance process. Explicitly assigning an expert owner and documenting the expected outcome ensures accountability and traceability until the task returns.

When should I use a formal handoff process for specialized agent tasks?

You should use a formal handoff process for specialized agent tasks when an agent encounters a complex blockage it cannot resolve. This formally delegates the issue to a specialized sub-agent while maintaining traceability.

Does agent handoff governance prevent premature task closures?

Yes, agent handoff governance prevents premature task closures by enforcing acceptance criteria and explicit ownership. It audits delegations and maintains task state traceability until the original requester successfully integrates the solution.