workflow-router

Engineering task routing for multi-domain requests is automated by classifying the request, selecting a primary and supporting skill, and ordering execution based on dependencies. This ensures evidence or design phases occur before mutation, followed by validation.

Ambiguous engineering tasks are allocated to the correct skill set through request classification based on deliverable and mutation risk. The system automatically selects one primary and at most one supporting skill to handle the execution.

Ordered execution for engineering workflows sequences tasks by dependency, ensuring evidence or design tasks run before mutation, followed by validation. This prevents structural errors by enforcing a strict execution order.

Complex task routing is supported through an exhaustive route table designed for multi-domain requests. This provides a comprehensive map to direct intricate engineering tasks to the appropriate configured skills.

Automated task routing requires appropriate skill configuration and task context to function correctly. You must configure the target skills and provide the necessary request context before initiating the routing process.

Automated workflow routing should not be used when appropriate skill configurations are missing or task context is incomplete. The system relies on these elements to classify requests and order execution dependencies accurately.