Level 2 · Intermediate
Intermediate Forge
Extend the same app: paste menu-meeting notes on a Jira page, and a queue, Forge LLM and a consumer turn them into dish tickets, a Confluence menu of record and a handoff to a Rovo agent.
What you’ll build
Menu desk
Receipt 3f9a1c2e: Done.
- KIT-24 Pad thai
- KIT-25 Tom yum soup assign-to-agent
- KIT-26 Green curry
- KIT-27 Mango sticky rice
Open “Menu of record: Spring menu” in Confluence
A page in Jira called Menu desk, where the head chef pastes the notes from a menu meeting. The desk answers at once with a receipt. Behind it, a queue and a consumer take over: Forge LLM picks out the dishes, the app writes one ticket per dish and a Confluence page that lists them, and every ticket still gets the Level 1 recipe card.
Then the app hands researched dishes on: a trigger at the pass, and a Rovo agent of your own that uses the same supplier. You finish by comparing it with an agent built in Rovo Studio, with no code.
Plan on about four hours, with breaks. It starts from the finished Level 1 app; download it from the first lesson if you need to.
What each lesson adds
Lesson 1: a Custom UI page in Jira, the menu desk, sends meeting notes to its own resolver.
In the kitchen: Lesson 1: the head chef drops the meeting notes at the menu desk, your own fitted counter.
Runs in the browser · Front of house
Global page The menu desk
A full page of your own in Jira’s Apps menu. Here the head chef pastes the notes from a menu meeting.
The desk where the head chef drops the notes from the menu meeting.
Select any box in the diagram to see what it is.
Open the menu desk. A Custom UI page, served from your own HTML and JavaScript, sends the notes to its resolver through the bridge.
Accept fast, cook later. The resolver saves the menu in the Key-Value Store, puts only its id on a queue, and hands back a receipt.
Accept fast, cook later. A consumer function, the prep cook, takes the slip down later and writes tickets as the app.
Bring in the sous-chef. Forge LLM reads the notes and lists the dishes. The prep cook writes one ticket each and ticks them off, so a retry never writes one twice.
Print the menu of record. One Confluence page lists every new ticket, and each ticket links back to it.
Hand dishes on at the pass. A second trigger hands a cleared specialist dish on, once, after checking four gates.
Hire the specialist chef. A Rovo agent in your manifest researches dishes with the Level 1 supplier and publishes notes. Then lesson 7 compares it with a Studio agent.
Cut a delivery door, optional. A web trigger lets other systems send menus, if they know the door code.
The lessons
- Lesson 0: Get ready for Level 2A working Level 1 app, an Approved for Agent status, a Confluence space, Rovo, and two settings that tell the app where the kitchen is.
- Lesson 1: Open the menu deskAdd a page of your own to Jira, built with Custom UI, where the head chef pastes menu-meeting notes and gets one ticket back.
- Lesson 2: Accept fast, cook laterSave the menu, put a job slip on a queue and hand back a receipt at once. A consumer function, the prep cook, writes the tickets afterwards on the app’s own badge.
- Lesson 3: Bring in the sous-chefLet Forge LLM read the meeting notes and list the dishes, check its answer, then write one ticket per dish and tick each off so a retry never writes one twice.
- Lesson 4: Print the menu of recordAfter the tickets, write one Confluence page that lists them, and comment its link on each ticket, once.
- Lesson 5: Hand dishes on at the passA second trigger watches for specialist dishes moved to Approved for Agent, checks four gates, and hands each one on with a comment, exactly once.
- Lesson 6: Hire the specialist chefAdd a Rovo agent to the app with two actions, one that researches a dish with the Level 1 supplier and one that publishes notes, both as the person chatting.
- Lesson 7: Invite a guest chef from StudioBuild an agent in Rovo Studio in the browser, with no code, let it work a handed-off dish ticket, and compare it with the specialist chef your app brings.
- Lesson 8: Cut a delivery dooroptionalGive the app a web trigger, a URL other systems can send menus to, guarded by a door code kept in an encrypted variable.