CommunityWriting & Editinggithub.com

fiction-planner

Web-novel ideation, positioning, and volume-level planning: turn vague ideas into marketable hooks, draft publish/blurb.md, design golden first three chapters, whole-book and volume outlines, beat/emotion waves, S-A-B-C hook and daily groupings, region cycles, and foreshadow schedules.

What is fiction-planner?

The `fiction-planner` skill is designed for web-novel authors and AI agents to handle creative planning at the volume level and above. It transforms fuzzy initial ideas into concrete book positioning, including marketable selling points, the protagonist's unique advantage (golden finger) with its costs and limitations, and target reader profiles. The skill guides the drafting of publishable materials like book titles, blurbs, and tags in `publish/blurb.md`, and plans the critical first three chapters (Golden Three Chapters) to maximize reader retention. Beyond the opening, it orchestrates the entire book outline, volume divisions, dual-line (overt/covert) rhythms, and volume-level hook chains. It also schedules beat/emotion waves using S-A-B-C hook grades, daily update groupings (regular and burst periods), region cycles for travel/multi-location arcs, and foreshadow/subplot timelines, with a systematic scan using `foreshadow-scan.mjs` to identify overdue, due, and dormant items. The skill operates across major platforms like Claude Code, Cursor, and Codex by producing structured markdown files (`bible/volumes/{vol}.md`, `bible/plot-outline.md`, etc.). It deliberately defers chapter-level outlining and drafting to `fiction-chapter`, setup and freezing to `fiction-init`, and review/submission to other dedicated skills, ensuring a clear division of labor.

Works with✓Claude Code✓Codex CLI~Cursor✓OpenCode
npx skills add https://github.com/interjc/create-fiction-skills/tree/HEAD/skills/fiction-planner

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Ideation and Volume Outline Planning

Responsible for creative and volume-level planning above the single-chapter level in a web-novel project: converge vague ideas into book positioning, a first draft of external copy, the Golden Three Chapters (first three chapters, which determine reader retention), a whole-book outline and volume-level plan (chapter planning table, rhythm waveform, hook grades, daily update groupings with region cycle notes), and then hand the volume plan downstream for chapter writing or review.

When to Use / Not Use

When to use this skill:

  • You have only fuzzy ideas and want to converge on genre positioning, core selling points, the protagonist's advantage (golden finger) with its costs and reader expectations.
  • You need to draft or rewrite publish/blurb.md (title, blurb, tags, tagline).
  • You need to design or restructure the opening Golden Three Chapters, validating "why the reader should keep reading."
  • You need to draft or adjust the whole-book outline, volume intervals, overt/covert line rhythm, major reversals, and volume-level big hook chains.
  • You need to start a new volume, reorder volumes, edit the ## Chapter Plan table in bible/volumes/{vol}.md, or allocate pop/emotion waves and S/A/B/C hooks according to daily/burst update schedules.
  • You need to design a stable "region cycle" structure for travel, multi-location, instance, or episodic detective-style volumes.

When to hand over to sibling skills (only hand over, never silently do their work):

  • To set up the book skeleton, import existing drafts, or update the public freeze list (frozen.ranges and lint.mjs --freeze): hand over to fiction-init. If not installed, deliver the produced discussion notes/template list, to-do steps (create directories or update frozen.ranges and run lint.mjs --freeze), and unchecked items.
  • To write single-chapter outline.md, draft the main text, or do post-chapter updates based on the volume plan: hand over to fiction-chapter. If not installed, deliver that volume's bible/volumes/{vol}.md (including free-form area with daily grouping and region three notes), a list of chapter outlines to write, and undone text/writeback checks.
  • To resolve canon conflicts, register new foreshadows/subplots, or do routine maintenance: hand over to fiction-continuity. If not installed, deliver the list of foreshadows/subplots to register and conflict points, explicitly marking incomplete registration and consistency review for manual backfill by the author.
  • For automated checks, desensitization review, and editorial review of publish/blurb.md and the main text: hand over to fiction-review. If not installed, deliver publish/blurb.md, a manual review checklist (corresponding to lint.desensitize.*, lint.banned_terms, lint.internal_terms), and note "Automated checks not run."
  • To submit title, blurb, and chapters to the publishing platform: hand over to fiction-publish. If not installed, deliver publish/blurb.md and a reminder to verify book.title, for the author to publish manually.
  • For scene writing, dialogue, atmosphere, or genre details: consult fiction-craft (especially references/genres/<id>.md). If not installed, confirm genre conventions and reader expectations with the author.
  • To adapt the web novel into a vertical short drama: hand over to fiction-short-drama. If not installed, deliver the finalized bible/plot-outline.md, bible/volumes/{vol}.md, and a list of drama-side files to create (series.md, adaptation-map.md), noting that adaptation checks have not been run.

Before You Start

Before creating or modifying any machine-readable file, open the corresponding format reference file (references/formats/*.md) and follow its format strictly. Do not rely on memory.

Before planning, read the three categories of project files in order:

  1. Project AGENTS.md (focus on ## Book Scope): Confirm the protagonist's scope, perspective discipline, book-specific rules, and genre taboos. Project rules take precedence over this skill's defaults (SB §3).
  2. .fiction/config.json (fields and defaults in SB §8): Read book.title, book.genres, rhythm.beat_every (default [3,5]), rhythm.external_event_max_gap (default 2), daily.* (default regular 2 chapters/day, last chapter minimum A; burst 3-5 chapters/day, last chapter minimum S), hook.discouraged (default ["C"]), frozen.ranges, foreshadow.*, subplot.*, lint.desensitize.*, lint.banned_terms, lint.internal_terms, and lint.extra_files.
  3. bible/sources.md (SB §5): Confirm the single main writing entry to avoid modifying derivative files by mistake.

Read the minimum required set by task (SB §4.1; do not full-scan bible/ out of fear of missing something):

  • For discussing whole-book direction or reordering volumes: bible/canon.md → bible/timeline.md → chapters/{vol}/vol-info.md → bible/volumes/{vol}.md → bible/plot-outline.md → bible/storylines.md → bible/subplots.md; read bible/foreshadows.md if needed.
  • If fiction-craft is installed and book.genres is non-empty, first consult the corresponding genre package references/genres/<id>.md to align with pop preferences and minefields.
  • If the replanning touches chapters in frozen.ranges that are published publicly frozen (SB §7.1), the frozen chapter text is read-only; only adjust unfrozen chapters. For canon conflicts involving frozen chapters, hand over to fiction-continuity; if you need to extend the public freeze range, hand over to fiction-init.

Missing file handling: If the author is starting from scratch with no project files yet, suggest the author can run fiction-init to initialize the skeleton at any time; for now, plan using SB §8 defaults and note at the beginning of the output "Currently using default parameters."

Process

The author may go through the full process from Step 1, or jump directly to the current phase (e.g., starting a new volume or replanning, start directly from Step 5). Whenever core positioning, dual-line thresholds, volume reordering, or overwriting existing plans are involved, first present the proposal for the author to approve; only after confirmation should authoritative files be written.

Step 1: Creative Positioning and Selling Point Convergence

  1. Collect initial ideas (genre, protagonist's predicament, scenes the author wants to write, estimated length, and target platform). If fiction-craft is installed and a genre is selected, first consult the corresponding genre package (references/genres/<id>.md) for selling point preferences and minefields.
  2. Following references/ideation-and-blurb.md, produce 2-3 premise variants. For each variant, clearly state: core selling point, protagonist's advantage/golden finger (the protagonist's unique problem-solving ability or information asymmetry, if required by the genre) along with its cost, limitations, and growth potential, target reader profile, and a one-line pitch.
  3. Competitor comparison: Ask the author for 2-3 reference works; only deconstruct their structure, tone, and selling point differences. Never fabricate sales, subscriptions, clicks, or chart data.
  4. Perform the "Why Keep Reading" five-question validation, and draft a positioning overview (one-line positioning, atmosphere reference, dual-line structure, core character draft).
  5. Pause and ask the author to approve: After the premise variant and boundaries are selected, continue; leave undecided drafts in bible/drafts/. According to fiction-continuity's conflict priority (SB §3), only write into bible/canon.md the setting judgments that the author unequivocally confirmed in this process and that have no conflicts. Unconfirmed or conflicting items go to fiction-continuity.

Step 2: Drafting External Packaging Copy (publish/blurb.md)

  1. Based on the approved positioning, referencing references/ideation-and-blurb.md and the template assets/blurb-template.md, draft: title candidates (at least 3 sets with different styles), a four-paragraph blurb, core tags, and a one-line tagline.
  2. According to SB §1.6 and SB §8, verify copy constraints:
    • Desensitization: Do not include exact Gregorian years or words that can be mapped to reality (lint.desensitize.*);
    • Banned terms: Avoid lint.banned_terms;
    • Internal terms: Do not leak lint.internal_terms (e.g., "foreshadow," "hook," "pop beat," "subplot," "outline").
  3. Pause and ask the author to choose, then write the selected version to publish/blurb.md. If the title is selected or changed, also remind to verify book.title in .fiction/config.json (for use by fiction-init / fiction-publish).
  4. Handoff closure: This skill is only responsible for drafting; hand over publish/blurb.md to fiction-review for automated checks and re-review per main-text standards (lint.extra_files includes this file by default), and to fiction-publish when ready for platform submission.

Step 3: Golden Three Chapters Design

  1. Following references/ideation-and-blurb.md, plan the hard tasks for chapters 1–3: Chapter 1 establishes situation + desire + first anomaly/conflict; Chapter 2 active probing + first small validation/small pop beat with its boundaries; Chapter 3 raises stakes + pushes the door open wider + strong cliffhanger hook.
  2. Check against opening anti-patterns (no infodump-style setup, no generic weather opening, no zero-incremental filler in the first 3 chapters, keep character count manageable).
  3. Pause and ask the author to confirm the direction of the first three chapters; after confirmation, in Step 6, these will be written into the ## Chapter Plan first three rows of Volume 1.

Step 4: Whole-Book Outline and Overt/Covert Dual-Line Planning

  1. Following references/outline-and-dual-line.md and the template assets/plot-outline-template.md, design the whole-book skeleton: phase divisions, volume intervals, volume-level big hook chains (plant the next volume's seed around 50%), overt/covert dual-line four-stage intervention thresholds (thresholds approved by the author based on total length, maintained only in bible/plot-outline.md; if the project AGENTS.md needs to mention, only reference, not copy), key reversal sequences (separating what the reader knows from the author's truth), and endgame direction.
  2. Pause and ask the author to approve the phase divisions, dual-line thresholds, and endgame direction.
  3. Write-back timing (strictly follow SB §4.2 order) :
    • If this session only does whole-book macro-planning without touching existing volumes or detailed volume planning, after author confirmation, write directly to bible/plot-outline.md;
    • If this session simultaneously creates or replans specific volumes, first keep the confirmed draft in the conversation or bible/drafts/, and after Step 6's volume plan is confirmed, write back in order: bible/volumes/{vol}.md → bible/plot-outline.md → chapters/{vol}/vol-info.md.

Step 5: Foreshadow and Subplot Scheduling Scan (Mandatory for existing projects starting a new volume or replanning)

  1. First scan without filtering diagnosis categories (do not add --only, to avoid masking invalid and writeback), using the latest finalized chapter number as the argument (parameters and default --fail-on behavior details in foreshadow-scan.mjs --help):
    node <this skill directory>/scripts/foreshadow-scan.mjs --at <latest finalized chapter number>
    
    • Exit code 2 (couldn't find book root, configuration, or usage error): First troubleshoot the command and environment; do not treat as no issues and continue;
    • Exit code 1 (default exists overdue or invalid) or writeback gaps appear: First hand over invalid / writeback to fiction-continuity (or the author manually) to fix the bible, then plan the new volume.
  2. Cover the entire volume interval to prevent omissions: A single --at only reflects a snapshot up to that chapter. After clearing existing debts, for the planned volume interval [vol_start, vol_end], manually check the Plant Chapter and Planned Recovery Chapter columns in bible/foreshadows.md (and can run --at <vol_end> --only plant_due,due,overdue,dormant,subplot_alerts to preview all items due within the volume), aggregate all to-be-planted, due, overdue, dormant foreshadows and stalled subplots within this volume interval into the scheduling pool.
  3. Pure new book handling: If bible/foreshadows.md or bible/subplots.md does not exist yet, skip the script, but separately list the new foreshadows and subplots planned for this volume for registration before handoff.
  4. Scheduling and approval: overdue / due items are prioritized for recovery in the early-to-middle part of the volume; for those that cannot be recovered on time, list options to reschedule or abandon and ask the author to approve; dormant items schedule for light touch or recovery; subplot_alerts (stalled / span / remind_gap) arrange advancement nodes according to subplot.* configuration.

Step 6: Volume-Level Planning, Rhythm Waveform, and Daily Update Scheduling

  1. Following references/rhythm-and-cadence.md and the template assets/volume-plan-template.md, draft the volume plan:
    • Segmentation and emotion waveform: tense → relax → tenser; no two consecutive chapters both climax or both lull; lull chapters carry subplots, ripples, character depth, or seeds for the next volume.
    • Pop beat cadence: According to rhythm.beat_every in .fiction/config.json (default every 3-5 chapters), land clear pop beats and rotate types; use micro/medium/macro "build-up then release" to amplify contrast.
    • External events and mini-arcs: Consecutive chapters without external events should not exceed rhythm.external_event_max_gap (default 2 chapters); arrange an external event in the following chapter. Complete a mini-arc every ~ 3 chapters.
    • Subplots and ripples: Each chapter should touch at least 1 active subplot and arrange at least 1 interacting character; schedule the six-step nodes according to subplot.remind_gap and subplot.max_span, and reserve end-of-chapter connection points; after major events, disperse direct/indirect/distant three-layer ripples over several subsequent chapters; recover no more than 1-2 foreshadows per chapter.
    • Hook grading and daily/burst update grouping: In the ## Chapter Planning table's Hook column, indicate the planned grade (S/A/B/C, definitions in SB §7.2). Group updates for regular publishing according to daily.chapters_per_day (default 2 chapters), with the last chapter each day not below daily.last_hook_min (default minimum A); for burst periods, group according to daily.burst.chapters_per_day (default 3-5 chapters) in a "pop → breather → bigger pop" wave, with the last chapter not below daily.burst.last_hook_min (default minimum S). In writing, grade C is only for breather chapters after big climaxes; hitting hook.discouraged (default ["C"]) in automated checks triggers a prompt. Write the chapter number groupings by publish day into the volume outline's free-form area ## Daily / Burst Update Grouping Notes, for fiction-chapter to fill into each chapter's outline.md ## Daily Update Position (SB §7.3).
  2. If this volume belongs to travel, multi-location, instance, or unit structure: Load references/region-cycle.md, establish the local main story line and at least 1 attached subplot for the current station, decompose into region cycle eight steps, advancing 1-2 steps per chapter. Write the three items (current region cycle step, this chapter's new region understanding, this chapter's settled gains) by chapter number into the volume outline's free-form area ## Region Cycle Per-Chapter Notes, without modifying the contract's eight-column table header; subsequently, fiction-chapter will write these into each chapter's outline.md ## This Chapter's Responsibilities.
  3. ID verification before handoff: Verify that all F-IDs and subplot IDs referenced in the ## Chapter Plan table are already registered in bible/foreshadows.md (SB §6.2) and bible/subplots.md (SB §6.3); list new unregistered items as a to-be-registered list.
  4. First pause and ask the author to confirm the complete plan (chapter planning table, rhythm waveform, daily groupings, region three items, list of IDs to register), then strictly follow SB §4.2 order to write back:
    1. First write or modify bible/volumes/{vol}.md (- Chapter Range + free-form area + SB §7.5 eight-column table: Chapter | Core Event | Pop Beat | Hook | Subplot | Foreshadow | Character | Weight); the {start_chapter}-{end_chapter} placeholders in the template must be replaced with actual chapter numbers, otherwise scripts will not parse them;
    2. Then synchronize bible/plot-outline.md (align the volume's range, core storyline, and big hooks);
    3. Finally update chapters/{vol}/vol-info.md (SB §7.4 summary fields, do not replicate the planning table).

Step 7: Handoff to Downstream

Hand over to the corresponding skill according to responsibilities; if the target skill is not installed, deliver the produced files, a clear to-do list, and unchecked items, without silently doing its work:

  • Write single-chapter outline.md and main text based on the volume plan, and complete post-chapter writeback → fiction-chapter;
  • List of new foreshadows/subplots to register, reschedule/abandon writeback, or setting conflicts → fiction-continuity;
  • Automated check and polish review of publish/blurb.md → fiction-review;
  • Submit title, blurb, and chapters externally (synchronously verify book.title) → fiction-publish;
  • Set up the book skeleton or update the public freeze list → fiction-init;
  • Pipeline continues toward vertical short drama adaptation → fiction-short-drama.

Checklist

Before delivering any planning artifact, check each item and report truthfully:

  • For existing projects, a full foreshadow-scan.mjs has been run with the current chapter number (no --only masking diagnosis categories, exit code not 2), and all invalid, writeback, overdue, due, plant_due, dormant, and subplot_alerts have been fully listed [Script]
  • The entire volume interval [vol_start, vol_end] has been checked against the planned recovery column in bible/foreshadows.md, and due/dormant items and stalled subplots have been scheduled into the volume outline; all F-IDs and subplot IDs referenced in the planning table are registered, or a separate to-be-registered list has been prepared for downstream [Model]
  • bible/volumes/{vol}.md (SB §7.5) and chapters/{vol}/vol-info.md (SB §7.4) are format-compliant, and after author confirmation, have been written back in the order volumes/{vol}.md → plot-outline.md → vol-info.md [Model]
  • If publish/blurb.md was drafted, it has been initially checked against lint.desensitize.*, lint.banned_terms, lint.internal_terms (SB §8), and it has been noted that it must go to fiction-review for automated checks; if the title changed, a reminder to verify book.title has been given [Model]
  • Pop beat density satisfies rhythm.beat_every, consecutive chapters without external events do not exceed rhythm.external_event_max_gap, no two consecutive chapters are both climax or both lull; daily/burst update groupings have been written into the volume outline's free-form area, each day's last chapter hook is not below the configured minimum (regular daily.last_hook_min / burst daily.burst.last_hook_min), and grade C and hook.discouraged are handled appropriately [Model]
  • Each volume has an active big hook and a seed for the next volume planted around 50%; A/B grade subplots are attached to the main plot and scheduled according to subplot.remind_gap / subplot.max_span; if this is a region-cycle volume, each station has a local main plot and attached subplot, eight steps are complete, three items are written by chapter into the volume outline's free-form area, and no warning-level anti-patterns exist [Model]
  • Competitor comparison does not fabricate sales/chart data; core selling points, golden finger cost, dual-line thresholds, title/blurb, overdue foreshadow rescheduling/abandonment, and the volume plan have all been approved by the author [Author]

Outputs

Depending on the current step, create or update the following files:

  • publish/blurb.md (draft title, blurb, tags, tagline)
  • bible/plot-outline.md (whole-book phases, dual-line thresholds, per-volume big hook chains, reversal sequences, endgame direction)
  • bible/volumes/{vol}.md (detailed volume plan, free-form area daily groupings and region three notes, ## Chapter Plan eight-column table)
  • chapters/{vol}/vol-info.md (volume summary)
  • bible/drafts/*.md (creative variants or outline drafts not yet approved, read-only reference)

Report format for the author:

  1. List of newly created/updated files (note whether they were synchronized in the order volumes → plot-outline → vol-info after confirmation).
  2. foreshadow-scan.mjs scan results and full-volume foreshadow/subplot scheduling summary (including exit code explanation, list of IDs to register; for pure new books, note script skipped).
  3. Rhythm and daily update health check summary (pop beat spacing, longest consecutive chapter string without external events, emotion peaks, daily last chapter hook compliance, big hook and next-volume seed positions).
  4. Decision items pending author approval, downstream handoff targets (if downstream skill not installed, list delivered files, to-do list, and unchecked items).

Reference Documents

When encountering this scenarioRead this file
View directory structure, conflict resolution, minimum required reading set, writeback order by event, and sources.md (SB §1–§5)references/formats/project.md
View foreshadow table, subplot six-step table, character and timeline anchors, and other bible/ machine-readable formats (SB §6)references/formats/bible.md
View volume detailed plan eight-column table, vol-info.md, outline.md, and hook grading specification (SB §6.1, §7)references/formats/chapter.md
View all .fiction/config.json fields and defaults (SB §8)references/formats/config.md
Converge selling points from fuzzy ideas, design golden finger boundaries, draft publish/blurb.md, or polish the Golden Three Chaptersreferences/ideation-and-blurb.md
Arrange whole-book outline, overt/covert dual-line intervention rhythm, three-layer information, big hook chains, A/B/C subplot scheduling, and three-layer ripplesreferences/outline-and-dual-line.md
Arrange pop beat cadence, build-up then release, conflict escalation ladder, emotion waveform, hook grading, and daily/burst update groupingsreferences/rhythm-and-cadence.md
Plan travel, multi-location, instance, and episodic detective-style volumes with the eight-step "region cycle" and warning listreferences/region-cycle.md
Copy the empty external copy template to create publish/blurb.mdassets/blurb-template.md
Copy the empty whole-book outline template to create bible/plot-outline.mdassets/plot-outline-template.md
Copy the empty volume-level planning template to create bible/volumes/{vol}.mdassets/volume-plan-template.md

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

fiction-chapter

网文单章写作六步闭环:查前文和设定、摘资料、定章纲、写正文、机检审改、回写追踪表。作者说“写新章”“接着写”“出下一章”“重写这一章”或要求重排单章结构时就用。重排卷纲或设计连载节拍用 fiction-planner;审校及已有章节获授权的局部回修、润色和去 AI 味用 fiction-review。 Write, continue, rewrite, or restructure one web novel chapter, from continuity checks and outlining through drafting, validation, and story bible updates. Use when asked to write a new chapter, pick up where the draft left off, write the next installment, or rewrite a chapter. Use fiction-planner for volume planning and serial cadence, and fiction-review for editorial review or authorized local fixes, polishing, and removing AI-like prose in an existing chapter.

fiction-craft

小说与网文写作技法库及风格指南构建工具:提供场景构建、场景-反应节奏、欲扬先抑、对话潜台词、信息分层、双线结构、氛围营造、混搭题材写法及准备/行动/分赃/交易/规则册子等章型剧本,并指导新建或从样章反向提炼项目 bible/style-guide.md。当用户询问具体怎么写某类场景、解决对话像话剧/节奏发闷/信息说太满/氛围不够等问题、设计题材混搭口径、或制定本书文风指南时使用,即使没提“技法”二字。只提供技法与风格校准:完整写新章用 fiction-chapter,技法问答或示范用本 skill,具体已有稿件的回修用 fiction-review,卷纲与爽点规划用 fiction-planner,设定与伏笔维护用 fiction-continuity。Web-novel craft library and style-guide builder: covers scene craft, scene-sequel pacing, dialogue, layered information, dual-line structure, atmosphere, genre-blend voice, chapter playbooks, and building bible/style-guide.md. Use for technique questions, demos, or codifying a book's voice. Use fiction-chapter for drafting, fiction-review for fixes to an existing draft, plotting to fiction-planner, and bible tracking to fiction-continuity.

fiction-short-drama

竖屏短剧改编与原创剧本闭环:立项、分集大纲与章集映射、分批写分集剧本、前 3 秒钩子与付费卡点设计、机检与映射回写。涉及改编短剧、把小说改成竖屏短剧、写短剧剧本 / 分集剧本、分集大纲、章集映射、付费卡点、前 3 秒钩子、断章、原创短剧、续写下一集短剧、检查短剧格式与时长时使用。建项目用 fiction-init;小说策划用 fiction-planner;写小说用 fiction-chapter;改共享档案用 fiction-continuity;润色用 fiction-review;转分镜用 fiction-storyboard;路由用 fiction-workflow。 Vertical short-drama adaptation and original scripting workflow: series setup, episode outlines, chapter-to-episode mapping, batched episode scripts, first-3-second hooks, cliffhangers, paywall breaks, and script checks. Use when adapting a novel into a vertical short drama, writing or continuing short-drama episodes, planning episode outlines or maps, placing paywalls, or checking script format and duration. Use fiction-init for setup, fiction-planner for novel planning, fiction-chapter for novel chapters, fiction-continuity for shared bible edits, fiction-review for polish, fiction-storyboard for storyboards, and fiction-workflow for routing.

fiction-storyboard

竖屏短剧分镜工作流:基于已定稿且过检的分集剧本,先做防剧透简报与视觉资产最小建档,再按“段(一次视频生成)→ 镜(段内剪切)”拆解分镜,逐镜核对台词认领、动作依据、竖屏构图、单瞬起止与跨集连戏,最后跑脚本验收并交接下游提示词。作者说“画分镜”“拆镜头”“做场景脚本”“切镜”“把第几集转成分镜”“剧本改了同步分镜”时就用,即使没提“分镜”二字。写或改分集剧本(含改台词)请用 fiction-short-drama;补全资产锁定词、写图片/视频提示词或做付费生成确认请用 fiction-visual-prompts。 Vertical short-drama storyboard workflow: turn finalized, validated episode scripts into segment-and-shot storyboards with spoiler briefs, minimal visual asset entries, continuity tracking, verbatim dialogue/action claiming, 9:16 vertical framing, single-instant start-to-end shot design, and automated storyboard validation. Use when asked to storyboard an episode, break a script into shots, cut segments, or sync storyboards after script edits. Use fiction-short-drama for writing or editing episode scripts and dialogue, and fiction-visual-prompts for full asset locks, reference-image slots, and image/video prompts.

Related Skills