This department is built for the Head of Growth, the Social Lead and the Creator Manager at a consumer app or a mobile game studio, who need TikTok, Instagram Reels and YouTube Shorts to produce installs rather than impressions.
It is twenty Claude agents that hand work to each other in a fixed order. They start at the evidence you already hold about your product and your audience, and they finish with next month's plan written from the results you supplied. In between they produce a strategy, ten repeatable formats, forty concepts, one hundred hooks, fifteen creator archetypes, fifteen briefs a creator could shoot from, fifteen shot lists, a production board, three genuinely different exports per asset, a distribution calendar, a test matrix and a monthly learning report.
Eighty numbered prompts. Thirty working templates. Five workflows. Twenty three files plus the zip, all attached below.
The thing that makes it a department rather than a prompt pack is that every output carries the same five field header, so the next agent can read it. A concept that cannot name the evidence row it rests on does not exist. A test whose sample rule was written after the result does not count. Three identical exports fail the publish gate.
<aside> ⚠️
Before using these prompts you should omit any PII (personal identifiable information) and check with your compliance team and/or your AI policy.
</aside>
<aside> ⬇️
Download the department. Every file individually, and the zip if you want all of it.
00-START-HERE-install-and-operating-guide.md
00-START-HERE-install-and-operating-guide.md
01-department-brief-and-charter.md
01-department-brief-and-charter.md
02-department-brief.xlsx
03-agent-department-20-agents.md
03-agent-department-20-agents.md
04-prompt-library-P01-P80.md
05-workflows-five.md
06-format-library-ten-formats.md
06-format-library-ten-formats.md
07-concepts-40.xlsx
08-hooks-100.xlsx
09-creator-archetypes-15.xlsx
10-creator-briefs-15.md
11-shot-lists-15.xlsx
12-production-board.xlsx
13-distribution-calendar.xlsx
14-testing-dashboard.xlsx
15-platform-adaptation-matrix.xlsx
15-platform-adaptation-matrix.xlsx
16-template-pack.xlsx
17-creator-brief-template.md
18-monthly-learning-report-template.md
18-monthly-learning-report-template.md
19-worked-example-consumer-app.md
19-worked-example-consumer-app.md
20-worked-example-mobile-game.md
20-worked-example-mobile-game.md
21-results-input-populated-example.xlsx
21-results-input-populated-example.xlsx
22-monthly-learning-report-example.md
22-monthly-learning-report-example.md
short-form-video-department.zip
short-form-video-department.zip
</aside>
Start with 00-START-HERE-install-and-operating-guide.md. It is the order everything else happens in. If you would rather see a finished cycle before you start one, open 19-worked-example-consumer-app.md.
Talk to UGC Ninja if you want this run on your own product and your own evidence.
| File | What it is | What you do with it |
|---|---|---|
00-START-HERE-install-and-operating-guide.md |
The install and operating guide, eight steps, plus the folder tree | Read this first. It is the order you do everything else in |
01-department-brief-and-charter.md |
The shared department brief: boundaries, record header contract, state machine, ten approval gates | Give it to Claude as standing context before you activate a single agent |
02-department-brief.xlsx |
The fourteen required inputs as fourteen tabs, T01 to T14, with a worked example row on each | Fill T01 to T13 once. Fill T14 every month. Leave a cell blank rather than guessing |
03-agent-department-20-agents.md |
All twenty agents in full: purpose, inputs, workflow, master prompt, output template, approval point, failure modes, handoff, worked example | Copy a master prompt into a Claude project to activate that agent |
04-prompt-library-P01-P80.md |
Eighty numbered prompts, four per agent, with the agent map at the top | Run them in order. Every bracketed token is declared in that prompt's Reads line |
05-workflows-five.md |
Five end to end runs with the agents, prompts and gates named at every step | Follow one start to finish. Workflow 1 takes about half a day |
06-format-library-ten-formats.md |
Ten repeatable formats, each with five named variation axes, beats, length window and how it fails | Pick four to six for your first cycle. Run P26 on each to see how many weeks it survives |
07-concepts-40.xlsx |
Forty concepts, four per format, plus both evidence ledgers and the ten format definitions | Read the evidence_ids column. That is the quality gate, and every id resolves against a tab in the same file |
08-hooks-100.xlsx |
One hundred hooks, ten per format, each attached to a concept and an evidence row | Use them as shape. Then run P29 on your own evidence, because a hook is only as true as its ledger |
09-creator-archetypes-15.xlsx |
Fifteen creator archetypes with never ask lists, rights posture and capacity, plus the archetype to brief map | Recruit against these. They are roles, not people, and P48 gives your Creator Manager six questions to ask |
10-creator-briefs-15.md |
Fifteen creator briefs written to be forwarded as they stand | Read one out loud as the creator. Then use the blank template for your own |
11-shot-lists-15.xlsx |
Fifteen shot lists, 105 shots, seven per brief including the alternate opener and the coverage shot | Send it with the brief. The what must be true column is the one that matters |
12-production-board.xlsx |
Fifteen production items with shoot windows, delivery dates, edit hours and a capacity check per department | Watch the Capacity_Check tab. The planner returns a shorter board rather than an impossible one |
13-distribution-calendar.xlsx |
Fifty six slots across four weeks and two departments, at the cadence each one declared | Hand it to whoever publishes. Nothing here posts itself and Claude cannot post |
14-testing-dashboard.xlsx |
Twelve one variable tests with decision rules written before the test runs, plus one test that ran and failed its own sample rule | Read the TST-01_Verdict tab. It shows a winner that was not adopted |
15-platform-adaptation-matrix.xlsx |
Forty five rows, three per asset, plus the standing platform profiles and a difference check | Run your eye down the Difference_Check tab. Three identical exports is a fail condition |
16-template-pack.xlsx |
Fourteen working templates, T15 to T28, from the evidence ledger to the test card | Copy a tab when an agent asks for one. Each carries the record header contract already |
17-creator-brief-template.md |
T29, the blank creator brief with the five point check before you send it | Copy it per brief. It is written to be forwarded, so the internal header comes off first |
18-monthly-learning-report-template.md |
T30, the blank monthly learning report | Fill it at the end of every cycle, from the results tab and nothing else |
19-worked-example-consumer-app.md |
A full run on a fictional consumer app: charter, territories, concepts, brief, shot list, three exports, calendar, results | Read it if you want to see what a finished cycle looks like before you start one |
20-worked-example-mobile-game.md |
A fictional mobile game run week by week, including the trend claim that got rejected. It stops at distribution: that studio supplied no results, so it carries no learning report and says so | Read the week three section. It shows what the department does when somebody says something is trending |
21-results-input-populated-example.xlsx |
Thirty two populated result rows, the derived metrics, and the cycle totals with every calculation shown | Divide one column by another and check it. Then copy the shape into your own T14 |
22-monthly-learning-report-example.md |
The learning report produced from that file: three findings, one failed test, keep change retire, next cycle, brief amendments | This is the output, not a description of one. Every figure recomputes from the file above |
short-form-video-department.zip |
Everything above, in seven folders | Grab everything at once |
Said plainly, because half of what gets sold as an AI content department quietly assumes otherwise.
This department plans, writes and structures. It does not access social accounts. It does not contact creators. It does not film video. It does not publish content. It does not read performance data you have not supplied.
Four specifics: