ask

Routing vague requests automatically involves classifying the user intent and dispatching it to the correct skill. This Skill handles multiple intents, performs brief clarification when needed, and executes chained skill dispatch with verbose progress logging.

Classifying multiple intents requires analyzing the request and planning primary and follow-up skill dispatch. This Skill identifies multiple intents, performs a brief clarification phase if needed, and routes them to chained skills with a clear execution plan.

Activity-feed logging for routed workflows assigns a one-time ephemeral session ID to track progress. The Skill writes events to the activity feed and produces verbose progress logs, ensuring full traceability for classified and dispatched requests.

Manual triage is not required before dispatching requests to chained skills. This Skill automatically classifies vague requests, plans the dispatch sequence, and handles the brief clarification phase, reducing manual triage and speeding up workflows.

Request classification for intake routing can be used without custom logic by providing a vague request directly. The Skill automatically classifies the intake, clarifies if needed, plans the workflow, and dispatches it to the correct skill.

Automatic request routing should not be used when requests lack the contextual clarity needed for brief clarification or when workflows do not support chained skill dispatch. It is designed for vague requests that require classification and traceable activity-feed logging.