route

Automates routing of user actions to the appropriate agent based on project state, using STATE.md and filesystem scan for pending work items and interrupts, ensuring correct context transfer for resumed or new tasks.

201|19|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/fabriqaai/specs.md --skill route-fabriqaai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route
Source: https://github.com/fabriqaai/specs.md/tree/main/src/flows/fire/agents/orchestrator/skills/route
Command: npx skills add https://github.com/fabriqaai/specs.md --skill route-fabriqaai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the decision of which agent should handle a task by evaluating the current project state and state.yaml, eliminating manual routing.

Core Features & Use Cases

  • Stateful routing: Reads .specs-fire/state.yaml and performs a filesystem scan for intents and work-items to determine the next agent.
  • Dynamic orchestration: Routes to builder-agent, planner-agent, or other components based on detected state, active runs, and pending work items.
  • Safe context propagation: Ensures the correct context is passed to the chosen agent to resume or start work seamlessly.

Quick Start

Trigger the orchestrator to evaluate the project state and route to the appropriate agent using the project's existing specsmd FIRE workflow.

Frequently Asked Questions about route

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

FAQPage Schema
How do I route user actions to the correct agent based on project state?

Route user actions by reading state.yaml and scanning the filesystem for intents and work-items to determine the next agent. This state-first approach ensures proper context is passed to the target agent.

What is state-first routing in adaptive FIRE workflows?

State-first routing in adaptive FIRE workflows evaluates state.yaml and pending work items to dynamically orchestrate execution paths. It determines whether to route to a builder-agent, planner-agent, or other components.

How do I start workflow orchestration using state.yaml?

Start workflow orchestration by triggering the orchestrator to evaluate your project state. The Skill reads .specs-fire/state.yaml and performs a filesystem scan to route to the appropriate agent.

Does this routing approach work with existing specsmd FIRE workflows?

Yes, this routing approach works with existing specsmd FIRE workflows. It applies to adaptive FIRE workflows where intents, work items, and runs determine execution paths automatically.

Why does agent routing require a filesystem scan for intents and work-items?

Agent routing requires a filesystem scan to detect active runs and pending work items accurately. This ensures the correct context is passed to the chosen agent to resume or start work seamlessly.