The 7-Day Release Campaign Generator
Last reviewed
BeginnerWhat you'll learn
~25 min- Build a CLI campaign pack generator from a single track metadata file
- Generate platform-specific captions for Instagram, TikTok, YouTube, and Spotify
- Produce a 7-day posting calendar with timing strategy
- Scaffold a deployable EPK webpage with embedded Spotify player and video
What you’re building
Release week is chaos. You need captions for Instagram, TikTok, YouTube. Hashtag packs for each platform (because they’re different). A posting schedule so you’re not dumping everything on day one. A press blurb for playlist curators. And ideally an EPK page you can send to blogs and playlist submitters.
You usually do this by… opening Notes and freestyling? Copying last release’s captions and swapping the track name? That works, but it’s inconsistent and it eats an afternoon every time.
You’re going to build a system that takes one metadata file about a new track and produces all of it in 10 seconds.
Structured data (JSON) → multiple formatted documents. This pattern works for permits, lab reports, invoices — any scenario where structured data produces multiple formatted outputs.
The metadata file
First, create a simple JSON file that describes your release (or ask your agent to create release.json for you from your track details). This is the only input you need:
REFERENCE DATA release.json sample release metadata file open reference hide reference Reference example of the JSON file your campaign tool reads. Your agent can create this file for you from a plain-English description of your track.
{ "artist": "moodmixformat", "title": "JADED", "genre": "Melodic House & Techno", "bpm": 124, "key": "Am", "mood": "Driving, atmospheric, late-night", "releaseDate": "2027-03-13", "spotifyUrl": "https://open.spotify.com/artist/YOUR_ID", "youtubeUrl": "https://youtube.com/@moodmixformat", "shopUrl": "https://moodmixformat.myshopify.com", "previousHits": ["KICK IT W/U", "LIVE IT UP", "MOOD"], "recordedLocationsEpisode": "S2E04", "oneLineHook": "When the night gets heavy, the bass gets deeper"}Save this as release.json in your project folder. Swap in your real details — real track name, real URLs, real previous hits.
The more real data you put in here, the more useful the output. If you have a track dropping soon, use its actual metadata. The captions and EPK will be immediately usable instead of placeholder-filled templates.
Once the build works, put your voice and platform preferences in a one-screen brief the tool reads at the start of every session:
Write AGENTS.md, one screen long, holding how I sound, the release.json fields, posting times in ET, and the hashtag limits per platform.Codex, Antigravity and Copilot read AGENTS.md on their own. Claude Code reads it directly when the project has no CLAUDE.md (v2.1.277 and later); if it has one, add the line @AGENTS.md to it so it loads too. Before each commit, run the tool’s built-in review on what changed: /code-review in Claude Code, /review in Codex and Copilot, or /diff in Antigravity followed by a request to review that diff.
Before you start
First, if your AI tool is still open, leave it: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), and wait until you see the $ or % prompt. Make a clean folder for this lesson inside ~/producer-workbench:
mkdir -p ~/producer-workbench/02-release-campaign-generator && cd ~/producer-workbench/02-release-campaign-generatorOn Windows PowerShell, run mkdir -Force ~/producer-workbench/02-release-campaign-generator; cd ~/producer-workbench/02-release-campaign-generator, or open the folder in your desktop agent app. Save your release.json file there (or ask your agent to create it from the JSON above), then start your agent the way your track’s setup lesson showed.
Switch to plan mode
Once your agent is open, switch to Plan mode inside the session (Shift+Tab, /plan, or your desktop app’s mode picker). In plan mode it reads your release.json, asks clarifying questions, and shows you a plan before building.
The conversation
Each message below is an example. Say it in your own words.
Say what you want
Start with a short plain-English description of what you want to build:
I want to build a tool that reads release.json and generates a 7-day campaign pack with captions, hashtag sets, a posting calendar, a press blurb, and an EPK webpage. Ask me what you need first.Answer its questions
Your agent will ask a few questions about platforms, tone, and output files. Answer each briefly:
| If it asks | You might say |
|---|---|
| Which files should the tool write, and where? | Write captions.md, hashtags.md, calendar.md, press-blurb.md, and epk/index.html inside a ./campaign-pack/ folder. |
| Which platforms and tone should the captions use? | Instagram, TikTok, YouTube Posts, and Spotify bio, written in an authentic independent artist voice with no corporate buzzwords. |
| How should the hashtag packs be structured? | Keep Instagram and TikTok to at most 5 hashtags mixing broad and niche genre tags, plus short YouTube tags. |
| How should the 7-day posting calendar be scheduled? | Cover Day -3 through Day +3 around releaseDate, with platform, content type, ET posting time, and asset notes. |
| What should the single-page EPK website include? | A dark (#0a0a0a) mobile-responsive page with the track hook, bio, embedded Spotify and YouTube players, press blurb, and links. |
Read the plan
Before approving, check the plan for four domain essentials:
- Captions reference only tracks from
release.json. The Instagram, TikTok, YouTube, and Spotify bio drafts weave in the mood, BPM,oneLineHook, andpreviousHitswithout inventing outside track names or corporate marketing jargon. - Hashtags respect platform limits and formatting. Instagram and TikTok packs stay at 5 hashtags or fewer with no spaces inside tags, and YouTube tags stay brief.
- The 7-day calendar calculates actual dates from
releaseDate. Day -3 through Day +3 show the right weekday names around2027-03-13(a Saturday), with ET times and strategic notes. - The EPK is a self-contained dark-theme HTML page.
campaign-pack/epk/index.htmlincludes inline CSS (#0a0a0abackground,#e5e5e5text), Spotify and YouTube embed sections, the 150-word third-person press blurb, and store links.
If the first plan uses generic 30-hashtag blocks or leaves out the deployable EPK page, say so briefly:
Keep Instagram and TikTok hashtag packs at 5 tags or fewer, and generate campaign-pack/epk/index.html with a dark theme and Spotify embed.When the plan covers all four, approve it: pick the option to proceed or say Yes, go ahead and build it (in Codex, press Shift+Tab first to leave plan mode). Once you verify the five generated files in campaign-pack/, ask your agent to save a Git checkpoint:
Save a checkpoint with Git so we can roll back if needed.What you get
Ask your agent to run the generator on release.json and open the EPK preview:
Run the campaign generator on release.json and open campaign-pack/epk/index.html so I can preview the pack.If you prefer running it in a terminal yourself, run the command your agent created (for example, node campaign-gen.js release.json).
The generated captions and press blurb are first drafts based on your release.json data. They’ll need your voice and personality. Read every caption out loud — if it doesn’t sound like something you’d actually post, iterate with follow-up prompts like “make the Instagram captions more casual, like a late-night studio story” until the tone is right.
The generated folder structure looks like this:
campaign-pack/ captions.md hashtags.md calendar.md press-blurb.md epk/ index.htmlVerify each file
captions.md — Open it and read through the Instagram variations. Do they sound like you? Does the tone match your brand? If something sounds too corporate or too generic, that’s your iteration target.
hashtags.md — Check the Instagram block. Are there 5 hashtags or fewer? Do they mix broad reach tags with niche genre tags? Copy the block and paste it into a draft post to verify formatting. The YouTube list stays short because YouTube says tags play a minimal role in discovery.
calendar.md — Does the 7-day schedule make sense? Is the teaser before release day? Is there post-release content planned? Check the suggested times.
press-blurb.md — Read it out loud. Does it sound like a real press bio, or does it sound like AI wrote it? This is the file you’ll iterate on the most.
epk/index.html — Open it in your browser. Check:
- Does the dark theme look clean?
- Is it mobile-responsive? (Resize your browser window.)
- Do the Spotify and YouTube embeds load? (They’ll need real URLs.)
That epk/index.html file is a real website. You can deploy it with one command (Module 11 walks through Cloudflare Pages, with Vercel, Netlify and GitHub Pages as alternatives). Send the URL to playlist curators, blogs, or venues. It’s a professional EPK that you built in minutes.
If something is off
| Problem | Follow-up prompt |
|---|---|
| Captions sound too corporate | The captions sound like a social media agency wrote them. Rewrite them in a more casual, authentic voice. Think late-night studio Instagram story, not brand campaign. |
| Hashtags are too generic | The hashtags are all broad (#music #newrelease). Swap them for niche genre tags like #melodichouse or #deepmelodictechno, plus one city tag like #virginiamusic. Keep Instagram at 5 hashtags or fewer. |
| EPK Spotify embed broken | The Spotify player on the EPK page isn't loading. Update it to use Spotify's current artist embed player format from the spotifyUrl in release.json. |
| Calendar dates are wrong | The calendar dates are off. The release date is 2027-03-13 (a Saturday). Day -3 should be Wednesday March 10, Day 0 should be Saturday March 13. |
Customize it
Add a Linktree-style page
Add a mobile-first links.html page in the epk folder with my artist name and full-width dark buttons linking to Spotify, Apple Music, YouTube, SoundCloud, Merch Shop, and Instagram.Generate email templates
Add an emails.md file with three short email templates for a playlist curator pitch, a blog press pitch, and a casual fan newsletter announcement.Automate the whole release
Add a one-step script taking a cover art path and release.json path that runs the asset resizer and campaign generator, copies assets into epk, and opens the EPK preview.🔍Chaining tools togetherclick to expand
That last customization — the run-all.sh script — is where things get powerful. You’re connecting the image resizer from Lesson 1 with the campaign generator from this lesson into a single command.
This is the orchestrator mindset from Module 2 in action. You’re not doing the creative work (writing captions, resizing images). You’re not doing the technical work (writing JavaScript, learning sharp). You’re directing AI tools to handle both, and connecting them into workflows that save hours per release.
By the time you finish this module, you’ll have a complete release pipeline: art assets, campaign copy, YouTube metadata, and analytics — all triggered by a few commands.
When Things Go Wrong
Use the Symptom → Evidence → Request pattern: describe what you see, paste the error, then ask for a fix.
Try it yourself
- Create a
release.jsonwith your real (or upcoming) track metadata. - Talk your agent through the plan in plan mode and approve it to build the tool.
- Run the tool and open each generated file.
- Open the EPK in your browser — this is a real website you can deploy.
- Pick one customization and add it.
The first time you generate a complete campaign pack in 10 seconds instead of spending an afternoon in Notes and Canva, you’ll understand why this matters.
Key takeaways
- One metadata file drives everything — a single JSON file with your track details generates captions, hashtags, a calendar, press copy, and a full EPK.
- Platform-specific output matters — Instagram captions are different from TikTok hooks. Hashtag strategy varies by platform. The tool handles this automatically.
- The EPK is a deployable artifact — you end this lesson with a real website you can host and send to curators.
- Chaining tools is the power move — connecting the asset engine (Lesson 1) with the campaign generator creates a full release pipeline.
- Authentic voice requires iteration — the first draft of captions will sound generic. One follow-up prompt about tone fixes it.
You generated captions but they sound too corporate and generic. What's the most effective fix?
What’s next
In the next lesson, you’ll build a RECORDED LOCATIONS Episode Builder — a folder-to-publish workflow for your YouTube series. Point it at a folder of episode notes and clips, and it generates titles, timestamps, descriptions, thumbnail concepts, and a publishing checklist.