release-video — Claude Code skill: what it does, how to install
release-video plans scenes for newly shipped features and renders an announcement video with background music and UI audio.
MIT ★ 571 updated 2026-10-29
npx skills add ai-driven-dev/framework --skill release-video -a claude-codeWhat release-video does
This skill prepares product announcement clips from changes delivered since the previous release. It reviews shipped features and assigns each item to a scene. The sequence is stored in aidd_docs/release-video/scenes.json, noting either the visual framing or an explicit reason to omit a feature.
Video creation uses render assets in assets/, while related tests run from scripts/__tests__/. The process layers interface audio and writes fresh background music via compose-music. Scenes are framed so the audience understands updates even when playing video muted.
The skill stops once it produces release-video.mp4. Uploading the clip and publishing release notes remain manual steps for the maintainer.
What it helps with
- plan video scenes covering each feature in a release
- render the final
release-video.mp4with UI sounds - compose a fresh music track for the release clip
- verify that no shipped feature was skipped by mistake
Example prompts for the agent
- Plan and render the video for release v1.4.0
- Compose a new music track for the release video
- Check the release scenes and render
release-video.mp4
How to install release-video
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill release-video -a claude-code2Manually: put the files in place
~/.claude/skills/release-video/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-video/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill release-video -a codex2Manually: put the files in place
.agents/skills/release-video/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill release-video -a cursor2Manually: put the files in place
.cursor/skills/release-video/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework .claude/skills/release-video2Manually: put the files in place
.github/skills/release-video/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill release-video -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path .claude/skills/release-videoManually: put the files in place
.devin/skills/release-video/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill release-video -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-video
How to install release-video in Claude Code?
Run npx skills add ai-driven-dev/framework --skill release-video -a claude-code in your terminal. The file is placed in ~/.claude/skills/release-video/SKILL.md.
What does the release-video skill do?
It drafts a scene plan in aidd_docs/release-video/scenes.json, adds UI sounds, composes background audio, and renders release-video.mp4.
Does this skill publish the video or write release notes?
No, the workflow stops at creating the local release-video.mp4 file. Attaching the video to a release and announcing it are handled separately by the user.
Source text
SKILL.md · MIT
--- name: release-video description: Plans and renders the release video, one scene per feature shipped since the last release, with its music and interface sounds. Use when the user wants to prepare the release announcement video, change its music, or the release video check reports missing scenes. Not for publishing the video or writing release notes. argument-hint: release version | music --- # Release video ```mermaid flowchart LR source([release]) --> plan --> render --> done([release-video.mp4]) render -->|"scene to fix"| plan track([music]) --> compose-music --> render ``` ## Actions Run the flow above. Read only the next action file. | Action | Does | | --- | --- | | plan | cover every shipped feature with a scene, or a reason to skip it | | render | turn the plan into the MP4 and check it on screen | | compose-music | write a new track when the user asks for other music | ## Transversal rules - The plan lives in `aidd_docs/release-video/scenes.json`; the check and the renderer are in `assets/`, their tests in `scripts/__tests__/`. - Show only what the product does; mark every invented figure as an example on screen; a demo of text alone, plainly a session, needs no mark. - A viewer may watch with the sound off and never read the release notes: the picture carries the message, the sound only makes it lively. - Never reuse the audio of a published video: it carries that video's own sounds, which then play at moments that mean nothing here. - Keep product choices with the user, music included: it is judged by listening, which is the user's. - Stop at the MP4: attaching it to a release and announcing it are the user's.
© ai-driven-dev · MIT · ai-driven-dev/framework