workflow-router

Route Codex tasks to the smallest suitable model and effort tier.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/koala-man-64/helpful-scripts --skill workflow-router-koala-man-64
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-router
Source: https://github.com/koala-man-64/helpful-scripts/tree/main/codex-workflow/skills/workflow-router
Command: npx skills add https://github.com/koala-man-64/helpful-scripts --skill workflow-router-koala-man-64

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Delegating Codex work without a routing policy wastes compute on trivial tasks or under-provisions high-risk production changes. This Skill maps each task's shape and risk directly to the smallest suitable model and effort tier. ## Core Features & Use Cases - Task-shaped routing: Sends mechanical transformations to Luna at low effort, investigation and code review to Terra at medium effort, and architecture, security, or production-risk work to Sol at high effort. - Delegation constraints: Enforces that a child route is strictly lower than its parent in both model order (Sol > Terra > Luna) and effort order (ultra > high > medium > low), and blocks Luna/low parents from delegating. - Catalog scenarios: Records explicit parent and child routes for narrow fixes, standard features, cross-repo contract changes, CI incidents, and production or IaC changes. - Use Case: When planning a cross-repo contract change with a CI incident, route the work to a Sol/high owner with Terra/medium investigation and QA children instead of escalating everything to the largest model. ## Quick Start Use the workflow-router skill to select the smallest suitable model and effort for this task.

Frequently Asked Questions about workflow-router

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

FAQPage Schema
How do I choose the right model for a Codex task?▼

Match the task shape and risk directly to a tier: mechanical or bounded transformations go to Luna at low effort, investigation and code review go to Terra at medium effort, and architecture, security, or production-risk work goes to Sol at high effort.

How does task delegation work between model tiers?▼

A child route must be strictly lower than its parent in both model order (Sol > Terra > Luna) and effort order (ultra > high > medium > low). A Luna/low parent cannot delegate at all, and routing goes directly to the smallest permitted model rather than climbing a tier ladder.

When should a task be routed to Sol at high effort?▼

Route to Sol at high effort when the work involves architecture, security, incidents, migrations, data integrity, or production risk, and only when the parent route permits it. Production or IaC changes use a Sol/high owner with Terra/medium children.

Can a Luna low-effort parent delegate subtasks?▼

No, a Luna/low parent cannot delegate. Delegation requires the child to be strictly lower than the parent in both model and effort order, which is impossible from the lowest tier.

What are the limitations of the delivery-orchestrator-agent route?▼

The delivery-orchestrator-agent is an unresolved fork, so in critical work it acts only as a coordination role, not a runnable canonical skill pin. Skill pins must be kept separate from the people or child routes selected for a task.