Create with Rovo Prompt Library

[#1]

Create with Rovo: Scenario Prompt Library

NOTE: These scenarios were created for a live workshop and work with OneAtlassian demo instances.

If you don't have a OneAtlassian Demo, you can try out these prompts with details specific to your company's Rovo-enabled instance. 

You'll see three sections under each scenario:

• Prompt - the prompt for you to try
• Content type - what you're creating
• Resources - pages, information, and context corresponding to the prompt that can be found in your OneAtlassian demo instance. 

Tip: Create with Rovo can be accessed from the create menu in confluence or by typing create.rovo.com in your browser if you get lost.

Example Team	Example Scenario
Marketing	Scenario 1: Campaign Planning
Marketing	Scenario 2: Customer / competitive research
Product	Scenario 3: Define product requirements
Product	Scenario 4: Stakeholder mapping
HR / HR Ops	Scenario 5: Onboarding
HR / HR Ops	Scenario 6: Onboarding / offboarding
Program Management	Scenario 7: Project planning
Program Management	Scenario 8: Program Brainstorm
IT	Scenario 9: Develop troubleshooting guide
IT	Scenario 10: Service Management Documenatation

Scenario 1: Campaign Planning

Prompt:

Develop a comprehensive marketing strategy for our new [product/feature

name] using the target audience, the problems it solves, its usage, and

core purpose highlighted here: [Confluence page link or description].

Create a campaign with traditional and digital marketing tactics,

including social media engagement, influencer partnerships, public

relations, and advertising to maximize reach and impact. Establish clear

objectives and define KPIs to track the campaign's success and

effectiveness.

Content Type: Confluence doc (product) → Confluence doc (marketing)

Resources: Works with Confluence “mobile development” space → “Mobile app version 2.0 - Requirements List” Confluence page

Scenario 2: Customer / Competitive Research

Prompt:

Create a database to organize user research findings, insights, and

supporting materials for [product or feature]

AND/OR

Set up a research database for [project or feature] to log competitor

insights, feature comparisons and market trends for ongoing analysis.

Content Type: Database

Resources: Works with any “product/feature” that exists in the demo environment and get a good output, for example, "mobile app"

Scenario 3: Define product requirements

Prompt:

Create a database to capture product requirements for [project or

feature], including user stories, acceptance criteria, and priority. Use

this [Confluence page link or description] as a source for the database.

Content Type: Database

Resources: Works with Confluence → “mobile development” space → “mobile app

version 2.0” document

Scenario 4: Stakeholder Mapping

Prompt:

Generate a stakeholder map whiteboard for [product / feature] including

internal teams (engineering, product, customer success), external

partners, and customer segments with influence/interest ratings

Content Type: Whiteboard

Resources: Works with any “product/feature” and get a good output

Scenario 5: Onboarding

Prompt:

Create a Confluence page with an onboarding checklist for new team

members joining the [project]. Include a table with the most updated

documents, summarize the content of each document, and provide a link to

each document.

Content Type: Project → Page

Resources: Works with Projects → any on track “project”

Scenario 6: Onboarding / offboarding

Prompt:

Generate a flowchart diagram to map out the employee onboarding and

offboarding process detailed on this page: [Confluence page link or

description].

Content Type: Confluence Page → Whiteboard

Resources: Works with Confluence → “Employee Onboarding” space → “action items - draft” confluence doc 

Scenario 7: Project planning

Prompt:

Create a clear project kickoff plan for "Mobile App 2.0"

Please include the main goals, important milestones, who’s responsible for

what, a rough timeline, and any risks we should watch out for. Also add a

section for open questions so the team can review and discuss.

Content Type: Confluence Doc 

Resources: Works with Confluence “mobile development” space, Jira "platfrom development" space, Jira "core experiment" space

Scenario 8: Program Brainstorm

Prompt:

Take the content from our to-do work item [link to item] and create a

whiteboard to facilitate a brainstorming workshop between stakeholders to

generate ideas for the program kick off. Be sure to include instructions

for participants.

Content Type: Work Item → Whiteboard

Resources: Works with Jira → “marketing content” space → To-do → MC-48

Scenario 9: Develop troubleshooting guide

Prompt:

Create a Confluence page with actionable troubleshooting steps using

details from the conversation in this [ticket link]. Provide a brief

overview of the issue, summarize key points and context needed to

understand the troubleshooting steps, and create clear and distinct steps

to address this issue and similar requests.

Content Type: Ticket/Work Item → Confluence Page

Resources: Works with Jira → “marketing software development” space → MSD-4

Scenario 10: Service Management documentation

Prompt:

Create a Confluence page that outlines a risk management strategy using

details from open facilities requests in this space [ticket link]. Provide

a brief overview of the risks, summarize key points and context needed to

understand the strategy recommendation, create clear and distinct steps to

address the issue, and suggest how this can inform similar risk strategy

approaches.

Content Type: Work Items List → Confluence Page

Resources: Works with Jira Service Management -> “facilities” space → all open work items

[Peter_DevSamurai]

Hi @Caity Belta ,

Thank you for the informative suggestions, I did't know Rovo could perform Scenario #2, I tried it and it worked beautifully! Have a great week ahead!