Content Creator Roadmap

INPUTS [Finished video summary]; [resources]; [intended viewer] PROMPT Draft a video description from [finished video summary] for [intended viewer]. State the actual topic and useful outcome, then organise [resources] into clearly labelled links or placeholders. Do not insert unrelated keywords, invented credentials or claims about results the video does not show.

Try this follow-up
Remove repeated phrases and put the most useful context in the opening lines.

Check before using
Verify resource destinations and any factual claims before publishing.

INPUTS [Timestamped outline]; [section purposes]; [platform requirements] PROMPT Turn [timestamped outline] into concise chapter labels reflecting [section purposes]. Keep every supplied timestamp unchanged and flag gaps or overlaps. List [platform requirements] I still need to verify. Do not invent timestamps or pretend to have watched the video.

Try this follow-up
Make the labels more specific without changing the times.

Check before using
Check each chapter against the final uploaded edit.

INPUTS [Video takeaway]; [question for viewers]; [boundaries] PROMPT Write three pinned-comment options around [video takeaway] and [question for viewers]. Keep [boundaries] and invite concrete experiences or questions. Do not manufacture controversy, pressure engagement or imply that a reply guarantees a benefit.

Try this follow-up
Choose the most natural option and shorten it to two sentences.

Check before using
Make sure the question fits the video and is comfortable for viewers to answer.

INPUTS [Viewer correction]; [verified facts]; [planned change] PROMPT Draft a response to [viewer correction] using [verified facts] and [planned change]. Acknowledge the specific point, state what I checked and explain the correction I can actually make. If the claim remains unverified, say what I need to check. Do not argue from authority or invent an apology.

Try this follow-up
Create a concise version for the comment and a separate note for the description update.

Check before using
Verify the correction before presenting it as settled.

INPUTS [Redacted comments]; [channel scope]; [available expertise] PROMPT Group [redacted comments] into recurring questions within [channel scope]. Preserve representative wording without identifying commenters. Distinguish a repeated question from a single unusual request. Suggest future topics I can address using [available expertise]. Do not invent frequency counts or audience sentiment.

Try this follow-up
Rank the topics by fit and ability to demonstrate, rather than predicted views.

Check before using
Check any counts against the supplied comments and keep personal details out.

INPUTS [Title]; [description]; [thumbnail description]; [final content] PROMPT Check the consistency of [title], [description], [thumbnail description] and [final content]. Flag mismatched promises, outdated references and claims unsupported by the video. Produce a short fix list ordered by viewer confusion. Do not predict performance or claim platform-policy approval.

Try this follow-up
Rewrite only the highest-priority inconsistent element.

Check before using
Review the final files and current platform requirements yourself.

INPUTS [Original plan]; [actual reason]; [confirmed next step] PROMPT Write a brief audience update about a delayed episode using [original plan], [actual reason] and [confirmed next step]. Keep the tone direct and human. Separate an estimate from a confirmed date. Do not invent circumstances, blame a collaborator or make a new promise to soften the delay.

Try this follow-up
Write a version that gives only the information viewers need.

Check before using
Use only a reason you are comfortable sharing publicly.

INPUTS [Original title]; [alternative]; [available metrics]; [time window] PROMPT Create a record for testing [alternative] against [original title]. Define what changes, what stays fixed and which of [available metrics] I will observe over [time window]. List confounding factors and limits. Do not predict an uplift or treat a small observation as a causal result.

Try this follow-up
Write a review template with spaces for actual observations and uncertainties.

Check before using
Use the platform’s real measurements and avoid over-interpreting a small sample.

INPUTS [Community purpose]; [unwanted behaviour]; [moderation approach] PROMPT Draft a short comment-guideline note for [community purpose]. Describe [unwanted behaviour] and [moderation approach] in plain language. Encourage disagreement about ideas while keeping boundaries clear. Do not threaten users or invent rules the channel will not apply.

Try this follow-up
Make the note shorter and add one example of a constructive disagreement.

Check before using
Make sure the guidelines match the moderation you can actually provide.

INPUTS [Description links]; [purpose of each]; [known status] PROMPT Organise [description links] into a resource audit using [purpose of each] and [known status]. Flag missing destinations, vague labels and resources that no longer match the video. Mark status unknown unless supplied. Do not claim to have opened or checked links you cannot access.

Try this follow-up
Suggest clearer labels for the resources I have verified.

Check before using
Open every final destination and confirm permission to share any private material.