Skip to content

Getting Started

The 60-second tour of what this pipeline is and how it operates.

The big picture

The pipeline turns a single product brief into ready-to-post short-form videos across multiple accounts and languages. Every stage is delegated to a specialized agent; the Manager is the director that coordinates them.

flowchart TB
    User[User Brief]
    Manager[Manager / Director]
    SW[Script Writer]
    VP[Visual Planner]
    IP[Image Prompter]
    VEO[Veo Prompter]
    PWI[PatchWork Importer]
    GR[Generation Runner]
    PW[PatchWork .nbflow]
    Out[Final Videos]

    User --> Manager
    Manager --> SW --> Manager
    Manager --> VP --> Manager
    Manager --> IP --> Manager
    Manager --> VEO --> Manager
    Manager --> PWI --> PW
    PW --> GR --> Out

The cast

Component Role
Manager The director. Coordinates stages, passes outputs between agents, owns the user-facing summaries.
Script Writer Five script modes (Schwartz framework, TikTok compliance). Writes new scripts, adapts existing ones, makes variants.
Visual Planner Decomposes a script into scenes with camera angles and B-roll planning. Produces the storyboard.
Image Prompter Image prompts for NanoBanana 2 (plain text + JSON).
Veo Prompter Video prompts for Veo 3.1. Speaking scenes use the universal talking head template.
Seedance Prompter Video prompts for Seedance 2.0 (Jimeng web UI).
PatchWork Importer Builds the .nbflow workflow file with all prompts wired in.
Generation Runner Executes the .nbflow headlessly via the G-Labs API. Reviews output for AI tells, auto-retries flagged images.
Strategist / Researcher Strategy briefs, audience research, trend scanning, competitor analysis.

The output

Workflows ship as .nbflow files — JSON descriptions of a graph of prompt nodes and generation nodes that PatchWork can execute. Each .nbflow contains one tab per account so a single file fans out across every target account simultaneously.

Standard operating procedure

USER BRIEF → VIDEO PLAN → (approval) → PATCHWORK FILE → GENERATION → REVIEW → FEEDBACK
  1. Brief — gather product, audience, tone, visual direction, sales channel, B-roll density.
  2. Video Plan — script + visual storyboard, presented together for approval.
  3. PatchWork File — image prompts, video prompts, and the .nbflow itself, generated automatically once the plan is approved.
  4. Reference Material — checklist of avatar photos, product photos, etc. that the user supplies.
  5. Generation — Generation Runner executes the workflow, produces 4 candidates per prompt for the user to pick from.
  6. Review — user opens the -generated.nbflow in PatchWork, picks the strongest takes, reruns failures.

Each stage is detailed in the Pipeline Overview.

How outputs are organized

Every workflow has a predictable folder layout under the project tree:

Folder What it holds
{growth\|sales}/testing/ Workflows still in the testing phase (V0-N versions)
{growth\|sales}/approved/ Workflows that have been approved (V1 and up, including variants)
{growth\|sales}/backups/ Snapshots of older versions before destructive edits
Generations/ Output from the Generation Runner (flat, one file per run with timestamp)
Assets/{workflow}/ Supporting files per workflow: scripts, storyboards, source video, contact sheets, per-scene prompt files

See the Glossary for what V0-N, Lvl 1-4, and other terms mean.