yt-plan
A plan that does not fit the week is a list of regrets. Ask two questions before writing anything:
how many hours do you actually have, and what is already half-made.
Before you write
- Read
~/.claude/youtube/voice.md if it exists. That is the user's voice profile: how they talk
on camera, the words they never use, who they are talking to, what they will not claim. If it
does not exist, ask for three of their own videos, read or transcribe them, infer the voice,
and write the file. A script in the wrong voice is worse than no script, because they have to
read it out loud.
- Never invent a number, a result or a source. If a figure would strengthen it and you do not have
one, ask for it or write the line without it.
The shape of a week
- One anchor. The video the week is for. It gets the most time and it goes out on the day the
channel's own analytics say is best - ask for that, do not assume Tuesday.
- One cheap one. Built from something that exists: a clip, a reaction, a follow-up to the
comment that got the most replies last week.
- Shorts from the anchor. Three, cut from the long video, not written separately.
/yt-shorts
finds them.
Three uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone
recognises, and the empty days are what make the filled ones survive a bad week.
What to hand back
A table: day, format, working title, the one sentence it promises, and what already exists for it.
Then the honest line at the bottom - how many hours this costs, and what to drop first if the week
goes wrong.
The gate
Nothing here publishes. This skill writes and you publish. Every output ends in a block the user
copies, and the last line of every run is the question: ship it, or change it?
1---2name: yt-plan3description: Plan a week or a month of YouTube uploads - what to post, when, and in what order, sized to the creator's actual capacity. Use for "plan my week", "content calendar", "what should I post", "I have no idea what to make next".4---56# yt-plan78A plan that does not fit the week is a list of regrets. Ask two questions before writing anything:9**how many hours do you actually have**, and **what is already half-made**.1011## Before you write12131. Read `~/.claude/youtube/voice.md` if it exists. That is the user's voice profile: how they talk14 on camera, the words they never use, who they are talking to, what they will not claim. If it15 does not exist, ask for **three of their own videos**, read or transcribe them, infer the voice,16 and write the file. A script in the wrong voice is worse than no script, because they have to17 read it out loud.182. Never invent a number, a result or a source. If a figure would strengthen it and you do not have19 one, ask for it or write the line without it.2021## The shape of a week2223- **One anchor.** The video the week is for. It gets the most time and it goes out on the day the24 channel's own analytics say is best - ask for that, do not assume Tuesday.25- **One cheap one.** Built from something that exists: a clip, a reaction, a follow-up to the26 comment that got the most replies last week.27- **Shorts from the anchor.** Three, cut from the long video, not written separately. `/yt-shorts`28 finds them.2930Three uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone31recognises, and the empty days are what make the filled ones survive a bad week.3233## What to hand back3435A table: day, format, working title, the one sentence it promises, and what already exists for it.36Then the honest line at the bottom - how many hours this costs, and what to drop first if the week37goes wrong.3839## The gate4041Nothing here publishes. This skill writes and you publish. Every output ends in a block the user42copies, and the last line of every run is the question: **ship it, or change it?**
Jakeschincariol