deliver

Classify delivery requests and route them to one downstream skill.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill deliver-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/deliver
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill deliver-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinator that classifies delivery requests and routes them to the appropriate downstream skills, enabling safe, efficient execution without performing implementation itself.

Core Features & Use Cases

  • Lightweight coordination that inspects incoming work requests and selects the optimal route (direct, parallel, swarm, or debug) based on the request scope.
  • Ensures exactly one downstream skill is delegated per request and records routing rationale for traceability.
  • Supports deflection rules to steer underspecified or ideation-shaped requests to planning or brainstorm workflows.

Quick Start

Provide a clearly scoped delivery request to trigger routing to the appropriate downstream skill.

Frequently Asked Questions about deliver

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

FAQPage Schema
What is task delivery routing in a multi-skill workflow?

Task delivery routing classifies incoming work requests and directs them to the correct downstream execution path. It selects direct, parallel, swarm, or debug routes based on request scope to ensure work is processed efficiently.

How does a coordinator route work requests to downstream execution paths?

A coordinator inspects the scope and context of a delivery request, then delegates to exactly one downstream skill. It selects between direct, parallel, swarm, or debug routes and records routing rationale in durable artifacts for traceability.

Can I deflect underspecified requests to a planning workflow?

Yes, you can deflect underspecified or ideation-shaped requests. The coordinator applies deflection rules to steer ambiguous work away from execution and into planning or brainstorm workflows before any downstream routing occurs.

How do I trace the routing rationale for a delegated delivery request?

You trace routing rationale through durable artifacts. The coordinator records its classification decisions and the selected execution path, ensuring full traceability for every request delegated to a downstream skill.

When should I use swarm routing instead of parallel execution paths?

Use swarm routing or parallel execution paths based on the scope and context of your incoming request. The coordinator evaluates the delivery requirements to select the optimal route, ensuring exactly one downstream skill handles the work.

Does this task routing coordinator perform implementation work itself?

No, the task routing coordinator does not perform implementation work. It acts as a lightweight layer that classifies requests and delegates execution entirely to downstream skills, ensuring safe and efficient workflow coordination.