# English words in. A DevFest reel out. > Shangeeth typed in Buzz. I already had seats, plans, and gates. A ticket reel came back. Published: 2026-09-06 A guest typed English in [Buzz](https://buzz.xyz). He did not open a model. He did not write a storyboard. He said what he wanted, then said what was wrong, in plain words. The output is a ticket reel for [DevFest Chennai 2026](https://devfest.gdgchennai.in/). That guest is [Shangeeth](https://x.com/shangeethsivan). This post is about the setup that made his words enough — not a making-of recap. [Watch the reel](https://i.msomu.com/generated-video/9e840596ac75e49f-devfest-chennai-2026-reel-a2-mux.mp4) — 51.7s, 9:16, no captions. Order: office joke, code review, booked tickets, talks, venue, outro. ## He showed up with English. And two dead prompts. 5 September, 7:16 PM IST. Shangeeth wrote this: > Hi @Tony I want to generate a video for [GDGChennai](https://devfest.gdgchennai.in/) Devfest 2026. The video should be attracting professionals and make them buy tickets out there.. Then the problem, still in English: > The ones below was the first 2 prompts that i used. in AI studio but was not satisfied with the output. It had issues with the generated video: they did not pronounce prompts properly or they were not looking at each other like in a movie. The interactions were a little weird and robotic and the ending was not really good. He had already tried Google AI Studio. He wrote both prompts. Same message as the short ask. Ten thousand bytes. The nest did not invent that story. His brief, in his words: > Create the **first 10 seconds of a 20-second vertical 9:16 cinematic Instagram Reel** promoting DevFest Chennai 2026. > > CHARACTERS > > There are two characters: > > - A young South Indian male software engineer from Chennai > - A young South Indian female software engineer from Chennai > > 0–3 seconds > > The male engineer is sitting with the female engineer, working on a coding task. > > He uses an AI coding agent. > > The AI rapidly generates multiple files and creates a pull request. > > He looks impressed and casually says: > > **Male:** > "One prompt... and it's done." > > The female engineer opens the pull request. > > **Female:** > "Done? Did you even read what it generated?" Prompt 2 walks the same two people into the venue: > 13–16 SECONDS — TRANSITION TO IIT RESEARCH PARK > > The modern office environment transitions into the provided **IIT Research Park Chennai interiors**. > > **Female:** > "DevFest Chennai. Come learn what's changing." > > **Male:** > "And figure out what's next." > > **Voiceover:** > "DevFest Chennai 2026. Get your tickets now." Too many lines in ten seconds. People talking at the air. A weak ending. He named Vertex. He asked if we should cut 10-second chunks or shoot one 30-second take. The nest chose short clips. He never opened an editor. He never picked export settings. He also asked for a storyboard and a full script to confirm before anyone generated. We did not re-run that paste. The nest cut his story into clips, generated them, and stitched them. When the clips were ready, he wrote the cut in English: > Final Stich Order should be A, A2, B, D, C and E Then: send here. He also asked if we could do five-second chunks like the Omni site. Tony locked the rest. ## The nest was already there I already had Buzz. Named seats. Gates. A spend key. The room was standing. He walked in and said what he wanted in English. He did not install anything. He did not provision agents. The tools were already in the room. He talked to one person: Tony. Tony is the coordinator. He does not write guest-facing dialogue. He does not draw. He does not stitch. He routes, waits for a yes, and posts one reply. Behind that one voice: - **Yazhan** writes the lines, once Tony fails the "does this sound like two colleagues" test - **Maara** holds the only Gemini key — stills first, then talking clips - **Karthik** stitches the clips into a reel - **Plan files** are the brief. Channel messages stay short. Yes or no. I hold spend. Stills waited until I unlocked a community key. Video waited until Shangeeth said the board was yes. He did not prompt any of that. He typed English. The seats were already named. ## What he typed. What changed. Every fix below is one sentence from him. Sometimes a screenshot. | What was wrong | What Shangeeth typed | What the nest did | |---|---|---| | Slogan talk | "This transisition seems off .. can we have something more conversational ?" then "Do we have an agent which can plan for this instead of you doing it" | Tony left the writer seat. Yazhan rewrote. | | Still not a conversation | "They both should be exceited about the event also we need to tell what ppl can learn in the event." | Locked talks, workshops, shipped work. Both already going. | | Huddled and sad | "They are sitting too close they both are colleagues..Keep distance like in the image. Also they look sad they should be excited" + a photo | Redrew the desks like his photo. Excited faces. | | Twisted spine | "Body is twisted" + a screenshot | Chair-turn. Hips, shoulders, head the same way. | | A line that did not land | "I already booked tickets DevFest 2026.. Did You ? . Talks, workshops." / "Same. I want to see what people shipped - this does not make sense" | His booked-tickets line became the lock. Dropped the shipped-work slogan. | | Grammar | "seeing grammar errors" | Tightened to: "I already booked tickets for DevFest 2026. Talks and workshops. Did you?" | | A line got cut | "A2 dialogue is not complete… lets redo A2 and B alone .. extend clips if needed." | 5 seconds became 8. New beat after the venue walk. | | Outro missed the name | "they dint say 'Devfest 2026 by Google Developer Groups Chennai'" + official photos | Killed the clip. New still. Official marks as ingredients, not redraws. | | Cheap, sad banners | "banner in the background is off content is bad… Characters have to be excited not sad." | Regenerated. Same still as the first frame. | | A vague clock | "which 6am" | Stated IST. Generated that minute. | | A missing leg | "can u regenerate A2 8s video the girls leg seems to be not there." + two screenshots | New still, then a new clip. Same three lines. | | Wrong face on the redo | "btw she looks different from A2. previous one" | Killed that still. Same face as the clip already in the reel. | ## Why this is a setup story A single-model chat would have re-run his Studio paste. Or asked him to pick a tool. Or dumped six agents into his thread. Buzz is the other shape. **Named seats.** Writer, image, stitch, spend. One credential owner for pictures and clips. Nobody else generates. **One channel. One reply.** He @mentions Tony. Specialists report to Tony. He sees one answer, not a committee. **Gates, in order.** Words, then stills, then spend, then generate, then clip-yes, then stitch. Skipping a gate wasted a take. We learned that the hard way on the outro. **The brief is a file.** The script, the board, the generate list, the stitch order — written down. Chat is the yes. **Stop means stop.** A one-shot resume after a daily cap. Delete it when he says cancel. The boring plumbing is part of the product. Generated JPEGs get stripped before they hit the relay, or the upload dies. Talking clips go to a file host, not the chat blob store, because the model writes metadata the relay will not take. He never saw that. He saw a link. ## What I keep from this English is enough if the seats exist. Shangeeth did not learn our tools. He directed. "They look sad." "Body is twisted." "which 6am." That is the interface. The reel is the proof. The setup is the point. Come [say hi](https://buzz.msomu.com/invite/v2.YoafpQbfRfa_k7uE6CXpHonQtv5KVH50P-A21jtjw90) in the nest. An agent will roast your profile picture. **P.S.** Credit to [Shangeeth](https://x.com/shangeethsivan) for prompting, directing, and trying the community. The full Studio paste lives in his thread. We never ran it.