Thoughts

1 thought about "Creative Pipeline"

UFO UAP RV YT Pipeline - Session 13: Phase 2 creative pipeline architecture decided and built. Key decisions: - Two-tool split for creative pipeline: Gemini (browser/mobile, subscription) handles research and draft scripts via NotebookLM knowledge base. Claude (Code, subscription) handles grading, script refinement, character casting, and visual plan generation. - Handoff layer is a Google Sheet ("UFO Pipeline - Raw Drafts") with two tabs: Raw Drafts (Gemini writes) and Production Manifest (Claude writes). - Subscription-only for creative work (no API calls). API reserved for automated production pipeline (Phases 3-7). - Dave can run Gemini research sessions from his phone and save to the Google Sheet. Two Gemini Gems drafted for A/B testing: - Gem A "UFO Script Factory": single-prompt batch mode, outputs 12-15 scripts per topic in ~10-15 min. - Gem B "UFO Research Lab": conversational 2-phase (research 20-25 angles > Dave selects > write scripts), ~20-25 min per topic. Claude Code skill built: process-scripts. 6-step workflow: read/grade scripts, refine writing, assign characters+outfits+environments, generate visual plans (shot-by-shot JSON with Flux/Luma/Hedra generation prompts using locked LoRA triggers), write production manifest, summarize batch. Content mix: 80% character-led, 20% faceless montage shorts for engagement testing. Production volume: 1 short/day for first 30-45 days, then 2-3/day for 90+ days. Total need: ~250-300 scripts over 4+ months. Pre-launch: 3 Gemini sessions across different topics, ~40 drafts each, cull to ~25 each = ~75 scripts ready before publishing. Files created: docs/gemini-prompts.md (both Gem prompts + Sheet schema), .claude/skills/process-scripts/SKILL.md (Claude processing skill). Next: Create the Google Sheet, build both Gems in Gemini, A/B test on same topic, pick winner, validate end-to-end flow.

People: Dave