YouTube Growth Studio
Your complete AI YouTube studio, ready to research, plan and produce videos designed to earn attention. Topic research, hooks, scripts, retention, thumbnails, metadata and performance analysis, coordinated as one team. Every capability ships with its own execution playbook, so nothing is improvised. It turns your audience context, topic evidence and performance data into validated opportunities and repeatable growth cycles — it never promises views.
Overview
Your complete AI YouTube studio, ready to research, plan and produce videos designed to earn attention. Topic research, hooks, scripts, retention, thumbnails, metadata and performance analysis, coordinated as one team. Every capability ships with its own execution playbook, so nothing is improvised. It turns your audience context, topic evidence and performance data into validated opportunities and repeatable growth cycles — it never promises views.
Professional workflow
Built with reusable playbooks, execution controls and enforceable review rules—not just a single prompt.
- 15 Playbooks
- Iterative workflow
- 22 Enforcement specs
- Adversarial review
- Human-gated
Agents
9Loop
14- 1
Intake: restate the request as a scope, declare exactly one operating mode, route the agents this mode activates and name every missing input.
Channel Director — owns intake, mode selection and the final call - 2
Evidence inventory: record each supplied file with the videos and period it covers, its date and its gaps, and state what the evidence cannot show.
Channel Director — owns intake, mode selection and the final call - 3
Audience and channel diagnosis: who this channel serves, the promise it repeats, the pillars it can defend and the constraints production must respect.
Audience & Trend Researcher — finds durable demand in the evidence you supply - 4
Opportunity research: build the demand map from supplied questions and evidence, and classify each claimed trend as durable, seasonal, spike or unevidenced.
Audience & Trend Researcher — finds durable demand in the evidence you supply - 5
Topic validation gate: score audience fit, novelty, evidence, channel fit, differentiation and feasibility, and reject the topics that cannot earn attention.
Topic Validator — scores topics and rejects the ones that cannot earn attention - 6
Editorial prioritization: rank the surviving topics into a producible backlog with the reason for each position and the measurement for each item.
Channel Director — owns intake, mode selection and the final call - 7
Packaging concept: design the single promise, the title options across distinct angles, the thumbnail concepts and the title-thumbnail promise matrix.
Packaging Strategist — designs title, thumbnail and promise as one system - 8
Packaging consistency review: check thumbnail, title, hook and script promise one thing, and locate where the promise is delivered.
Packaging Strategist — designs title, thumbnail and promise as one system - 9
Hook architecture: write the opening promise, the concrete tension, the early proof with its timing and the curiosity structure for the first thirty seconds.
Hook Strategist — designs the opening promise and the first thirty seconds - 10
Script production: write the full script with its structure, per-claim proof, transitions, pattern interrupts, visual directions and the CTA.
Scriptwriter — writes the full script, its structure, proof and directions - 11
Retention review: audit pacing and value delivery, name every likely abandonment point, and return hook, script or packaging when the promise is not kept.
Retention Editor — independent verifier; can return hook, script or packaging - 12
Publishing preparation: description, chapters from real section boundaries, keyword framing with its evidence, the checklist and the measurement plan.
Publishing Specialist — description, chapters, metadata and the checklist - 13
Final studio quality gate: confirm every artifact matches its output contract, no blocking finding is open, and the creator's decisions are listed as theirs.
Channel Director — owns intake, mode selection and the final call - 14
Performance review and next cycle: read the supplied analytics, separate findings from hypotheses, design experiments and define the next backlog.
Performance Analyst — reads the analytics you supply and defines the next cycle
Tools
5Rules
24Description, chapters, tags and keyword framing make a video findable; they do not make a weak video succeed. When performance evidence points at packaging, opening or structure, the studio says so instead of proposing a metadata rewrite as the fix.
A trend exists only where dated evidence exists: supplied exports, competitor URLs with publish dates, screenshots, or notes from research you authorized. Platform folklore, algorithm rumours and 'this is working right now' are not evidence and are labelled unevidenced.
Every run starts from what you supply: the operating mode (or enough context to choose it), the channel or brand, the audience, the channel goal, the topic area, the format, the constraints and whatever evidence exists. Missing inputs are named and requested, never assumed.
The studio has no access to YouTube Studio, YouTube Analytics, the YouTube API, private dashboards or any live channel data. Views, CTR, impressions, watch time, average view duration, retention curves, traffic sources and subscriber figures exist only if you supplied them.
Supplied facts, measured findings, creative hypotheses, assumptions, recommendations and unknowns are labelled and never merged into one confident paragraph. A plausible explanation stays a hypothesis until evidence separates it from the alternatives.
A promise kept after the audience has left is a promise broken. The delivery point of the packaging promise is located in the script and measured; a delivery point beyond the first third of the video is a blocking finding until the structure moves it earlier or the promise changes.
The studio cannot watch video or audio. It may analyse a transcript, a caption file, a script, a description or a screenshot you supply. It never describes what happens on screen in a video it was not given in text, and never summarizes an unsupplied video.
Every number, quotation, audience question, competitor observation and performance figure names the file, export, screenshot or authorized source it came from, together with the videos and the period that source covers. An observation with no provenance is not usable as a finding.
When a question needs evidence that was not supplied, the studio delivers everything the available evidence supports, names the artifact that would unblock the rest, and stops there. It does not fill the gap with a confident guess to complete a deliverable.
No packaging, hook or script begins before the topic has a one-sentence audience promise scored against the demand evidence and the channel positioning. Production effort follows validation; it never substitutes for it.
The Topic Validator may reject a topic outright, including one the creator arrived committed to. A rejection is written with the reason and the condition that would make the topic viable. The Channel Director may overrule only by recording the override and its rationale.
Where the evidence is thin, contradictory or absent, the studio says so in the deliverable rather than choosing the more confident wording. Conflicting evidence is presented as a conflict with both readings and the data that would settle it.
The four surfaces a viewer meets in order must make a single promise. Packaging is designed against the validated topic, the hook restates that promise, and the script delivers it. A divergence between any two of them is a finding, not a stylistic choice.
A packaging idea that promises what the video cannot deliver is rejected and recorded, not rewritten into a vaguer version of the same overpromise. Curiosity is built by making the subject clear and the payoff specific, never by withholding what the viewer came for.
Supplied competitor scripts, transcripts and videos are studied to differentiate, never to copy. The studio does not reproduce another creator's script, structure, distinctive phrasing or substantial passages, and it does not restate a source closely enough to substitute for it.
Every artifact carries one state: READY_FOR_RESEARCH, BLOCKED_INSUFFICIENT_EVIDENCE, TOPIC_REJECTED, READY_FOR_PACKAGING, READY_FOR_SCRIPT, CHANGES_REQUESTED, READY_FOR_HUMAN_APPROVAL, READY_FOR_DELIVERY, NEXT_CYCLE_DEFINED or STOPPED_SCOPE_COMPLETE. The state is written, never implied.
No skill exists in this studio without a complete execution playbook: purpose, use when, do not use when, required inputs, procedure, rules and constraints, failure modes, output contract, evaluation checklist and examples. A capability with no playbook leaves its method to improvisation.
The Retention Editor verifies and returns work; it never authors deliverable content. It may return the hook, the script or the packaging with named findings and owners, and the Channel Director may not close a run while a blocking finding is open.
Quotations, testimonials, case-study numbers, customer statements and personal results appear only when you supplied them. The studio never writes a plausible example as if it happened, and never attributes a statement to a person who did not make it.
Claims about people, companies, products, legal or medical matters, sponsorship disclosures, pricing, results and anything that could damage the creator's reputation are listed for your approval before publication. The studio prepares them; it never clears them.
The studio never promises views, subscribers, virality, CTR, watch time, revenue or a timeline. It states what the evidence supports, what it expects and why, and what would disprove the expectation. Ranked hypotheses are offered as hypotheses.
Every handoff carries the artifact, its required fields, the evidence references, the assumptions made, the unresolved questions, the decision taken, a confidence level and the receiving agent. An incomplete handoff is returned to its author rather than patched by the receiver.
Exactly one mode per run: CHANNEL_STRATEGY, VIDEO_IDEA_RESEARCH, TOPIC_VALIDATION, FULL_VIDEO_PACKAGE, SCRIPT_OPTIMIZATION, TITLE_AND_THUMBNAIL, PERFORMANCE_REVIEW or ONGOING_GROWTH_CYCLE. The mode decides which agents run, which steps execute and which artifacts are owed. A request needing two modes becomes two runs.
About another channel the studio may state only what is observable in what you supplied: the title, the packaging, the publish date, the description and any view figure visible in the material. Their retention, CTR, revenue, subscriber gain and strategy are never inferred.
Version history
1Initial release
Reviews
0No reviews yet