<!--
  Public educational copy — Division Agent skill pack.
  Scrubbed for public download: no personal emails, Drive folder IDs, or private paths.
  Status labels such as Working Draft refer to the draft→approved lifecycle, not a site watermark.
-->
---
name: Manus episode video generation
description: >-
  Use when a [series] / [series] episode needs a Manus-ready pack whose
  required deliverable is a finished SRT-timed episode video (not stills-only),
  plus fifteen scene prompts and motion plan for that edit.
---
# Manus episode video generation

Prepare a **Manus-ready pack whose required deliverable is one finished episode video**, built from fifteen cinematic 16-bit dark-fantasy scene prompts and an SRT-aligned motion plan. Stills may be intermediate assets; **stills alone are not success**.

Also known as episode pixel-art video / storyboard work for *[series]*.

## Standing rules

1. **SRT is authority.** Bilingual episode SRT controls dialogue, released sequence, subtitle timing, and the final narrative beat. Plot brief and production handoff supply staging/tone only when consistent with the SRT. Flag material conflicts; never silently rewrite dialogue or insert brief-only events.
2. **Required Manus output = video.** Instruct Manus to export one 16:9 episode MP4 timed to the SRT (Ken Burns / restrained zoom-pan on pixel-art scenes is fine). **Required export format: 1280×720, 25 fps, H.264 MP4.** Do **not** upscale Manus video — keep native Manus size; no 2560×1440 or other upscale. Upload that video to the episode’s Drive folder. Filename pattern when operator uses it: `episode-NN-no-subs.mp4` (or clear equivalent). **Do not burn subtitles into the picture** — Studio uploads separate caption tracks later.
2a. **Drive master uploads (full quality).** When uploading episode MP4s to Google Drive (Studio connector or Manus), upload the **full-quality unconverted** binary (`convertToGoogleFormat: false` / keep as MP4). Google’s **50 MB limit applies only when converting into Docs/Sheets/Slides — not to raw MP4 or other binary files**, which may use Drive storage quota (far larger). **Never recompress, downscale bitrate, or split episode masters just to stay under 50 MB.** Keep the full local master at `/workspace/novel-ch1-west/epNN/video/episode-NN-no-subs.mp4` (or clear equivalent) and prefer that file for remake/YouTube.
3. **Audio.** Prefer picture-led video without final English TTS/music mix (Studio adds music, SFX, and English TTS). If Manus includes temp audio, keep it quiet and do not invent dialogue.
4. **Approved visuals.** Explicit approved production designs control visual continuity. If they conflict with prose, disclose both and keep established looks unless the user redirects.
5. **Child safety.** Keep child characters age-appropriate; all contact protective, familial, or otherwise non-suggestive. Fully clothed staging only.
6. **No spoilers.** Identify the first permitted reveal of each creature/identity/secret and the episode’s final permitted action. Exclude later-chapter facts even if supporting docs disclose them.
7. **Style defaults.** Fifteen scene images feeding one edit; 16:9; cinematic 16-bit dark-fantasy pixel art; subtitle-safe lower 15–18%; Manus-ready copy blocks. User instructions override defaults.
8. **Pipeline note.** Evening pack prep (~21:23 HKT) finalizes this pack; nightly Manus kickoff (~23:50 HKT) pastes it on the series studio’s desktop. Daily 4pm Drive → YouTube Premiere finishes one episode/day; **YouTube upload must stay aligned with Manus format (1280×720, 25 fps, H.264 MP4 — no upscale).** operator keeps public publish.

9. **Anti-misread (Manus is the video producer).** Manus must NOT write another pack, markdown handoff, delivery specification, scene-prompt document, timing table, or continuity report as the deliverable. Those materials are INPUTS the Studio pastes in. **Success = GENERATE then upload** `episode-NN-no-subs.mp4` (or clear equivalent) to the episode Drive folder. Never lead with “Success = upload”. Text/markdown alone = failure. Asking the user for an existing MP4 = failure. If Manus starts rewriting the pack or asking for a file instead of generating the video, stop and paste the CORRECTION message.

## Inputs

**Required:** episode identifier; episode SRT (preferably bilingual Traditional Chinese + English).

**Supporting:** plot brief; relevant manuscript passages; production handoff; character/location refs; approved character images / prior frames. Narration audio is **not** required — Studio adds TTS later; time picture to the bilingual SRT only.

Typical Drive layout under operator episodes folder:
- `Episodes/epNN/the-king-who-woke-up-dead-epNN.bilingual.srt`
- `Episode plot briefs/EpNN-plot.md`
- Part handoff (e.g. `MEDIA-STUDIO-HANDOFF-part1.md`)

Local mirror when present: `/workspace/novel-ch1-west/epNN/`. Save filled packs to `/workspace/shorts-studio/manus-epNN/EpNN-Manus-master-prompt.md` and sync to shared workspace mirror.

## Workflow

### 1. Discover and read sources
Find the exact episode SRT and brief. Read relevant story passages and production refs; inspect approved visuals when available. Report which sources were **actually read** and which remain unavailable. Never claim to have read all files after only listing them. Do not substitute a neighbouring episode.

### 2. Resolve authority and conflicts
Priority order: SRT → approved production designs → story docs (where consistent) → episode brief (where consistent). Unsupported details are provisional production choices, never verified canon. Ask for clarification only if a conflict blocks a coherent safe output.

### 3. Build a continuity ledger
For every recurring character and location, record verified name, role, age, build, physical description, costume, and source; approved visual choices; unspecified details and provisional choices. Check chronology, day/night, blocking, creature design, names, and props. Never infer hair or costume colour from a name. Reuse one reference sheet across all scenes.

### 4. Establish spoiler boundaries
First permitted reveal per creature/identity/object/secret; final permitted action; production tone limits. No invented later events to fill silence.

### 5. Divide into fifteen visual sections
Use actual SRT cue timestamps. Cover the whole edit (recap/outro when present). Label coverage ranges as **proposed**; never change SRT cue times. For long subtitle-free intervals, **use SRT timings only** — do not hunt for missing narration audio or an existing edit (Studio adds TTS later); keep the gaps; do not auto-remove them.

Each image = one coherent moment. Prefer distinct establishing / medium / reaction / protective / cliffhanger compositions. Preserve spatial continuity; never reveal a later event in an earlier image.

### 6. Write fifteen image prompts
Each scene includes: scene number and title; proposed coverage `HH:MM:SS.mmm`–`HH:MM:SS.mmm`; supporting subtitle cue numbers and story purpose; copy-ready prompt; separate editing-motion instruction; source attribution **outside** the copy-ready prompt.

Open each prompt with: `Create one cinematic 16-bit dark-fantasy pixel-art image, 16:9.`

Shared style: deliberate visible pixel clusters; coherent limited palette; retro RPG cutscene composition; follow actual daylight chronology. No embedded text, speech bubbles, watermark, collage, or contact sheet. No character-animation instructions inside a still prompt. Keep speculative costume choices explicit. Same creature anatomy/scale/colour across frames.

### 7. Specify restrained image motion and **require the video export**
Proposed editor settings:
- One clear motion direction per shot
- Typical push-in 100% → 105–108%; an important reveal may reach 110% if framing permits
- **Dialogue framing:** when a character speaks, push in / crop to medium-close on that speaker’s face; use wider frames for action and silent beats. Typical talker zoom 108–115%.
- Gentle pull-backs and horizontal pans OK
- Keep faces, key props, and subtitle-safe space inside the crop
- Long sections: reuse the image in two or three purposeful crops
- Cuts for dramatic reveals; short dissolves only for calm/time transitions
- No unnecessary shake, morphing, face smoothing, lip animation, or invented character motion
- Preserve pixel-art character

**Manus must then assemble those scenes into one continuous episode video** matching SRT duration, export MP4 **1280×720, 25 fps, H.264**, 16:9, **without burned-in subtitles**, and upload to the Drive episode folder named in SOURCE FILES. Do **not** upscale Manus video — keep native Manus size; no 2560×1440 or other upscale. Optional: also keep the fifteen stills as working files. **Success = GENERATE then upload** the video to Drive, not a stills folder alone.

Subtitles: Studio adds separate caption tracks later. Do not burn zh-Hant/English into the picture unless the user explicitly asks for a review burn.

### 8. Quality check
Before delivery verify:
- Exactly fifteen prompts and fifteen timeline entries
- Master/paste blocks explicitly require **one finished episode video** uploaded to Drive
- Correct episode and actual SRT consulted
- No unsupported appearance labelled canonical
- No wrong-era props or inconsistent roles/costumes
- Chronology and formation match subtitles
- Reveal timing and final beat respect spoiler limits
- No fabricated citations, assets, tool features, or claims of completed generation

## Deliverable structure

1. Source-read status and material conflicts
2. Verified continuity table with unresolved details
3. Copy-ready Manus master instruction (**video-first OUTPUT**)
4. Fifteen numbered scene prompts (coverage, cue refs, motion, source notes)
5. Timeline table (Studio pack only — optional note for Manus; **never** a Manus success criterion): scene, start, end, cue range, crop focus, motion, transition
6. Copy-ready editing + **GENERATE video then Drive upload** instructions and review flags
7. Split paste files: `paste-1-master.txt`, `paste-02-scene1.txt` … `paste-16-scene15.txt`, `paste-17-motion.txt` (motion block must end with GENERATE+upload MP4 to Drive)

Keep citations outside prompts. Do not reproduce entire manuscripts or subtitles unnecessarily.

## Manus master instruction template

```text
ROLE (READ FIRST — DO NOT SKIP)
You are the episode VIDEO PRODUCER. GENERATE the video.
Do NOT write a production pack, delivery specification, markdown brief,
scene-prompt list, timing table, or continuity report as your deliverable.
Do NOT ask the user for an existing MP4 — there is none; you must create it.
There is no narration audio or prior edit to find — use the bilingual SRT only.
Success = GENERATE episode-{{EP}}-no-subs.mp4 (1280×720, 25 fps, H.264,
no burned-in subs) and upload it to the Drive episode folder named below.
Text/markdown alone = FAILURE. Asking for an MP4 = FAILURE.

TASK
GENERATE ONE finished Episode {{EP}} video for
“{{TITLE_EN}} / {{TITLE_ZH}},” 16:9, cinematic 16-bit dark-fantasy pixel art.
Use exactly 15 scene stills as source frames, apply restrained zoom/pan
editing timed to the bilingual SRT, then export and upload the MP4.
Fifteen stills alone are NOT the deliverable — the edited episode video is.

SOURCE FILES
Read:
1. [series]/episodes/ep{{EP}}/
   the-king-who-woke-up-dead-ep{{EP}}.bilingual.srt
2. [series]/plot-briefs/Ep{{EP}}-plot.md
3. Relevant Part handoff and approved character / production refs.

SOURCE PRIORITY
The Episode {{EP}} SRT controls spoken sequence, subtitle timing, and ending.
Use brief and story docs only where consistent with the SRT.
Use approved production references for established appearances.
Keep looks consistent; do not write a conflict or verification report.

CHARACTER CONTINUITY
Keep character looks consistent while generating (ages, build, hair, clothing,
insignia). Reuse approved reference images across all scenes.
If references are absent, establish one provisional character sheet and use it consistently.
Do NOT write a character-verification or continuity report as your deliverable.

VISUAL STYLE
Cinematic 16-bit dark-fantasy pixel art, 16:9 landscape.
Visible deliberate pixel clusters; coherent limited palette;
retro RPG cutscene composition. Follow SRT dawn/daylight chronology.
Keep faces, age, proportions, clothing and location consistent.
Leave the lower 15–18 percent relatively uncluttered for later captions.
No text, labels, speech bubbles or watermarks inside generated images.

OUTPUT (REQUIRED)
1. GENERATE 15 individual scene images (working assets), named in scene order.
2. Edit them into ONE continuous episode MP4 (16:9) using the timeline and
   restrained Ken Burns motion below. Match SRT timing; do not invent plot.
3. Video format (REQUIRED): finished MP4 is 1280×720, 25 fps, H.264.
   Do NOT upscale Manus video — keep native Manus size; no 2560×1440 or other upscale.
4. Do NOT burn subtitles into the video picture.
5. Upload the finished MP4 to the Episode {{EP}} Drive folder above
   (preferred name: episode-{{EP}}-no-subs.mp4).
   Upload as an **unconverted MP4** at full export quality — do NOT recompress
   to fit under 50 MB (that cap is for Google-native conversion only).
6. Also upload the fifteen stills if useful — but success = GENERATE then upload
   the video file on Drive. Fifteen stills alone are NOT the deliverable.

EDITING
Use bilingual SRT cue times only; Studio adds TTS later.
There is no narration audio or prior edit to find — do not hunt for them.
The scene ranges below are proposed image coverage ranges,
not replacements for subtitle cue timings.
Do not automatically remove subtitle-free intervals; time the picture to the SRT.

Use subtle digital zooms/pans on stills only; no lip-sync or character morphing.
DIALOGUE FRAMING: when a character speaks, push in / crop to medium-close on
that speaker’s face; use wider frames for action and silent beats.
Typical talker zoom 108–115%.
Do not invent dialogue, narration, new plot events or spoiler reveals.
Picture-led video is fine; omit final TTS/music mix (Studio finishes audio).

SPOILER AND CONTENT LIMITS
No romantic or suggestive framing.
No future names, handlers, or later explanations.
End exactly on the SRT’s final beat.
{{EPISODE_SPECIFIC_LIMITS}}
```

## Paste into Manus (when asked / nightly kickoff)

1. Open manus.im on the signed-in the series studio desktop session.
2. **First Manus message / task title** must say **GENERATE** or **PRODUCE** the finished episode video — never “Upload … MP4” alone (that caused Manus to wait for an existing file).
3. Paste master block (**ROLE first**, then TASK / ANTI-MISREAD), then scenes 1–15, then visual-motion / **GENERATE+upload** block.
4. Point Manus at the Drive episode folder named in SOURCE FILES.
5. Confirm Manus is tasked to **GENERATE** the **MP4 video**, not stills-only and not a pack rewrite.
6. Record episode number, Drive path, local pack path, and Manus task URL.
7. After paste, confirm Manus acknowledges it will **GENERATE/export the episode MP4** (not rewrite a pack/spec, not ask for an existing MP4, not hunt for narration audio). If Manus starts writing a production/delivery pack, specification, markdown brief, scene-prompt document, timing table, or continuity report — or asks for an MP4 — **stop immediately** and paste the CORRECTION file (`paste-0-correction.txt` when present) into the same task.

Do not start Manus until the nightly kickoff or an explicit operator ask for that episode.

## Reference pack

Ep. 16 filled example (update OUTPUT language when revising): `/workspace/shorts-studio/manus-ep16/Ep16-Manus-master-prompt.md`
Ep. 17+ packs must use the video-first master template above.

## Invocation examples

- Use this skill for Episode 17: read bilingual SRT and refs; prepare fifteen prompts, motion timeline, and video-first Manus paste pack.
- Use this skill for Episode 18 with approved Episode 17 character references; require Drive MP4 upload in the master block.
- Use this skill to audit an existing pack and rewrite stills-only OUTPUT into required video export language.
