route

Evaluate task complexity and scope to select an optimal workflow.

Updated Mar 23, 2026

Search Tags:#automation #workflow #planning #spec #orchestrator #route

Ready to run

npx skills add https://github.com/mattphanm/Codex-Agentic --skill route-mattphanm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: route
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/route
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill route-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route routing decisions by analyzing task complexity and scope to select the appropriate workflow (oneoff-vibe, oneoff-spec, orchestrator, refactor, or journal-only).

Core Features & Use Cases

Analyze task complexity to suggest an optimal workflow.
Consider scope, dependencies, and cross-workstream impact to guide planning.
Provide a structured routing decision with rationale and next steps for cross-team alignment.

Quick Start

Provide a task description and let Route determine the best workflow and generate a routing decision.

Frequently Asked Questions about route

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

FAQPage Schema

How do I automate workflow routing for tasks with different complexity and scope?▼

Automate workflow routing by analyzing task complexity, scope, and dependencies to select the optimal workflow. Route evaluates these factors to return a structured routing decision with rationale, estimated scope, files, and recommended next actions.

What's the best way to choose between spec, orchestrator, and refactor workflows for a new task?▼

Choosing the right workflow requires evaluating task complexity and cross-workstream impact. Route assesses these dimensions to recommend oneoff-vibe, oneoff-spec, orchestrator, refactor, or journal-only, defaulting to the most appropriate option when ambiguity exists.

How do I plan task dependencies and scope across multiple workstreams?▼

Plan task dependencies by analyzing scope and cross-workstream impact to guide your workflow selection. Route evaluates these parameters to produce a structured routing decision, ensuring cross-team alignment through recommended next actions and rationale.

When should I use a journal-only workflow instead of a full orchestrator workflow?▼

Use a journal-only workflow for simple tasks with minimal scope or complexity. Route evaluates task parameters to determine when a full orchestrator is unnecessary, defaulting to lighter workflows when ambiguity exists to prevent over-planning.

Can I get a structured rationale for why a specific workflow was selected for my task?▼

Get a structured rationale by analyzing task complexity and scope to select a workflow. Route returns a routing decision that explicitly includes the chosen workflow, rationale, estimated scope, affected files, and recommended next actions.

Why does my task planning workflow default to oneoff-vibe when requirements are ambiguous?▼

Task planning defaults to the most appropriate workflow when ambiguity exists. Route evaluates task complexity, scope, and dependencies to select the best fit, defaulting to lighter workflows like oneoff-vibe to avoid unnecessary overhead for under-specified tasks.