---
name: retro
description: 48-hour post-publish retro for a video, performance vs the last 10, promise-delivery check, lessons into the wiki. Use when the creator says "retro NNN" or ~2 days after a publish.
---
<!-- Adapted from the hijoseromero production repo (Claude Code skill). Generic version: personal rules, private paths and names removed.
   Assumes a repo laid out as content/videos/NNN-slug/, content/ideas.md, pipeline/, tools/ (auto-editor, faster-whisper, Playwright).
   Drop this file at.claude/skills/retro/SKILL.md and invoke with /retro NNN. -->

# 48-hour retro

1. Ask the creator for the numbers from YouTube Studio (views, impressions CTR, avg view duration, retention graph shape, subs gained), no API access yet; when a YouTube API key lands in the env, pull automatically instead.
2. Write `content/videos/NNN-slug/retro.md`:
  - Numbers table + comparison vs the running averages of the last 10 videos
  - **Promise check:** did the video deliver what title+thumbnail promised? (Re-read titles.md pick vs transcript.)
  - Which title/thumbnail ran, and would the B option have done better?
  - One thing to repeat, one thing to change (append these to `log/` daily note)
3. Update the channel tracker with date + headline number.
4. Trend note: after 5+ retros exist, compare pillars, flag what the audience is actually voting for. Once there is enough data: hunt the "wave" topic and propose feeding it.
5. **Improve the pipeline, not just the videos:** end every retro by proposing concrete edits to the skills/templates that caused what went wrong (or codify what went right), e.g. a hook rule to `pipeline/script-craft.md`, a checklist line to `/record`, a title formula to `content/templates/metadata.md`. Skills are git-versioned; show the diff, the creator approves, commit. Log the change in the daily note.