How to design a multi-agent architecture with Rovo (orchestrator + specialized agents)?

[Giuseppe Torraco]

Hi everyone,

I’ve been experimenting with Rovo agents and I’ve noticed that they perform really well when they are focused on a single, well-defined task.

However, when I need to execute more complex, multi-step workflows, a single agent doesn’t seem sufficient. My current idea is to design an architecture composed of:

• multiple specialized Rovo agents (each responsible for a specific task), and
• one “orchestrator” Rovo agent that coordinates the overall flow and delegates tasks to the others.

My questions are:

• What is the recommended approach to implement this kind of multi-agent architecture with Rovo?
• Is there any best practice for orchestrating multiple agents (e.g., chaining, event-based triggers, shared context, etc.)?
• How can agents effectively share context or state between each other?
• Are there any limitations or pitfalls I should be aware of when designing this setup?

Any guidance, examples, or real-world experiences would be greatly appreciated.

Thanks in advance!

[Matteo Vecchiato]

Hi @Giuseppe Torraco ,

Thank you for your post. I suggest to post your question also in the Rovo channel: https://community.atlassian.com/forums/Rovo-questions/qa-p/rovo-atlassian-intelligence-questions?sort=recent&unanswered=true 

Kind regards