route

Read state.yaml and filesystem scans to route work items to agents.

3|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/4tikhonov/the-minority-report --skill route-4tikhonov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: route
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/orchestrator/skills/route
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill route-4tikhonov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The route skill analyzes the current project state and directs users to the most appropriate agent based on verified state information.

Core Features & Use Cases

  • Discover and read state.yaml and the filesystem to identify pending work items and active runs.
  • Route decisions to builder, planner, or run-execute agents based on current context and workflow rules.
  • Automatically handle transitions between intents, item planning, and execution, ensuring progress with minimal manual intervention.

Quick Start

To use this skill, ensure your project contains a .specs-fire/state.yaml and the intents structure. Then trigger the orchestrator to scan the state, reconcile items, and route to the appropriate agent as soon as a run is active or new work items are detected.

Frequently Asked Questions about route

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

FAQPage Schema
How do I route tasks to the right agent based on project state?

Agent orchestration uses state.yaml and intents to govern work items, scanning the filesystem to identify pending runs and automatically route decisions to the appropriate builder, planner, or execution agent based on verified project state.

What do I need to set up before using dynamic agent orchestration?

You need a .specs-fire/state.yaml file and the intents structure in your project. These provide the verified state information required to route work items to the appropriate builder, planner, or run-execute agents.

How does agent routing handle transitions between planning and execution?

It applies workflow rules to the current context, automatically handling transitions between intent discovery, item planning, and execution to ensure continuous progress with minimal manual intervention.

When should I use an automated routing skill for agent orchestration?

Use it for dynamic agent orchestration pipelines where state.yaml and intents govern work items, guiding runs from discovery to execution with minimal manual intervention.

Can I route work to a specific builder or planner agent based on file system scans?

Yes, the skill performs file system scans for intents and work-items, using the verified state information to decide routing and provide context to the target builder, planner, or run-execute agent.