delegation-routing

Route tasks between agents using keyword patterns and #runSubagent prompts.

14|2|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/kennedym-ds/copilot_orchestrator --skill delegation-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-routing
Source: https://github.com/kennedym-ds/copilot_orchestrator/tree/main/.github/skills/delegation-routing
Command: npx skills add https://github.com/kennedym-ds/copilot_orchestrator --skill delegation-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegation routing enables autonomous, seamless handoffs between agents, replacing UI-based handoff buttons with #runSubagent-driven delegation.

Core Features & Use Cases

  • Keyword-based routing: Detect when a specialist is needed and route to the correct agent.
  • Context-aware prompts: Build concise delegation prompts carrying objectives, scope, and constraints.
  • Guardrails & escalation: Enforce model preferences, allowlists, and escalation to conductor when routing is ambiguous.
  • Unified conductor-downstream coordination: Maintain a single user-facing entry point while enabling autonomous delegation across agents.

Quick Start

Instruct the system to delegate a task to the appropriate agent with objective, scope, and acceptance criteria.

Frequently Asked Questions about delegation-routing

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

FAQPage Schema
How do I route tasks between agents in a multi-agent workflow?

Task routing between agents is handled by matching keyword patterns to select a target agent, then constructing a context-aware prompt with objectives, scope, and constraints to invoke via #runSubagent.

What is autonomous inter-agent task delegation?

Inter-agent task delegation replaces manual UI-based handoffs with autonomous, seamless handoffs between agents, using keyword detection and #runSubagent-driven prompts to route objectives to specialist agents.

How do I enforce guardrails when delegating tasks to specialist agents?

Delegation guardrails enforce model preferences, agent allowlists, and escalation to a conductor agent when routing is ambiguous, preventing unauthorized or incorrect specialist invocations.

Can I use keyword matching for cross-functional coordination across workflow agents?

Keyword matching applies across core workflow agents like conductor, planner, implementer, and reviewer, plus support agents for security, performance, accessibility, docs, and observability coordination.

When should I escalate a delegated task to a conductor agent?

You should escalate to a conductor agent when routing is ambiguous, keyword matching fails to identify a clear target agent, or when invocation guardrails detect a constraint violation.

What context do I need to include in a delegation prompt?

A delegation prompt should include the task objective, scope, and acceptance criteria, carrying concise context to the target agent to ensure cross-functional coordination succeeds.