agent-routing

Routing NestJS backend requests involves analyzing task keywords and automatically assigning them to specialized agents. This Skill uses keyword-based decision logic to map complex multi-domain requests—such as Redis caching, TypeORM migrations, BullMQ queues, and CQRS—to the correct expert, then selects execution strategy (SINGLE, SEQUENTIAL, PARALLEL, or DIRECT) for optimal task completion.

Yes. The Skill supports execution strategy selection across SINGLE_EXPERT, SEQUENTIAL, PARALLEL, and DIRECT routing modes. You provide a backend request containing multiple domains—Redis, TypeORM, BullMQ, microservices, testing—and the Skill generates subagent prompts and coordinates execution, deciding whether tasks run in parallel for speed or sequentially for dependency ordering.

The routing system covers Redis caching, TypeORM entities and migrations, BullMQ queues, CQRS patterns, microservices architecture, testing frameworks, and Fastify integration. It recognizes keywords for each domain and routes requests to specialized agents equipped to handle those specific technologies within NestJS backend development.

Keyword-based routing analyzes incoming backend requests for domain indicators—redis, typeorm, bullmq, cqrs, microservices, testing, fastify—and matches them to expert agents. The Skill applies MCP-driven decision logic to determine routing paths and execution strategy, generating specialized prompts for each assigned agent.

No. The Skill automates agent assignment and execution planning. Provide your multi-domain backend request, and the system analyzes keywords, routes to appropriate experts, and automatically selects execution strategy—whether tasks need single expert focus, sequential chaining, or parallel execution—without manual intervention.

SEQUENTIAL execution runs assigned agents one after another, preserving task dependencies and order. PARALLEL execution runs agents simultaneously when tasks are independent, reducing total execution time. The Skill selects the optimal strategy based on task analysis and dependencies within your multi-domain backend request.