Skill Router

Activate this skill first, resolve the request into a skill, then hand the work to that skill. Routing is a decision, not a menu: one primary owner, at most two supporting skills, and a stated order.

When to use

• The request does not name a skill, or names a technology instead of a workflow.
• The request is broad, spans domains, or is a new project, new feature, or new service.
• Something is broken, slow, unsafe, or failing review and the correct discipline is not obvious.
• The user asks which skill, which order, or where to start.

When not to use

• The user named a specific skill: load it directly.
• The task is a one-line edit, a lookup, or a command: answer it.
• Another skill was already activated and is mid-work: finish that work instead of re-routing.

Core algorithm