Loop 018
The product update podcast loop
A scheduled editorial workflow that turns meaningful public product changes into a short, source-grounded podcast episode.
Ready-to-use prompt
Copy the loop
Each night, review publicly released product changes and select only those users need to know. Verify each against the product, docs, or release notes. Use the Jellypod MCP to turn the approved changes into a three-to-five-minute podcast explaining what changed, why it matters, and how to try it. Check the script and audio for accuracy, clarity, and pronunciation. If nothing meaningful shipped, make no episode. Ask before publishing. Finish with the draft episode, sources, and review result.
Verify / stop
The episode accurately covers every meaningful public update.
Finish with a review-ready three-to-five-minute episode, or a confirmed no-episode result when nothing meaningful shipped.
Context and guidance When to use it, steps, safety notes, and related loops
Use this when
Use this when a product ships frequently enough that users would benefit from a short recurring audio explanation of what changed and how to use it.
How to run it
- Collect the previous day's public product changes, documentation, and release notes.
- Select the changes most meaningful to users and verify what actually shipped.
- Use Jellypod to draft a three-to-five-minute episode covering the benefit and how to try each selected change.
- Review the script and audio against the sources, regenerate weak passages, and request approval before publishing.
Why it works
A fixed release window keeps coverage current, while editorial selection and source verification prevent the episode from becoming an automated reading of commit titles.
Implementation note
Use only publicly released information. Do not expose private repository context, customer data, security-sensitive details, or unreleased work in the generated episode.