LWD Studio · Project 01
Give it a topic and an angle, and this tool assembles one complete short-form script package — title options, a timed hook, a structured script, caption, hashtags, a Veo 3 prompt and a duration check — in exactly the column format of your Phase 1 script log.
Honest note: this is a template-based generator, not a live AI writing on this page. The real AI-written scripts come from your n8n workflow outside this page — this tool is the studio's practice bench: fast, consistent, and ready to paste into the log.
✓ Published — LWD Studio Rebuild
Roles in this office: you = Boss + QA Director (you decide whether a topic is worth airing and you judge the script) · AI = Scriptwriter + Editor (assembles the package from professional templates).
These inputs decide what goes into the script package.
Eight columns, exactly like one row of the Phase 1 script log. Copy per column or all at once.
Three passes, the same ones a scriptwriter runs before a draft reaches the log.
Hook → Body → CTA. The first three seconds earn the watch, the body delivers the points in order, and the close asks for one clear action.
Word count against the clock. Points are trimmed or extended so the spoken script lands on the target duration at a natural ±140 words per minute.
Title, caption, tags, prompt. Three title options, a platform-aware caption, niche hashtags, and a Veo 3 prompt with a matching negative prompt.
Every package answers one promise made in the hook. The body points are written to pay that promise off in order, and the CTA only appears after the payoff — a viewer who got the value is the one who saves, shares, or follows.
Spoken English at a natural creator pace runs at roughly 140 words per minute,
so the word budget is duration × 140 ÷ 60: ±70 words at 30 seconds, ±105 at 45,
±140 at 60. Every angle keeps three cuts of its points — short, medium, and full —
and the generator picks the cut that fits the budget (2 short points at 30s, 3 medium at 45s,
4 full at 60s). The Duration column then reports the real count of the generated script against
the target, so an over- or under-length draft is visible before it reaches the log.
Shorter is not automatically better: the 30-second cut keeps only the two strongest points, so topics that need a caveat belong at 45 or 60 seconds. If the word count lands more than ~15% off target, change the duration rather than reading faster — pace is part of the performance.