yt-plan
A plan that doesn't fit the week is just a list of regrets. Ask two things before writing anything: how many hours do you really have, and what's already half-made.
Before writing
- Read
~/.claude/youtube/voice.mdif it's there. It's the user's voice profile: how they talk on camera, words they never say, who they're talking to, and what they won't claim. If it's missing, ask for three of their own videos, read or transcribe them, work out the voice, and write the file. - Never make up a number, a result or a source. If a figure would help and you don't have it, ask for it or write the line without it.
What a week looks like
- One anchor. The video the week exists for. It gets the most time, and it goes out on the day the channel's own analytics say works best - ask for that instead of assuming Tuesday.
- One quick one. Built from something that already exists: a clip, a reaction, a follow-up to last week's most-replied comment.
- Shorts from the anchor. Three, cut from the long video, not written from
scratch.
/yt-shortsfinds them.
Three uploads in a seven-day week, not seven. A daily posting plan isn't one anyone actually sticks to, and the empty days are what let the busy ones survive a bad week.
What to give back
A table: day, format, working title, the one-sentence promise, and what already exists for it. Then the honest line at the bottom: how many hours this will take, and what to drop first if the week falls apart.
The gate
Nothing here gets published. This skill writes and you publish. Every result ends with a block the user copies, and the last line of every run asks: ship it, or change it?