delegation

Coordinate multi-agent delegation across Donna, Nina, Leo, and coding sub-agents.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/spiral-app-labs/skills --skill delegation-spiral-app-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation
Source: https://github.com/spiral-app-labs/skills/tree/main/delegation
Command: npx skills add https://github.com/spiral-app-labs/skills --skill delegation-spiral-app-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestration protocol that provides a repeatable, safe framework for multi-agent delegation, ensuring clear roles, constraints, and context sharing across Donna, Nina, Leo, and coding sub-agents.

Core Features & Use Cases

  • Agent roster and constraints: defines roles, access, and memory boundaries to prevent cross-device leaks.
  • Cross-agent handoff protocols: formalizes Donna→Nina, Donna→Coding Sub-Agent, and Donna→Leo handoffs with required briefs and channels.
  • Task orchestration structures: supports Task, Epic, and Phased Epic with blockers and dependencies in Mission Control.
  • Context sharing rules: ensures critical knowledge persists in Notion, Supabase, and GitHub while local workspace remains device-scoped.
  • Safe escalation and governance: includes decision rules to minimize unnecessary delegation and optimize handoffs for complex workflows.

Quick Start

Consult this delegation protocol before any non-trivial task to ensure proper agent roster, handoffs, and context sharing.

Frequently Asked Questions about delegation

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

FAQPage Schema
How do I manage multi-agent orchestration and ensure safe handoffs between coding sub-agents?

Multi-agent orchestration is managed by defining an agent roster, cross-agent handoff contracts, and context-sharing rules enforced via Notion and Supabase. This framework prevents memory boundary leaks by formalizing required briefs and channels for every delegation.

What is a cross-agent handoff contract and when do I need one for task delegation?

A cross-agent handoff contract is a formalized brief and channel requirement for transferring tasks between agents like Donna, Nina, and Leo. You need this protocol for any non-trivial task to ensure shared context, policy enforcement, and safe escalation.

How do I structure complex tasks with dependencies and blockers in a multi-agent workflow?

Complex tasks are structured as Tasks, Epics, or Phased Epics within Mission Control using Supabase. This structure maps dependencies and blockers across the agent roster, optimizing real-time workflows and minimizing unnecessary delegation during execution.

Can I use Notion and Supabase together for context sharing across multiple agents?

Notion and Supabase work together to persist critical knowledge and enforce context-sharing rules across agents. Notion stores shared briefs while Supabase manages Mission Control, ensuring local workspaces remain device-scoped to prevent cross-device leaks.

What are the limitations of unstructured delegation in real-time multi-agent workflows?

Without structured delegation protocols, real-time workflows risk cross-device memory leaks, lost shared context, and unnecessary escalation. Implementing a decision tree and formal handoff contracts mitigates these risks by enforcing constraints and clear agent roles.

Do I need a decision tree to prevent unnecessary delegation to coding sub-agents?

A delegation decision tree is required to optimize handoffs and enforce safe escalation governance. It provides explicit rules for when to delegate tasks to coding sub-agents, preventing unnecessary escalation and maintaining workflow efficiency.