What does your Rovo Agent production-readiness checklist actually look like? Sharing mine - looking

[Prashanth]

Hi All,

I'm currently building and refining a production-readiness framework for Rovo Agent deployments in enterprise environments and wanted to open it up for critique from the community.

My current checklist covers five areas:

1. Documented and reviewed knowledge boundaries with no unnecessary over-scoping
2. Conservative action boundaries (write actions requiring human confirmation gates)
3. Structured reasoning with source citation requirements for every claim
4. Graceful degradation when information cannot be found (no speculation)
5. Explicit escalation paths directing users to named teams or channels when the agent reaches its scope boundary

What I'm less confident about is the testing protocol.

How are people systematically validating permission containment across multiple access levels before declaring an agent production-ready?

And how are teams handling versioning and change management for system prompts?

For example:

- New Confluence spaces added
- Existing permissions changed
- New knowledge sources introduced
- Agent instructions updated

Are these treated as informal configuration changes, or are they going through the same governance and approval process as other production changes?

My suspicion is that prompt and knowledge-boundary changes often receive less governance scrutiny than they should.

Would love to hear what has worked (or not worked) in your own deployments.

[Remy RAMIREZ]

Hello @Prashanth 
For the prompt versioning I'm doing it manually with JIRA tickets where I write the changes and I add in the description the number of version that redirect to a release note page. 
A feature should come soon with versioning: https://jira.atlassian.com/browse/ROVO-93

For the testing it's quite manual to potentially update the testing dataset

[Prashanth]

Hi @Remy RAMIREZ 

Agent testing is manual today, can't help much here,  its like sculpting until we get the desired statue. Having said that, Test cases can be auto generated for a prompt by a prompt. Try it once.

can you help me understand this please , what is this ROVO project about, looks interesting, https://jira.atlassian.com/projects/ROVO/issues/ROVO-261?filter=allopenissues, you added me as a user but hope you didn't give me any permissions yet.

Can you elaborate please.

[Remy RAMIREZ]

From my understanding it's a public JIRA Board from atlassian to share feedbacks / feature request with the community and this board is for ROVO. 

There is no specific roles or permissions