Demo & Changelog Generator
When you ship, a producer pulls the shipped work from your repository and turns each feature into a 30-second clip script, X and LinkedIn posts, a launch note, and a changelog entry — checked for accuracy and voice and handed to you to approve before anything is posted.
Saves you ~3 h / week
How it works
- Trigger
- On the “Shipped-work content run” schedule.
- Job
- Pull shipped work, produce the content kit, check accuracy and voice.
- Outcome
- A verified release-note and changelog draft grounded in shipped work.
What it installs
Agents 3
-
Content Producer
Turns each shipped feature into a 30-second clip script, X/LinkedIn posts, a launch note, and a changelog entry.
-
Content Editor
Verifies the content kit against the actual shipped work and tightens voice before the human gate.
-
Demo & Changelog Generator Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Demo Content Team
A producer who turns shipped work into a content kit and an editor who checks accuracy and voice before the human gate.
Workflows 1
-
Demo & Changelog Generator
Pull shipped work, produce the content kit, check accuracy and voice, then hand off for approval before posting.
Goals 1
-
Shipped work always becomes content
Keep the shipped-to-content loop running so nothing ships silently. Success looks like: Every cycle of shipped, user-facing work produces an approved content kit (clip script, posts, launch note, changelog) and none is left undocumented.
Skills 3
-
demo-video-scripting
Turn a shipped feature into a tight 30-second demo clip script: a 3-second hook, a fast on-screen demo, a captioned shot list with voiceover, the money shot, and a single CTA — value-first and accurate to what shipped. Adapted from public growth playbooks.
-
launch-posts
Write native X and LinkedIn launch posts plus a launch note from a shipped feature: hook-first lines, build-in-public voice, the right depth per platform, a single CTA, and accuracy to what shipped. Adapted from public growth playbooks.
-
changelog-writing
Draft user-facing changelog entries from merged work: group under New/Improved/Fixed, lead with the benefit not the commit, skip behavior-neutral chores, and keep a plain present-tense voice. Adapted from public growth playbooks.
Schedules 1
-
Shipped-work content run
Turns shipped work into a content kit on the schedule you choose. ## Professional quality control Objective: complete the recurring Demo & Changelog Generator operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. Verify audience, trigger, source, claim, personalization, permission, and any spend exposure. Public copy must be useful before promotional, truthful about affiliation, and free of generic AI phrasing, fake familiarity, filler, hype, hollow transitions, or template language that could be sent unchanged to unrelated recipients. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.
Requirements
- Connected repository — The agent reads merged PRs, commits, and releases from your connected repository to know what shipped. Until repository access is connected, it works from the shipped work supplied as attachments.
- Browser access to X and LinkedIn — The agent posts to X and LinkedIn through their web interfaces in your browser and pauses for your approval before posting; until you connect it, it produces ready-to-post drafts you publish yourself. These platforms have no usable API for this.
Setup guide
How to Automate Demo and Changelog Generation
A practical guide to turning shipped work into demo scripts, launch posts, launch notes, and changelog entries.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.