Skill Router

Route a user request to the smallest useful skill set. Prefer one primary skill. Use a short ordered set only when the request genuinely spans independent domains.

When to use

• User asks which skill applies to a request
• A request appears to match multiple skill descriptions
• A skill description or trigger list is causing routing confusion
• You need to explain why one adjacent skill is a better fit than another

When NOT to use

• Creating or rewriting a skill - use skill-creator
• Batch improving a collection - use skill-refiner
• Capturing feature ideas or competitive backlog items - use roadmap
• Implementing domain work after routing - use the selected domain skill
• Routing requests to understand or optimize a skill's own trigger text - use skill-creator (Mode 4)