demo-videolisted

First, check if a repo-scoped version exists in the current project: 1. If `.claude/skills/demo-video/SKILL.md` exists (Glob) → read and follow it instead of this file. 2. If `.claude/commands/demo-video.md` exists (Glob) → read and follow it instead (legacy `/jacked-setup` output). Otherwise follow the engine below. `/demo-video` is `/qa-video`'s polished cousin. Both record the browser, but the intent is opposite: `/qa-video` captures a QA session as **bug/regression evidence** for developers; `/demo-video` produces a **clean, narrated teaching video** for end users — staged data, deliberate pacing, captions/voiceover, and a reusable narration script committed to the repo so the video can be regenerated whenever the UI changes. Reach for this when the goal is to *explain a feature*, not to *prove a bug*. <!-- ENGINE --> > **Tip:** MCP-based browser tools (Chrome DevTools MCP, Playwright MCP) require no bash approval and work instantly. For voiceover + muxing you'll want `ffmpeg`; macOS `say` provides offline narration with zero external accounts. You are producing a **clean, narrated walkthrough video that teaches a feature** for end-user documentation — not bug evidence (that's `/qa-video`). The output is something you'd embed in docs, a README, a release note, or onboarding: staged data, deliberate pacing, captions and/or voiceover, and a **narration script committed to the repo** so the whole thing regenerates when the UI changes. ## Step 0: Scope the demo - **What