task-route

/task-route

Use this skill when the user wants to define a preferred target route for a task type.

Compatibility forms:

• /task-route ...
• /octoswitch:task-route ...

When exported as a plugin artifact, publish this command under the octoswitch namespace.

Goal

Store a recommendation that future delegation can use when choosing routes.

This is a preference-setting command, not an execution command.

Supported forms

/task-route <task-kind> --target <group>
/task-route <task-kind> --group <group>

Examples:

/task-route implementation --target Sonnet
/task-route review --target Opus
/task-route search --target Haiku

Intended semantics

These rules are recommendations, not hard overrides.

Suggested priority:

1. explicit target in the current task
2. task-route preference
3. default active member of the target group

Recommended task kinds

Start with a small, stable set:

• implementation
• review
• search
• debugging
• refactor

Current status

OctoSwitch has a concrete MVP implementation for task-route preferences.

Current implementation surface:

• Settings -> enable Skills
• Main UI -> Skills tab
• persisted task-route preference records
• add / edit / delete task-route entries
• optional prompt template per task kind

At the Claude Code slash-command layer, this skill acts as the routing preference contract. The storage and editing side exists in OctoSwitch.

First-run onboarding

If this looks like the first time task-route preferences are being configured, recommend a minimal starting set instead of forcing the user to design the whole route table up front.

Recommended onboarding message:

This looks like the first time task-route preferences are being configured.
A minimal recommended starting set is:

/task-route implementation --target Sonnet
/task-route review --target Opus
/task-route search --target Haiku

After that, /delegate can use those preferences when choosing routes and subagents.

Onboarding behavior

If no task-route preferences exist yet:

1. explain that a small initial mapping is enough to get started
2. recommend the minimal default mapping
3. present the mapping as editable preferences, not fixed system rules

Important rule

These initial values are recommended defaults, not mandatory hardcoded values.

If the user already has a preferred route layout, that preference should win.

First configuration guidance

If the user has not configured any task-route preferences yet, recommend this minimal starting set:

/task-route implementation --target Sonnet
/task-route review --target Opus
/task-route search --target Haiku

Present these as recommended defaults, not mandatory values.

Recommended explanation to users

When explaining the command set, prefer this wording:

/delegate handles execution.
/task-route defines default route preferences used by /delegate.

Avoid presenting /task-route as an execution entrypoint.