legion:intent-router

Parse and normalize semantic intent flags for Legion build and review workflows.

72|8|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/9thLevelSoftware/legion --skill legion-intent-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion:intent-router
Source: https://github.com/9thLevelSoftware/legion/tree/main/skills/intent-router
Command: npx skills add https://github.com/9thLevelSoftware/legion --skill legion-intent-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires minimatch, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Parses semantic intent flags, validates combinations, and routes to appropriate team templates — the semantic flag interpreter for /legion:build and /legion:review.

Core Features & Use Cases

  • Flag parsing and normalization for --just-* and --skip-* flags
  • Conflict detection and validation against intent-teams.yaml rules
  • Team template resolution and domain-to-agent mapping for execution planning
  • Execution mode detection to support ad-hoc or filtered execution
  • Natural language intent parsing (NL) integration to convert plain language requests into legion commands

Quick Start

Run /legion:build --just-harden to execute a hardened build workflow.

Frequently Asked Questions about legion:intent-router

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

FAQPage Schema
How do I parse and validate semantic intent flags for build workflows?

Semantic intent flags are parsed and validated by normalizing --just-* and --skip-* flags, detecting conflicts, and checking combinations against intent-teams.yaml rules to drive workflow orchestration.

What is semantic routing for intent-based build and review workflows?

Semantic routing interprets intent flags to map domains to specific agents and resolve team templates, enabling targeted execution planning for build and review processes based on normalized flag combinations.

How do I convert natural language requests into legion commands?

Natural language intent parsing converts plain language requests into legion commands, allowing you to trigger workflows like a hardened build by running /legion:build --just-harden instead of manual flag configuration.

Can I use minimatch and yaml for intent flag conflict detection?

Yes, the intent router relies on minimatch and yaml dependencies to parse intent-teams.yaml rules and validate flag combinations, ensuring that conflicting semantic flags are detected before execution.

How do I resolve team templates and map domains to agents for execution?

Team template resolution maps validated intent flags to specific agent configurations using intent-teams.yaml, enabling domain-to-agent mapping and execution mode detection for ad-hoc or filtered workflow execution.

Why does my intent flag validation fail during workflow orchestration?

Intent flag validation fails when conflicting --just-* and --skip-* flags are detected, or when combinations violate the rules defined in intent-teams.yaml during the normalization and conflict detection process.