request-dispatcher

Routes ambiguous user requests to the correct Skill using intent classification and project state analysis.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill request-dispatcher-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-dispatcher
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/request-dispatcher
Command: npx skills add https://github.com/iJosueeh/amauta --skill request-dispatcher-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a user's request is ambiguous and doesn't clearly match a single Skill's trigger criteria, static dispatch rules fail. This Skill provides a structured decision framework to classify intent, cross-reference project state, and recommend the correct target Skill without guessing. ## Core Features & Use Cases - Intent Classification: Maps natural language requests to intent types (new product, change, bug, review, design, planning, implementation, release) using a decision matrix. - Project State Cross-Reference: Checks for artifacts like Product-Spec.md, DEV-PLAN.md, code, and active changes/ folders before recommending a route. - Disambiguation: Asks a single targeted clarifying question when intent and state analysis cannot resolve ambiguity. - Use Case: A user says "improve this" without context. The Skill checks project state, then asks whether they mean bug fixes, code quality, or UI design before routing to the right Skill. ## Quick Start Analyze my request and recommend which Skill should handle it based on the current project state.

Frequently Asked Questions about request-dispatcher

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

FAQPage Schema
How do I route ambiguous user requests to the right AI skill?▼

Classify the user's intent into categories like bug, feature, or planning, then cross-reference project state such as existing specs and code. If still ambiguous, ask one targeted clarifying question before recommending a single skill.

What is a request dispatcher in an AI agent workflow?▼

A request dispatcher is a routing layer that analyzes user intent and project state to select the correct downstream skill. It handles the edge cases where static dispatch rules cannot uniquely determine the target.

When should I use a dispatcher instead of static routing rules?▼

Use a dispatcher only for the roughly 10 percent of requests where static rules produce no clear match. Clear-cut requests that match a single skill trigger should go directly to that skill without dispatch overhead.

Why does skill routing fail without checking project state?▼

Routing fails when prerequisites are missing, such as dispatching to a planner without a product spec or a code reviewer without code. Verifying artifact existence before recommending prevents recommendations that bounce back.

Can a dispatcher handle requests that mix bugs and features?▼

Yes, but it routes to the dominant intent first rather than both at once. The standard practice is to fix the bug before adding features, so the bug-fixing skill takes priority.