ScreenplayFormat: K-drama script2026-10-15

Scene purpose audit: what breaks without it

When to use it

The script ran long. Test every scene by asking what breaks if it goes.

Fill in the variables

Script (several scenes){{manuscript}}

Assembled prompt

526

Audit the scenes of the script below.
Table: S# | the scene's purpose in one word (information / relationship / danger / tone / setup) | later scene numbers that break without it ('none' if none) | verdict (keep / merge / cut) | if merge, with which scene
Rules:
- Keep at most two scenes whose only purpose is tone; the rest are cut candidates.
- Two consecutive scenes with the same purpose are merge candidates.
- End with the approximate length saved (pages or %).
- Do not rewrite.

[Manuscript]
[Script (several scenes)]

Free runs use the fast model and return a short preview (about 300 words). Only the first ~1,000 words of manuscript are read.

How to use this prompt

1
Fill in the variables
Enter your manuscript, characters or situation in the fields below. The example values are hints.
2
Check the assembled prompt
The prompt is assembled below with placeholders filled. Edit any rule to fit your work.
3
Copy it or run it
Copy it into the tool you already use, or run it in SparkLore for a short preview.
4
Revise the result into your manuscript
The output is a draft. Follow the tips and rewrite half of it by hand.

How to get the most from it

'Breaks: none' plus 'keep' means a tone scene. Ask yourself whether that tone is truly needed.
Bring the table to the editing meeting; it shortens the 'why cut this scene' argument.

Use it in the studio with your story bible

← Prompt library