Intelligent Routing

Intelligent Agent Routing

Purpose: Automatically analyze user requests and route them to the most appropriate specialist agent(s) without requiring explicit user mentions.

Core Principle

> The AI should act as an intelligent Project Manager, analyzing each request and automatically selecting the best specialist(s) for the job.

How It Works

1. Request Analysis

Before responding to ANY user request, perform automatic analysis:

graph TD
    A[User Request: Add login] --> B[ANALYZE]
    B --> C[Keywords]
    B --> D[Domains]
    B --> E[Complexity]
    C --> F[SELECT AGENT]
    D --> F
    E --> F
    F --> G[security-auditor + backend-specialist]
    G --> H[AUTO-INVOKE with context]

2. Agent Selection Matrix

Use this matrix to automatically select agents:

| User Intent | Keywords | Selected Agent(s) | Auto-invoke? | | ------------------- | ------------------------------------------ | ------------------------------------------- | ------------ | | Authentication | "login", "auth", "signup", "password" | security-auditor + backend-specialist | ✅ YES | | UI Component | "button", "card", "layout", "style" | frontend-specialist | ✅ YES | | Mobile UI | "screen", "navigation", "touch", "gesture" | mobile-developer | ✅ YES | | API Endpoint | "endpoint", "route", "API", "POST", "GET" | backend-specialist | ✅ YES | | Database | "schema", "migration", "query", "table" | database-architect + backend-specialist | ✅ YES | | Bug Fix | "error", "bug", "not working", "broken" | debugger | ✅ YES | | Test | "test", "coverage", "unit", "e2e" | test-engineer | ✅ YES | | Deployment | "deploy", "production", "CI/CD", "docker" | devops-engineer | ✅ YES | | Security Review | "security", "vulnerability", "exploit" | security-auditor + penetration-tester | ✅ YES | | Performance | "slow", "optimize", "performance", "speed" | performance-optimizer | ✅ YES | | Product Def | "requirements", "user story", "backlog", "MVP" | product-owner | ✅ YES | | New Feature | "build", "create", "implement", "new app" | orchestrator → multi-agent | ⚠️ ASK FIRST | | Complex Task | Multiple domains detected | orchestrator → multi-agent | ⚠️ ASK FIRST |

3. Automatic Routing Protocol

TIER 0 - Automatic Analysis (ALWAYS ACTIVE)

Before responding to ANY request:

// Pseudo-code for decision tree
function analyzeRequest(userMessage) {
    // 1. Classify request type
    const requestType = classifyRequest(userMessage);

    // 2. Detect domains
    const domains = detectDomains(userMessage);

    // 3. Determine complexity
    const complexity = assessComplexity(domains);

    // 4. Select agent(s)
    if (complexity === "SIMPLE" && domains.length === 1) {
        return selectSingleAgent(domains[0]);
    } else if (complexity === "MODERATE" && domains.length  intelligent-routing
- If GEMINI.md specifies explicit routing, follow it
- Intelligent routing is the DEFAULT when no explicit rule exists

## Testing the System

### Test Cases

#### Test 1: Simple Frontend Task

```text
User: "Create a dark mode toggle button"
Expected: Auto-invoke frontend-specialist
Verify: Response shows "Using @frontend-specialist"

Test 2: Security Task

User: "Review the authentication flow for vulnerabilities"
Expected: Auto-invoke security-auditor
Verify: Security-focused analysis

Test 3: Complex Multi-Domain

User: "Build a chat application with real-time notifications"
Expected: Auto-invoke orchestrator
Verify: Multiple agents coordinated (backend, frontend, test)

Test 4: Bug Fix

User: "Login is not working, getting 401 error"
Expected: Auto-invoke debugger
Verify: Systematic debugging approach

Performance Considerations

Token Usage

• Analysis adds ~50-100 tokens per request
• Tradeoff: Better accuracy vs slight overhead
• Overall SAVES tokens by reducing back-and-forth

Response Time

• Analysis is instant (pattern matching)
• No additional API calls required
• Agent selection happens before first response

User Education

Optional: First-Time Explanation

If this is the first interaction in a project:

💡 **Tip**: I am configured with automatic specialist agent selection.
I will always choose the most suitable specialist for your task. You can
still mention agents explicitly with `@agent-name` if you prefer.

Debugging Agent Selection

Enable Debug Mode (for development)

Add to GEMINI.md temporarily:

## DEBUG: Intelligent Routing

Show selection reasoning:

- Detected domains: [list]
- Selected agent: [name]
- Reasoning: [why]

Summary

intelligent-routing skill enables:

✅ Zero-command operation (no need for /orchestrate) ✅ Automatic specialist selection based on request analysis ✅ Transparent communication of which expertise is being applied ✅ Seamless integration with existing workflows ✅ Override capability for explicit agent mentions ✅ Fallback to orchestrator for complex tasks

Result: User gets specialist-level responses without needing to know the system architecture.

---

Next Steps: Integrate this skill into GEMINI.md TIER 0 rules.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: matthewbspeicher
• Source: matthewbspeicher/remembr-dev
• License: MIT

Install and usage instructions live in the source repository linked above.