intent-routing

Classify user intents and route them to PMO departments and agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BoomerAng9/foai --skill intent-routing-boomerang9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-routing
Source: https://github.com/BoomerAng9/foai/tree/main/acheevy/.claude/skills/intent-routing
Command: npx skills add https://github.com/BoomerAng9/foai --skill intent-routing-boomerang9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ACHEEVY's intent-routing mechanism classifies user requests and dispatches them to the appropriate PMO department and agent, streamlining cross-team collaboration and response times.

Core Features & Use Cases

  • Classifies user intents beyond keyword matching to map to the correct PMO department (ECHO, SHIELD, PULSE, LAUNCH, LENS) and agent.
  • Supports deterministic routing logic, department-aware escalation, and overflow handling for complex queries.
  • Use Case: A user asks to build a REST API endpoint; the system routes it to PMO-ECHO with the API_Ang agent for backend work.

Quick Start

Provide a user message describing the desired outcome and let ACHEEVY route it accordingly.

Frequently Asked Questions about intent-routing

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

FAQPage Schema
How does intent routing work for dispatching user requests to PMO teams?

Intent routing classifies user requests beyond keyword matching to map them to the correct PMO department and agent. It applies deterministic routing logic to determine the appropriate department, agent, and escalation path for multi-department tasks.

How do I escalate a task that spans multiple PMO departments?

To escalate multi-department tasks, the intent routing mechanism applies department-aware escalation rules to escalate the request to Chicken Hawk and Lil_Hawks. This ensures complex queries receive coordinated cross-team handling.

What happens when the intent routing system is unclear about the correct PMO department?

When the intent is unclear, the routing system enforces a fallback chain that defaults the request to PMO-ECHO. It also allows escalation when confidence is insufficient to ensure accurate dispatch.

Can I route a REST API endpoint request to a specific backend agent?

Yes, intent routing can dispatch specific technical requests. For example, a user asking to build a REST API endpoint is routed to PMO-ECHO with the API_Ang agent assigned for backend work.

Which PMO departments are available for intent dispatch and escalation?

The intent routing system maps user requests to five PMO departments: ECHO, SHIELD, PULSE, LAUNCH, and LENS. Each department handles specific task categories and assigns the appropriate agent.

Do I need to set up dependencies to start routing user intents to agents?

No dependencies are required to start routing user intents. You simply provide a user message describing the desired outcome, and the system classifies and routes it to the appropriate PMO department and agent automatically.