An AI pit-wall strategy agent for Jira teams, built on Atlassian Forge + Rovo.
Rovo Race Engineer analyzes Jira sprint and release “telemetry” and answers one critical question for delivery teams:
“What are the top 3 race-critical risks that will block our release, and what should we do next?”
Inspired by Formula 1 race engineers who monitor live data and make split-second strategy calls, Race Engineer brings the same decision-making clarity to software delivery.
Built for Codegeist 2025 – Atlassian Forge + Rovo Challenge.
Before every release, teams spend 30–60 minutes in reviews debating:
- Which issues will actually block us?
- What’s risky vs. just noisy?
- Where should we focus right now?
Meanwhile, Jira already contains the signals:
- Priority
- Time in status
- Linked bugs or incidents
- Aging, stalled work
But Jira doesn’t synthesize these into actionable risk insight.
Rovo Race Engineer is an AI race engineer for Jira.
It:
- Pulls issue telemetry from a sprint or release
- Analyzes risk factors (priority, age, dependencies, incidents)
- Produces a ranked Top-3 list of race-critical risks
- Explains why each item is risky and what to do next
All in one concise response — no dashboards, no noise.
Top 3 race-critical risks for Release 1.0
-
DEV-42 – Payment retry logic
- High priority, blocked for 6 days
- Linked to 2 unresolved bugs
- Suggested action: Prioritize fix before release cutoff
-
DEV-17 – Auth service refactor
- Large scope, late-stage changes
- High regression risk
- Suggested action: Isolate changes or defer to next release
-
DEV-29 – Database migration
- External dependency approval pending
- Linked to a prior production incident
- Suggested action: Escalate dependency immediately
This is the same decision support a pit-wall gives a driver during a race.
Forge App
- Deployed on Jira Cloud
- Uses Jira REST APIs to fetch issue data
Rovo Agent Module
- Defines the Race Engineer agent persona and prompt
- Accepts structured telemetry and generates ranked insights
Forge Action
- Aggregates Jira issue data
- Computes risk signals
- Returns structured context to Rovo
LLM via Rovo
- Ranks risks
- Explains reasoning
- Suggests next actions in plain language
-
manifest.yml
Forge app configuration, permissions, and Rovo agent definition -
src/index.js
Core risk analysis logic (analyzeJiraRisks) -
static/race-ui/
Optional Jira global page placeholder -
AGENTS.md
Rovo agent prompt and behavior definition
- Jira Cloud site
- Node.js 18+
- Forge CLI
git clone https://github.com/Shyamistic/race-engineer.git
cd race-engineer
npm install
Install Forge CLI if needed:
bash
Copy code
npm install -g @forge/cli
Register and deploy:
bash
Copy code
forge register
forge deploy
Install into Jira:
bash
Copy code
forge install --product jira --site YOUR-SITE.atlassian.net
🤖 Using the Agent (Rovo)
Once Rovo is enabled on your Jira site:
Open Rovo in Jira
Select the Rovo Race Engineer agent
Ask:
“What are the top 3 race-critical risks in the current sprint?”
“What are the biggest risks for Release 1.0?”
The agent will analyze live Jira data and respond with ranked, actionable insight.
⚠️ Rovo Availability Note
Rovo is not yet enabled on all Atlassian Cloud tenants.
If Rovo does not appear on your site:
Ask your Atlassian org admin to verify Rovo availability
Or join the Rovo early-access waitlist via Atlassian
This app is Rovo-ready and will surface immediately once Rovo is enabled on a site.
Judges can install and test it on any Rovo-enabled Atlassian environment.
🔮 Future Enhancements
Multi-project and cross-release risk aggregation
Incident-aware release blocking
Custom risk scoring heuristics per team
🏁 Why This Matters
Race Engineer helps teams:
Reduce pre-release uncertainty
Focus effort where it actually matters
Make faster, clearer delivery decisions
Just like in Formula 1, races are not lost because of lack of data — they’re lost because teams fail to interpret it in time.
📄 License
MIT