
Change one fact in every SCORM package
A rename, a new logo, a changed rule: found and fixed across your library, one approval.
- For
- L&DLegal / IT
- Routine
- When it happens
- Setup
- Juno only
- You approve
- every draft
What you get
Before
Security basics 2023
SCORM package
Updated March 4, 2024
After
Security basics 2026
Course
Updated September 28, 2026

Phishing in practice
Interactive lesson
Updated September 28, 2026
The prompt
Written to ask before it assumes, check what already exists, and stop before anything goes live.
Something changed (a product name, a logo, a rule, a contact) and I want it fixed in every SCORM lesson in Juno Journey that mentions it. Use the Juno Journey connector for anything in Juno. If it isn't connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. My role and the team I support 2. What changed: the old wording and the new one 3. Which lessons or programs to look in, or all of them 4. Anything that must not change Ask these in one message, then wait for my answers. Search Juno for the lessons likely to contain it, open each one and find every occurrence. Tell me which lessons you couldn't read, and which occurrences sit in generated code you can't edit. Show me the list: lesson, where, the old text, the new text. After I approve, update each lesson in place as a new version on the same link, and give me the version numbers so we can roll back. Routine: after the first run, offer to repeat this for every change of the same kind. If this assistant can run scheduled tasks, set one up only after I approve it; if not, give me a one-line prompt I can re-run. Change nothing until I approve the list.
Your AI asks you
- Q1My role and the team I support
- Q2What changed: the old wording and the new one
- Q3Which lessons or programs to look in, or all of them
- Q4Anything that must not change
The routine
- 01
Connect
Juno and the tools below
- 02
Answer
the questions, one message
- 03
Review
the draft or the view it builds
- 04
You approve
before anything goes live
Routine: When it happens. The prompt offers to set it up as a scheduled task in your assistant, only after you approve.
What it connects
- JunoRequired
Your AI assistant reads the tools it can reach and drives Juno.
Where this Journey Play works
Journey Plays that go with it

Bring your Storyline and Rise courses into Juno
Imported once, then edited in plain words: same link, same assignments, every version kept.
Once
Turn a SCORM package into a course anyone can edit
The content of a locked package, rebuilt as a native Juno course with its quiz.
When needed
Sort the library before you move it
Keep, merge, rebuild or retire: decided before the migration, not after.
Once






















