using-sales

Routing ambiguous sales requests requires a router that directs tasks to the narrowest applicable child skill, prioritizing concrete outputs like meeting prep before outbound drafts to minimize misrouting and accelerate workflows.

Prioritizing sales tasks involves enforcing exactly one primary child skill per request, ranking concrete outputs by placing meeting prep before outbound draft before general account research to guide the workflow.

Handling missing child skills uses a safe fallback mechanism that prompts you to install the missing skill and then routes the sales task accordingly, ensuring the request still reaches the correct workflow.

Yes, a single router can evaluate ambiguous sales requests across account research, call preparation, and outbound drafting, selecting exactly one specialized child skill to handle the specific task.

You need a routing skill when sales requests are ambiguous and could match multiple workflows, requiring boundary references to enforce correct routing rules and direct tasks to the narrowest specialized skill.

Sales task routing fails when boundaries are unclear, which is why the router references children boundaries to enforce exactly one primary child skill or a no-skill option, preventing misrouting.