The problem this solves
Launch weeks die by a thousand asset requests. The announcement needs a hero. The social post needs a square. Stories need a vertical. The blog needs an OG image so the link unfurls properly, and somebody inevitably asks for a short clip the day before. Each format is a separate request to a designer who is already overbooked, so the kit arrives piecemeal, the sizes drift out of sync, and the launch thread fills with versions nobody can tell apart.
The deeper problem is coherence. A launch lands harder when every surface - homepage, feed, story, link preview, teaser - visibly belongs to the same moment. Assembling that coherence by hand means one person holding five aspect ratios and one visual idea in their head simultaneously, under deadline. Most teams settle for whichever three assets got finished, ship the launch anyway, and quietly accept that the story format and the OG image never happened.
How the mission runs
- Read the launch from the thread. The agent starts with the launch described in your thread: what is shipping, who it is for, and the one line that should survive every crop. It locks a single visual concept and copy hierarchy before generating anything, so all five assets come from one idea instead of five separate improvisations.
- Generate the image set. Image Generation produces the four stills - landscape hero, square feed image, vertical story, and OG image - each composed for its placement rather than cropped from one master. Draft-quality passes settle the concept cheaply; the four finals render at final quality once you approve the direction.
- Produce the teaser clip. Video Generation turns the same concept into an 8-second vertical teaser built to stop a scroll: a hook in the first second, the product moment, and the launch line. Because the clip inherits the approved visual direction, it lands as part of the kit rather than a separate production.
- File everything to Drive. All five assets are saved to a dated launch folder in Google Drive with clean, predictable filenames that state the format and dimensions. Whoever schedules the posts finds one folder containing everything, at full resolution, with no version-guessing and no digging through a chat scrollback for attachments.
- Post the kit to #launches. The agent posts the complete kit to your #launches channel in Slack: every asset previewed, the Drive folder linked, and a one-line usage note per format. The team sees the whole kit at once and can flag any fix in the thread before the launch goes out.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
Five finished, launch-ready assets in one Google Drive folder: a landscape hero, a square feed image, a vertical story variant, an OG image sized for link previews, and an 8-second vertical teaser clip. All four stills render at final quality, filenames state format and dimensions, and the full kit is posted to #launches with previews and the folder link, so distribution can start the moment the team says go.
Make it yours
- Ask for two competing visual directions at draft quality first, pick the winner in the thread, and have only the winning direction rendered as the full five-asset kit.
- Extend the kit for a product with multiple audiences: the same launch concept rendered twice, one set framed for practitioners and one framed for executives.
- Compress it for a minor release: skip the clip, produce hero plus OG image only, and have the pair filed and posted within the same mission.
Frequently asked questions
How does the kit stay on brand?
The agent applies your brand kit across every asset - palette, type treatment, logo placement - and holds one visual concept through all five formats. Because the whole kit comes from a single mission, coherence is structural: every crop is composed from the same approved direction instead of assembled from parts.
What if I want changes after seeing the kit?
React in the Slack thread or the mission thread and the agent revises. Stills regenerate quickly, and because concept approval happens at draft quality before finals render, most revisions are cheap. The clip can be re-scripted and regenerated too; you approve the storyboard line before it renders.
What formats and sizes do the files come in?
Standard placement-native dimensions: landscape hero and OG image in wide format, the feed image square, the story and teaser vertical. Files land in Drive at full resolution in web-ready formats, named by placement, so they can be uploaded directly to each channel without further export work.