subagent-routing

Analyze work-shape classifications and persona suitability to recommend subagent routing.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/lukeivers/loam --skill subagent-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-routing
Source: https://github.com/lukeivers/loam/tree/main/plugins/dev-sdlc/skills/subagent-routing
Command: npx skills add https://github.com/lukeivers/loam --skill subagent-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides precise recommendations for routing work-shapes to appropriate subagent personas, improving automation efficiency and consistency in AI dispatch workflows.

Core Features & Use Cases

  • Work-shape classification: Determines the nature of the dispatched task to suggest suitable personas.
  • Persona match validation: Checks if the recommended persona matches the task's work-shape and constraints.
  • Use Case: When authoring a dispatch brief for an amendment cycle, this Skill recommends routing to loam-builder or defaults to general-purpose when boundary conditions are detected, streamlining the decision process.

Quick Start

Use the subagent-routing skill to identify the best subagent persona for a given task based on its scope and constraints.

Frequently Asked Questions about subagent-routing

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

FAQPage Schema
What is subagent routing in AI dispatch workflows?

Subagent routing recommends appropriate AI agent personas for dispatch tasks by analyzing work-shape classifications and boundary conditions. It evaluates task scope and tool restrictions to select the correct agent type for workflow automation.

How do I determine the best agent persona for a specific task scope?

To determine the best agent persona, classify the task's work-shape and validate persona suitability against boundary constraints. This process matches the task scope to the correct agent profile, streamlining dispatch decisions for automation workflows.

When should I default to a general-purpose agent during task dispatch?

You should default to a general-purpose agent when boundary conditions are detected during work-shape classification. If the task scope violates specific persona constraints or tool restrictions, the routing logic falls back to a general dispatch profile.

Can I use automated routing for complex workflow automation tasks?

Yes, you can use automated routing for complex workflow tasks by evaluating work-shape classifications and persona match validation. The routing mechanism handles boundary checks and tool restrictions to maintain dispatch accuracy across varying automation scopes.

What are the limitations of using persona-based routing for task automation?

The limitation of persona-based routing is that boundary conditions can invalidate specific persona matches, forcing a default to general-purpose agents. Task scope and tool restrictions must align with the persona profile to maintain routing accuracy.