Agent team
Agentic AI
Creative Studio, a product I built: a small team of AI roles that takes a brief to delivery, with a human at every gate.
- Status
- A working product called Creative Studio (Design. Ads. Video. Landing.). It runs as a team structure with skills and workflows, and the host environment provides the execution tools.
A user asks for a packaging design and a native ad banner. The Lead agent plans the route, the Creative Director approves it, the Design agent builds both, a QA gate checks them, and the banner and the packaging are delivered. The Video Editor and the Landing Builder are not needed for this brief.
A simulation of how I work with it. The sample product and its outputs are illustrative.
The problem
Creative production breaks when AI is used one prompt at a time. Product facts drift, approved parts get rewritten, and costly generations are spent before anyone has agreed on the direction.
How it runs
1Brief intake
Fix the goal, audience, channel, format and number of outputs. Ask only for what is missing and matters.
2Asset audit
Check the latest source, packs, logos, copy and references. Decide the source of truth, what is locked and what is editable, and keep the original.
Rule it follows: Lock means lock: change this part, keep everything else. Text on a product pack is never translated or regenerated.
3GEO and research
Fix the market, language, localization scope and what stays untranslated. Research the category, competitors and audience when needed, and keep the sources.
4Creative strategy
Connect audience, pain or desire, mechanism, hook and call to action. A product mechanism needs grounds, and an untested angle is labelled a hypothesis.
Rule it follows: Product facts, outside research and creative hypotheses stay separate. A reference is not proof, and no health benefit, testimonial, certificate or discount is ever added.
5Human approval
I approve creative routes, copy, claims and assets before any costly production. Video follows a fixed order to waste as few generations as possible: planning, reference image, approval, video, selective repair, assembly.
6Generation and editing
Reuse first, create new when needed. Edit only the area or shot that needs it, keep what already works, then assemble in sequence.
Rule it follows: Routes must differ in idea, not just in colour or size. Mockups keep true geometry, and a raster concept is never called print-ready.
7QA and localization
Check product identity, claims, text, fonts and glyphs, line breaks, layout and format. Video adds continuity and audio sync, landing pages add mobile, links, forms and calls to action.
Rule it follows: Localize in context: natural language, the right script, people and settings that fit. Flags and landmarks appear only for a reason.
8Delivery
Hand over by market, language, format and version, with preview and source. State clearly whether it is a concept, a mockup, final or published, and keep the approved version for rollback.
What exists today
- Plans, creates, clones, adapts, localizes and reviews product packaging, native ads, video and conversion-focused landing pages, while preserving source assets, factual content, product identity, GEO requirements and creative direction.
- Eight defined stages from brief intake to delivery, each with its own rules.
- Four roles (Lead, Design, Video Editor, Landing Builder) directed by a human Creative Director.
- Work types covered: packaging, native ads and banners, landing pages and video.
- Video is planned inside a fixed credit budget in a fixed order: planning, reference image, approval, video, selective repair, assembly.
What comes next
A storyboard interface, a node graph, chapters, checkpoints and parallel jobs are kept as ideas. They get built only when volume and budget call for them: build V0, but know where V4 sits.
Output samples (banners, packaging, landing pages) will be added here when available.