Write a single episode's intention into a performable, shootable, story-state-changing script at .

Maintain only one script Markdown; do not create additional episode cards, beats, block indexes, recording sheets, QA, or acceptance records. Top-level headings use , scene headings use . Write dialogue as ; use production tags , , , , , . Do not mistake action descriptions containing colons for dialogue.

Developing an outline and long-form analysis are optional upstream steps; write directly when current material is sufficient.

By default, only read this SKILL and direct input. When any of the following explicit signals appears, read the corresponding knowledge before writing the body; multiple issues in the same input can be read separately, but do not traverse unrelated references:

Only write an index to the system temporary directory when the user asks about duration. First use Python to query the cross-platform temporary directory, and replace the full path printed by the first command verbatim into the quotes of the next two commands. Each of the following is a complete one-line command, not relying on shell variables or continuation characters; use on Windows when is unavailable. The example values of must be replaced with the actual speakers in this episode. must be added only to the third command ( accepts it; has no such parameter and will report if added), and only when a project configuration actually exists:

python3 -c "from pathlib import Path; import tempfile, uuid; print(Path(tempfile.gettempdir()) / ('short-drama-' + uuid.uuid4().hex + '.jsonl'))"
python3 "{技能目录}/scripts/screenplay_index.py" "剧集/EP001/剧本.md" --output "粘贴第一条命令输出的完整路径" --speaker "本集角色一" --speaker "本集角色二"
python3 "{技能目录}/scripts/duration_estimate.py" "剧集/EP001/剧本.md" --index "粘贴第一条命令输出的完整路径"

Re-run after revision: the output path written once by the second command cannot be written again directly; it will fail with . To keep original block IDs, add ; to renumber from scratch, add ; or go back to the first command and choose another temporary path.

Before estimating, distinguish the counting calibers: includes punctuation; reference speaking rates in video prompts are calculated by pronounceable character count. When converting by speaking rate, exclude punctuation and treat numbers and abbreviations according to actual pronunciation; do not mix the two counts.

Estimation is a reference, not a gate; when no speaking rate or action-segment rate is available, only report countable facts and do not guess seconds. But when the task already gives a target duration, the writer must still use real reading and action pacing to judge whether it fits, and directly compress repeated beats; "cannot precisely estimate seconds" is not a reason to ignore the target.

Completion is achieved when the named scope is written, scenes are causally coherent, dialogue and action are performable, promises are paid off or deliberately delayed, and the ending completes the episode's intended dramatic or emotional function. The final beat may advance, close quietly, form resonance, or re-contextualize existing action; judge whether it works by whether it works, not by substituting "did one more thing happen."

Assets, storyboards, review, and production begin only when the user names them. After the five creative documents are complete, you may turn to for a mechanical cross-document consistency check; content quality remains with the creator's review.

Run only when installing, upgrading, or troubleshooting.