edit-video-blog
Step 0 — Gather inputs
Before doing anything else, ask the user for the following. Do NOT proceed until you have at least the transcript.
- The video transcript (required — this is the source of truth for what was actually said)
- The initial draft article, if they have one
- The YouTube video URL, if they have one
- The GitHub repository URL, if any
- The target audience (e.g. "intermediate Go developers", "developers new to Kubernetes")
Wait for the user to respond before continuing.
Step 1 — Extract key points from the transcript
More from fboucher/skills
grill-me
Interview the user persistently about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
12prd-to-issues
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
10write-a-prd
Create a PRD through user interview, codebase exploration, and component design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature in a .NET web application.
7write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
6tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
5improve-codebase
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
5