smart-router

Cross-repo workflow routing is automated by dynamically selecting execution phases based on repository changes. A config-driven engine uses JSON configurations to define phases and parallelization rules, coordinating specialized subagents across multiple repositories.

Config-driven phase orchestration centralizes decision-making to choose which workflow phases, such as discovery or implementation, to run. It coordinates parallel or sequential execution across repositories by delegating work to specialized subagents defined in a JSON configuration.

Parallel and sequential phases are run using a shell script router that reads JSON-configured parallelization rules and dependencies. This coordinates specialized subagents to execute tasks across specified repositories in the correct order or simultaneously.

Yes, jq is required as a dependency for the config-driven routing engine. The shell scripts use jq to parse the JSON configurations that define phases, parallelization rules, and subagent orchestration across repositories.

Yes, shell scripts orchestrate subagents by dynamically selecting phases based on detected changes. The router applies a JSON configuration to delegate work to specialized subagents, coordinating parallel or sequential execution across multiple repositories.

Dynamic phase selection should be avoided for single-repo tasks lacking varying change types. This orchestration engine specifically solves cross-repo workflow routing by dynamically selecting phases based on changes across multiple repositories.