delivery-router

Route ambiguous delivery and product tasks to appropriate sub-skills.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill delivery-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-router
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/delivery-router
Command: npx skills add https://github.com/Ocean326/Agents --skill delivery-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivery Router acts as a centralized categorization gateway that routes vague or multi-faceted requests to the most appropriate product/delivery sub-skills, reducing misrouting and handoff friction.

Core Features & Use Cases

  • End-to-end routing guidance across discovery, proposal, planning, implementation, testing, and verification.
  • Unified decision-maker that selects the best delivery lane and proposes next concrete steps.
  • Clear separation of concerns, with fallback routing when no single lane is obvious.

Quick Start

Describe your task and let Delivery Router route it to the appropriate path (discovery, proposal, planning, delivery, or verification) and propose the next concrete action.

Frequently Asked Questions about delivery-router

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

FAQPage Schema
What is the best way to route ambiguous product management tasks to the correct workflow?

Task routing for ambiguous product work uses a centralized gateway to categorize multi-faceted requests and direct them to appropriate sub-skills, reducing misrouting and handoff friction across discovery, planning, and implementation phases.

How do I coordinate product delivery tasks that span discovery, planning, and verification?

Coordinating end-to-end product delivery tasks requires a unified decision-maker that selects the best delivery lane across discovery, planning, implementation, and verification, while proposing the next concrete action and respecting boundaries between sub-skills.

When do I need task orchestration for product management workflows?

Task orchestration is needed when requests span multiple delivery phases like discovery, proposal, planning, implementation, or verification, and require explicit coordination across owners and artifacts to ensure correct task routing decisions.

Can I use a single AI assistant to manage task routing across different delivery phases?

Using a single AI assistant for task routing provides a unified front door that applies decision-making logic to ambiguous requests, selecting the best delivery lane and proposing next concrete steps without requiring manual handoff.

What happens to product management requests when no clear delivery lane exists?

When no clear delivery lane exists for product management requests, the system applies fallback routing to handle the ambiguity, ensuring that tasks lacking a single obvious path still receive guidance and a proposed next action.