From creator-stack
Creates complete YouTube video plans with title options, thumbnail concepts, hooks, and content outlines. Use for new video planning or triggers like 'plan a video' or 'plan my next YouTube video'.
npx claudepluginhub kenneth-liao/ai-launchpad-marketplace --plugin creator-stackThis skill uses the workspace's default tool permissions.
This orchestrator sequences foundation skills to produce a complete video plan: researched titles, thumbnail concepts, hook strategies, and a content outline. It manages the user selection workflow between steps but delegates all content generation to specialized skills.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
This orchestrator sequences foundation skills to produce a complete video plan: researched titles, thumbnail concepts, hook strategies, and a content outline. It manages the user selection workflow between steps but delegates all content generation to specialized skills.
Core Principle: This is a thin orchestrator. All content generation goes through foundation skills — that's where the proven patterns, formulas, and quality logic live. This skill manages workflow sequence, user decisions, and plan file assembly only.
Each step below invokes a foundation skill that owns its own reference files. When you invoke creator-stack:title, it loads references/youtube-title-formulas.md from its own directory. When you invoke creator-stack:thumbnail, it loads references/thumbnail-formulas.md from its own directory. You don't need to manage these paths — just invoke the skill and provide context.
All episode files live under ./youtube/episode/[episode_number]_[topic_short_name]/.
research.md in the episode directoryplan.md in the episode directoryIf a local channel context file exists (e.g., ./youtube/channel.md or similar), load it at the start of the workflow to provide channel-specific context to downstream skills.
When creator-stack:research is invoked from this orchestrator, the YouTube Analytics MCP tools are available for data gathering:
search_videos — find videos by keyword, channel, or criteriaget_video_details — video stats, views, likes, comments, publish dateget_channel_details — channel metadata, subscriber count, video countget_video_comments — comment text and sentiment dataget_video_transcript — full video transcriptget_related_videos — videos related to a specific videoget_trending_videos — currently trending videosget_video_enhanced_transcript — enhanced transcript with timestampsThe YouTube Researcher agent (defined in this plugin's agents/youtube-researcher.md) can also be used for structured data gathering tasks.
Use this skill when:
Research for the video must be completed first. Either:
./youtube/episode/[episode_number]_[topic_short_name]/research.md, ORcreator-stack:research to conduct research first (YouTube MCP tools are available)Execute all steps below in order. Track progress systematically.
Read the research file for this episode:
./youtube/episode/[episode_number]_[topic_short_name]/research.mdIf research does not exist, invoke creator-stack:research first. The YouTube MCP tools are available from this orchestrator context, enabling the research skill to gather YouTube-specific data.
The video plan should incorporate research findings at each step — research grounds every recommendation.
Create a new plan file at: ./youtube/episode/[episode_number]_[topic_short_name]/plan.md
If a plan file already exists, read it to understand what has been done so far and continue from there.
Initialize the plan file with this template:
# [Episode_Number]: [Topic] - Video Plan
## Research Summary
[Summary of research insights]
## Titles
[3 title options with rationale and star ratings]
## Thumbnails
[2 thumbnail concepts per title with rationale and star ratings]
## Hooks
[3 hook options for selected title+thumbnail with rationale and star ratings]
## High-Level Content Outline
[Section structure with key points]
## Final Plan
[Selected title, 3 AB test thumbnails, selected hook, outline]
Update this document as you progress through the planning steps.
Invoke creator-stack:title to generate 3 optimized titles.
Document all title options in the plan file including:
Complete title generation before proceeding to thumbnails — thumbnails need to complement the titles.
Invoke creator-stack:thumbnail to generate 2 thumbnail concepts for each title. These should be concept descriptions only, not actual images yet.
Document all thumbnail concepts in the plan file including:
Present all title/thumbnail combinations to the user, along with your top 3 recommended title + thumbnail pairings.
Ask the user to select their one preferred title + thumbnail pairing to proceed with.
Update both the title and thumbnail sections in the plan file to indicate the user's selection with a (User Selection) marker next to the selected options.
Always present all options so the user can make an informed decision — that's the whole point of generating multiple options.
Invoke creator-stack:hook to generate 3 retention-optimized hooks, only for the user's selected title + thumbnail pairing.
Document all hook strategies in the plan file including:
Present all hook options to the user and ask the user to select their preferred hook strategy.
Update the hook section in the plan file to indicate the user's selection.
The plan should now contain a user-selected title, thumbnail, and hook combination.
Invoke creator-stack:write to create a high-level content outline.
Create and document the strategic roadmap:
Keep the outline high-level — structure and key points only, no detailed scripts. Focus on what is important to cover from the viewer's perspective rather than assuming specific content.
Now that the user has selected their preferred title, thumbnail, and hook, finalize the plan.
Invoke creator-stack:thumbnail to generate 3 thumbnail options for AB testing. These should be actual images generated with creator-stack:nanobanana, not just concepts. The first thumbnail should be based on the user's selected thumbnail concept. The other 2 should test different visual styles of the first thumbnail.
Update the final plan section in the plan file with the complete final selections:
## Final Plan
- **Title**: [Selected title]
- **Thumbnails**:
- 
Thumbnail A Description
- 
Thumbnail B Description
- 
Thumbnail C Description
- **Hook**: [Selected hook strategy]
- **Rationale**: [Why this combination works]
A final plan always includes 3 thumbnails to AB test — that's how you learn what works for your audience.
Each foundation skill owns its own reference files and loads them automatically:
| Content | Skill | Reference (loaded by the skill) |
|---|---|---|
| Titles | creator-stack:title | youtube-title-formulas.md |
| Thumbnails | creator-stack:thumbnail | thumbnail-formulas.md |
| Hooks | creator-stack:hook | youtube-hooks.md |
| Outline | creator-stack:write | youtube-script.md |
| Voice | creator-stack:voice | Invoked automatically by writing skill |
Before finalizing, verify that title/thumbnail/hook work together:
Verify completion before finalizing plan:
creator-stack:title invoked — 3 title options generatedcreator-stack:thumbnail invoked — 2 thumbnail concepts per titlecreator-stack:hook invoked — 3 hook strategies generatedcreator-stack:write invoked — high-level content outline createdcreator-stack:thumbnail invoked — 3 AB testing thumbnails generatedScenario: User requests plan for video about "Building AI agents with memory" (research already complete)
./youtube/episode/18_ai_agents_with_memory/research.md, extract key insights./youtube/episode/18_ai_agents_with_memory/plan.mdcreator-stack:title — 3 title options focused on practical implementationcreator-stack:thumbnail — 2 concepts per title (6 total)creator-stack:hook — 3 hook strategies for selected pairingcreator-stack:write — high-level content outlinecreator-stack:thumbnail — 3 AB testing thumbnails for final planResult: Production-ready plan with multiple options for user selection, all backed by research and generated using proven patterns from foundation skills.