Story structure
Write audience promises, character motivations, conflicts, turning points, and cliffhangers into checkable beat sheets.

FORMWEFT ORIGINAL · METHOD
By default, complete the script, character continuity, storyboards, task list, and acceptance sheet first; only after tools, data destinations, and authorizations are approved do you proceed to actual generation and assembly.
The real challenge is keeping multi-episode, multi-character, multi-shot work traceable, replaceable, and reviewable amid change.
Write audience promises, character motivations, conflicts, turning points, and cliffhangers into checkable beat sheets.
Use stable IDs, visual anchors, locked elements, and reference assets to reduce face swaps, wardrobe changes, and spatial jumps.
Images, video, audio, and subtitles all enter through declarative adapters - don't lock the entire pipeline into one model.
Technical completeness and creativity are reviewed separately; rendering completion does not mean final approval.

SEVEN GATES
Each step leaves behind replaceable structured artifacts; when issues arise, return to the relevant checkpoint rather than discarding the whole pipeline.
BRIEF
Confirm audience, platform, aspect ratio, duration, language, budget, rights, and success signals.
STORY
Complete character bibles, scene bibles, season and episode arcs, and beat sheets.
SHOT
Record shots, performance, continuity, audio, transitions, and negative constraints.
GENERATE
Use swappable providers, preserving version, seed, input, state, and failure diagnostics.
ASSEMBLE
Align subtitles to the final audio and retain a clean master without platform packaging.
QA
Full decode inspection and full manual creative review are performed separately.
DELIVER
Delivery master, subtitles, poster, checklist, rights, hash, and known limitations.
The download package is a method and structure template. It does not include model weights, third-party ComfyUI nodes, account keys, or auto-publishing code. People, voices, music, and assets still require authorization from the project owner.
For real people's likenesses, voices, and identifiable images, explicit authorization must be documented first.
Generation complete, technical pass, human approval, delivery, and launch are different states.
Third-party custom nodes can contain arbitrary code and must be reviewed separately.
Record the model, version, data destination, costs, and failure statuses.
TRUST MANIFEST
The current download package is a method and structure template. The MIT license covers only original FORMWEFT documentation, not models, third-party tools, assets, or generated content. This page's review record applies only to this fixed ZIP and its hash.
You can download this reviewed version's resource package. If it includes SKILL.md, provide it and the related documentation to your AI tool; first read and check the materials and usage boundaries, and do not run anything automatically.
You can also select the text to copy directly; read it first before executing.
FORMWEFT original documentation-type Skill, intended by default for production planning and acceptance design. Structural checks, offline static scans, and manual file-by-file reviews are complete. The download package contains no scripts, dependencies, model weights, keys, auto-uploads, or auto-publishing. MIT covers only original documentation and templates, not third-party tools, models, assets, or output.
4e9d46aa1ba3ff17e0d29cb1905dcd65c01dc834340ee5871938b35bc4f73287
Describe your content types, output, existing tools, brand assets, approval chain, and channels, and we can scale the approach into your business's own AI video workbench.