request-dispatcher

Route ambiguous user requests to the correct Forge Skill using intent and project state.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/iJosueeh/nexora-web --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/nexora-web/tree/main/.opencode/skills/request-dispatcher
Command: npx skills add https://github.com/iJosueeh/nexora-web --skill request-dispatcher-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves ambiguity in user requests that don't clearly match a single Skill's trigger criteria, routing them to the correct Skill based on intent and project state.

Core Features & Use Cases

  • Ambiguity Resolution: Analyzes ambiguous user requests and routes them to the correct Skill.
  • Project State Awareness: Checks project artifacts like Product-Spec.md, DEV-PLAN.md, and code for routing.
  • Structured Decision Framework: Classifies intent, cross-references project state, and resolves ambiguity to recommend a Skill.

Quick Start

Run the /request-dispatcher command to analyze and route an ambiguous user request.

Frequently Asked Questions about request-dispatcher

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

FAQPage Schema
What is the best way to route ambiguous user requests to the correct skill?

Routing ambiguous requests requires analyzing user intent and project state to match the request to the correct skill. It classifies the request, cross-references project artifacts, and resolves ambiguity to recommend the appropriate skill.

How do I resolve request routing ambiguity when a command matches multiple triggers?

To resolve routing ambiguity, cross-reference the request with project state artifacts like Product-Spec.md and DEV-PLAN.md. Analyzing project state alongside intent clarifies which specific skill should handle the request.

When do I need intent analysis for dispatching project tasks?

Intent analysis for dispatching is needed when a user's request is unclear and doesn't match a single skill's trigger criteria. It applies to scenarios where request routing boundaries overlap and manual clarification is required.

Does request routing work without existing project artifacts like DEV-PLAN.md?

Request routing relies on project artifacts like DEV-PLAN.md and Product-Spec.md to analyze project state. Without these artifacts, the structured decision framework loses context needed to accurately classify intent and resolve ambiguity.

Why does ambiguous resolution fail to match the correct skill despite clear instructions?

Ambiguous resolution may fail if the project state has changed recently without updating artifacts. The routing mechanism requires knowledge of project artifacts and recent changes to accurately cross-reference intent with the current project state.