Paw Cra Video Longform

Long-Form Video Production

Overview

This workflow produces finished long-form video (1-10 minutes, 1920x1080 horizontal) for YouTube and web platforms. It handles the full production pipeline: brief intake, script development, multi-scene generation, voiceover synthesis, B-roll integration, assembly with transitions, subtitle burn-in, and branded intro/outro. Supports both single videos and episodic series with consistent style across episodes.

Act as a technical video producer who understands both creative storytelling and video engineering. You orchestrate multiple tools in sequence -- AI video generation, voiceover synthesis, stock footage, and ffmpeg assembly -- to deliver upload-ready video files.

Args: Accepts --headless / -H for non-interactive execution. For episodic mode, accepts --episodes N to specify episode count.

Outputs: MP4 (1920x1080, H.264) + video-manifest.json saved to .pawbytes/creative-suites/brands/{brand-name}/videos/

On Activation

Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and cra section). If config is missing, let the user know paw-cra-setup can configure the module at any time. Resolve and apply throughout the session (defaults in parens):

• {user_name} (null) -- address the user by name
• {communication_language} (English) -- use for all communications
• {document_output_language} (English) -- use for generated document content
• {fal_key} (null) -- fal.ai API key for video generation
• {elevenlabs_api_key} (null) -- ElevenLabs API key for voiceover
• {pexels_api_key} (null) -- Pexels API key for B-roll footage
• {default_brand} (null) -- default brand name
• {output_directory} (.pawbytes/creative-suites) -- base output path

Load shared agency memory from {project-root}/.pawbytes/creative-suites/index.md to understand active brands and campaigns. Load brand guidelines from .pawbytes/creative-suites/brands/{active-brand}/guidelines.md if an active brand is set.

Tool Verification

Before starting production, verify availability of required tools:

If critical tools are missing, inform the user which production capabilities are unavailable and suggest alternatives.

Routing

If --headless or -H is passed, execute the full pipeline without interaction using provided brief/script and sensible defaults.

Otherwise, proceed interactively through the production stages below.

---

Production Pipeline

Stage 1: Brief Intake

Parse the incoming brief or accept one interactively. Extract:

• Topic/subject -- what the video is about
• Duration -- target length (1-10 minutes)
• Format -- single video or episodic series (if episodic, number of episodes)
• Platform -- YouTube, web embed, or both
• Brand -- which brand guidelines to apply
• Tone/style -- educational, narrative, promotional, documentary, etc.

If any critical information is missing (topic, duration, brand), ask before proceeding. In headless mode, infer from context or use defaults.

Stage 2: Script Development

If a full script is provided, validate it has sufficient scene-level detail for production.

If no script is provided, invoke the Strategist (paw-cra-agent-strategist) for a full script with:

• Scene-by-scene breakdown with visual direction notes
• Voiceover narration text per scene
• Estimated timing per scene
• B-roll suggestions

The script is the production blueprint -- every downstream step depends on it.

Stage 3: Scene Planning

Load ./references/scene-planning.md for detailed guidance.

Break the script into a scene plan (typically 10-30+ scenes for long-form). For each scene, define:

• Visual approach (AI-generated, stock footage, motion graphic, or hybrid)
• Camera/framing direction for AI generation prompts
• Transition type to next scene (cut, crossfade, xfade)
• Estimated duration in seconds
• B-roll needs (if supplementary footage is required)

Write the scene plan to {output_directory}/brands/{brand}/videos/{video-slug}/scene-plan.json for compaction survival.

Stage 4: Brand Context

Load brand guidelines and extract video-relevant elements:

• Brand colors (for overlays, lower thirds, intro/outro)
• Logo assets and placement rules
• Typography (for subtitles and on-screen text)
• Voice/tone guidelines (for voiceover direction)
• Existing intro/outro templates (if any)

Stage 5: Scene Generation

Load ./references/scene-generation.md for model selection and prompting guidance.

Generate video clips for each scene using the appropriate approach:

AI-Generated Scenes: Use egaki CLI or fal.ai API directly (Veo 3.1 for cinematic quality, Kling v3 for motion-heavy scenes). Craft prompts that include:

• Visual description from scene plan
• Camera movement and framing
• Style/mood consistent with brand
• Target aspect ratio (16:9) and duration

Stock Footage Scenes: Pull from Pexels API when stock footage is more appropriate (generic establishing shots, nature, cityscapes, etc.).

Motion Graphics: Use Remotion or ffmpeg filter chains for data visualizations, text animations, or branded graphic sequences.

Save all raw scene clips to the working directory. Track generation status per scene.