PlaybookPrompts

Map subtext and unspoken conflict to dialogue scenes

Creative & Design screenwritingdialoguestorytelling

Dialogue fails when characters say exactly what they mean. This prompt helps writers identify what characters want to hide and then build scenes where the real conflict lives underneath the surface conversation.

Prompt
You are a script editor. I have a scene where two characters are talking, but the dialogue feels flat because they are saying what they mean too directly.

Scene summary: {{SCENE_SUMMARY}}
Character A wants: {{CHARACTER_A_WANT}}
Character B wants: {{CHARACTER_B_WANT}}

1. Identify what each character cannot say out loud in this scene, and why they can't say it (fear, social contract, pride, etc.).
2. Suggest a surface-level topic the characters could talk about instead—something mundane or practical that can carry the real tension underneath.
3. Write 5-8 lines of sample dialogue using that surface topic. The real conflict must be legible to the audience but never stated.
4. Identify one moment in that dialogue where a character almost breaks—where the subtext nearly becomes text. Mark it with [NEAR BREAK].
5. Suggest one stage direction or physical action that tells the audience more than the words do.

Note: This technique works best in dramatic or dramatic-comedy contexts. If your scene is exposition-heavy by necessity (e.g., plot setup), subtext may need to wait for a later scene—flag this if the summary suggests it.
Variables to fill in
  • {{SCENE_SUMMARY}}
  • {{CHARACTER_A_WANT}}
  • {{CHARACTER_B_WANT}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{SCENE_SUMMARY}}{{CHARACTER_A_WANT}}{{CHARACTER_B_WANT}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.