Vertical Short-Drama Storyboard
Decompose a finalized, validated episode script into a two-level storyboard (segments → shots) that is ready to shoot and audit, while maintaining minimal visual asset entries and cross-episode continuity tracking.
When to Use / Not Use
- Use this skill: Decompose
drama/{series}/episodes/ep{NNN}.mdinto storyboard shots; create minimal asset entries or variants for characters, locations, and props appearing in this episode; maintain cross-episode continuity status; synchronize existing storyboards after script revisions are finalized. - Writing or editing episode scripts (including dialogue changes, completing mapping lines, finalization): Delegate to
fiction-short-drama. This skill will never modify script text or dialogue; it will return to upstream if the script is not finalized, mapping lines are missing, validation checks have blocking items, or actions are unshootable. Iffiction-short-dramais not installed, list the unfinalized status, missing mapping lines, or specific errors with line numbers and ask the author to fix them manually before proceeding. - Completing full asset appearance and lock terms, writing reference image slots, writing image/video prompts, confirming before paid generation: Delegate to
fiction-visual-prompts. This skill will never write锁定词(lock terms), write prompts or model parameters in the storyboard, or call any generation interface. - Determining the project stage: Delegate to
fiction-workflow; if not installed, ask the author directly for the target series and episode number.
If the downstream fiction-visual-prompts is missing, deliver the checked storyboard, asset library, and continuity table, clearly noting prompt-check not run (this skill does not run it) and provide a downstream manual checklist: complete full asset appearances and 锁定词, write reference image slots and episode image/video prompts under drama/{series}/prompts/, and confirm by segment and shot number before the author decides whether to generate.
Before Starting
First read AGENTS.md (especially the "Series Scope" section), .fiction/config.json, and bible/sources.md (main writing entry registry, see SB §5) from the book root. Then read in the minimal required order for the task (SB §4.1):
- Storyboarding: The script for the episode
drama/{series}/episodes/ep{NNN}.md→storyboard-check.mjs --briefoutput →drama/{series}/visual/assets.md→drama/{series}/visual/continuity.md; optionally read the last segment of the previous episode's storyboard and thebible/characters.mdentries for appearing characters; for original series (series.mdhas来源:原创), also readdrama/{series}/series.md's## 悬念账(mystery ledger). - Creating/modifying visual assets:
drama/{series}/series.md→bible/characters.md(main characters and those appearing in this episode) →drama/{series}/visual/assets.md→ locations and props that appear in the written script; optionally readbible/inventory.md,bible/foreshadows.md,bible/timeline.md,bible/world-rules.mdif foreshadowing, objects, or period specificities are involved.
Before writing or modifying any machine-readable file, first open the corresponding format excerpt from the reference document table at the end of this document, and write exactly according to the original, not from memory.
The short-drama visual chain is resolved by upstream priority over downstream (SB §3): characters.md stable traits > visual/assets.md > storyboard > prompts; script > storyboard > prompts. If an upstream error is found, fix it upstream first, do not create alternative descriptions in the storyboard.
If the project skeleton is missing, prompt to use fiction-init first; if fiction-init is not installed, ask the author to manually supplement AGENTS.md (including ## 本书口径), .fiction/config.json, bible/sources.md, bible/characters.md, and the required files under drama/{series}/ according to SB §2, SB §5, and SB §8. If only .fiction/config.json is missing, scripts will run with contractual default values (SB §8), and the author should be informed.
Path conventions: paths starting with bible/, drama/{series}/ are relative to the book root; shorthand visual/..., storyboards/..., episodes/... in the text are relative to drama/{series}/. All scripts run from the book root; enclose paths with spaces in quotes.
Seven-Step Workflow
1. Pre-Work Check: Confirm Finalization and Mapping, Then Run Script Check and Brief
Before starting breakdown (including subsequent script revision synchronization), verify three entry gates one by one:
- Script finalized: Open
drama/{series}/episodes/ep{NNN}.md(SB §9.3) and confirm metadata is- 状态:定稿(set by author). - Mapping lines complete: Open
drama/{series}/adaptation-map.md(SB §9.2) and confirm the target episode has a corresponding line with character and foreshadowing columns filled for this episode (missing lines only reportmap-missingas a suggestion, but will cause the brief to miss the mapped characters and their secrets for this episode). - Script validation all green: Run (see
drama-check.mjs --helpfor usage):
node <path-to-this-skill-dir>/scripts/drama-check.mjs <series> --ep <N>
Must have exit code 0, and zero blocks at both series level and for the target episode (exit code 2 indicates argument, configuration, or reading errors, not a pass); also confirm that fiction-short-drama has reported exit code 0 for the latest lint --series on this drama. If any condition is not met, stop and return to fiction-short-drama; if the lint report is missing, ask it to run and report (if not installed, list the gaps and error line numbers and ask the author to fix manually). If there are unshootable, dialogue-run or other suggest items, continue if resolvable through breakdown; if truly unshootable, ask the author to modify the script first.
After the entry gates are passed, run the storyboard brief (see storyboard-check.mjs --help for usage):
node <path-to-this-skill-dir>/scripts/storyboard-check.mjs <series> --ep <N> --brief
Read through all five sections section by section: ## 来源 (Source), ## 本集不得画出的真相 (Truths that must not be depicted in this episode, derived from any line in adaptation-map.md or any asset's 揭示伏笔 that haven't been revealed earlier), ## 人物秘密 (Character secrets, from this episode's mapping 人物 column and series.md 主要人物 entries that have 作者真相 filled), ## 尚不可用的资产 (Assets not yet available), ## 连戏现状 (Continuity status). If series.md has 来源:原创, the brief does not scan original clues, so manually read drama/{series}/series.md's ## 悬念账 and incorporate it into the spoiler avoidance checklist.
2. Build Minimal Visual Assets and Record Continuity Net Changes
Update drama/{series}/visual/assets.md according to SB §9.4 and SB §6.1 (for first-time creation, refer to Visual Asset Template):
- Minimal entry principle: Only create
### {asset_key}and one visible- 外观:line for characters, locations, and props that need to be on screen in this episode (for locations, optionally add锚点; for props with a corresponding entry inbible/inventory.md, add- 物品:Ixxx; for confidential entries, add- 揭示伏笔:or- 揭示集:). Do not write锁定词; leave complete appearance polishing and reference image slots forfiction-visual-prompts. For first-time creation, only write画幅if it differs from configvisual.aspect_ratio, and confirm the series basic画风with the author. - Standard names and variants: Use the standard name from
bible/characters.mdunder## 人物; do not create entries for extras without character files; do not repeat the same name across groups; usename@variantfor costume or state changes (a base entry must exist first in the same group). Do not mix the three layers; see Visual Asset Writing Guide for details. - Refresh the brief: If any
揭示伏笔/揭示集field is added or modified in this step, immediately re-runnode <path-to-this-skill-dir>/scripts/storyboard-check.mjs <series> --ep <N> --briefto synchronize newly included foreshadowing truths and restricted assets into this episode's verification checklist.
If this episode has state changes that will continue into subsequent episodes (costume changes, persistent injuries/dirt, prop transfer/destruction/exit, persistent location changes), according to SB §9.5, directly write the net changes for this episode into drama/{series}/visual/continuity.md (for first-time creation, refer to Cross-Episode Continuity Table Template), so that step 6's automated check can verify them in one pass. When encountering inconsistencies between the brief's continuity.md and bible/inventory.md, except for adaptation scopes already approved by the author and recorded in adaptation-map.md, list all other differences and ask the author to decide; never write back to the novel's bible/inventory.md; see Cross-Episode Continuity Guide for details.
3. Divide into Segments First, Then Cut into Shots
Open SB §9.6 and SB §6.1, write drama/{series}/storyboards/ep{NNN}.md following the Storyboard Template, initially with - 状态:初稿.
- Segment first (
## SEG01|Scene 1): One segment = one video generation, never cross scenes. Usually divide into 9–15 second segments based on plot units (short transitions can be shorter than 9 seconds if shot individually); total duration must not exceedstoryboard.segment.max_seconds(default 15 seconds, see SB §8).地点is required;站位,环境声,配乐are optional. - Cut shots within segment (
### SH001|3s): Aim for around 3 seconds per shot, withinstoryboard.shot.seconds(default 2–5 seconds); duration must not be 0.景别(6-item closed set) and画面are required;运镜(8-item closed set, default固定),转场(4-item closed set, default切),人物,道具,依据,声音,备注are optional. - Verbatim claiming of dialogue and actions:
- Dialogue: Copy each line of dialogue from the scene block in script order, exactly as written (including punctuation and applicable
(OS)/(VO)), do not change words, do not delete words. If a single dialogue line cannot fit into one shot when converted to seconds usingdrama.chars_per_minute(default 250 code points/minute, not rounded), split it into valid dialogue rows for adjacent shots; after combination, they must match the original sentence character by character. - Actions and shot lines: Extract original text fragments from
△action lines and【…】shot lines directly into- 依据:(at least 4 code points per segment, separate multiple segments with;), and ensure that画面truly performs the action.
- Dialogue: Copy each line of dialogue from the scene block in script order, exactly as written (including punctuation and applicable
- Shot language and vertical framing: The first shot of the entire episode must have a moving subject; alternate between close and wide shots, short and long durations; use shot-reverse-shot for dialogue and leave reaction shots, insert short close-ups for key actions; cut in the middle of action (match on action); within a segment, at most 1–2 non-fixed camera movements, default
固定; for 9:16 vertical screen, avoid empty wide shots, build depth with foreground/midground/background, use character actions to reveal the environment; write camera position, angle, and focal length into画面. See Segment and Shot Grammar and Vertical Framing and Shot Writing for details. - Maintain stable numbering: Insert new shots using new numbers or letter suffixes (e.g.,
SH003a); do not shift existing numbers, do not reuse deleted numbers.
4. Write 画面 Under the Single-Instant Principle
Organize each shot's 画面 as **