We do have what you call Items and Shouts in the form of an agent communication system and a Linear style issue tracker that agents and humans use together.
In our case everything around orchestration is discussed with the agent itself and they take action for the user via our CLI. We found any UI to prescribe how teams of agents should coordinate too clunky. So in our case you just tell the agent: "every codex luna max implementer gets an opencode muse spark reviewer. when a subtree is done, review with opus high.". It then sets up the graph and the system enforces the rules.
We also open-sourced a similar system called https://github.com/madeinorbit/podium
We do have what you call Items and Shouts in the form of an agent communication system and a Linear style issue tracker that agents and humans use together.
In our case everything around orchestration is discussed with the agent itself and they take action for the user via our CLI. We found any UI to prescribe how teams of agents should coordinate too clunky. So in our case you just tell the agent: "every codex luna max implementer gets an opencode muse spark reviewer. when a subtree is done, review with opus high.". It then sets up the graph and the system enforces the rules.
It works really well for us.