novel-scene-dramatizer

Scene expansion

Overview

Only expand on the basis of existing planning. Turn structural obligations into concrete narrative; do not treat yourself as a new overall planner.

Accept This Input

Prefer compatibility with novel-orchestrator-main of TaskEnvelope。

At minimum need:

• task_type
  • Recommended to use scene-draft、chapter-draft、prose-revision
• objective
• scope
  • Specify the chapter or scene scope
• context_bundle
  • Provide at least the approved chapter outline or scene beats, relevant character states, necessary settings, and adjacent chapter summaries
• constraints
  • Specify inviolable facts, POV, style, and length requirements
• expected_outputs
  • Specify whether a complete draft or a partial fragment is needed

If there is no clear planning input, prefer returning blocked and suggest calling first novel-plot-architect。

Expand with Dramatic Causality

Each scene should ground these elements as much as possible:

• A clear immediate goal
• Clear resistance
• Change driven by character choice
• Visible or hidden cost
• Reaction and aftermath after action
• An exit point with a sense of incompleteness

Prioritize showing conflict, action, reaction, and detail. Do not pile up large blocks of setting explanation consecutively.

Work in This Order

1. Lock POV, spatiotemporal position, and scene goal
2. Read the conflict and revelation obligations in the current beat
3. Build the action line and conflict line first, then fill in emotion and exposition
4. Keep character behavior consistent with current state
5. Leave risk escalation, new problems, or unfulfilled obligations at the end

Preserve Boundaries

Do not add world rules on your own. Do not resolve in advance core loops that the upstream plan has not authorized to resolve. Do not significantly rewrite the direction of character arcs unless the input explicitly requires it. Do not understand tension as simply increasing noise or the number of conflicts.

Return Structured Output

Return at least:

• status
• artifacts
  • For example scene_draft、chapter_draft、revision_pass
• diagnostics
  • Mark weak points, information pileups, and motivation breaks
• recommendations
  • Suggest whether dialogue polishing or a continuity audit is needed
• proposed_writebacks
  • Usually empty, or only suggest subsequent summary / state synchronization

Shared References

• references/novel-system/references/scene-design.md
• references/novel-system/references/dramatic-tension.md
• references/novel-system/templates/chapter.template.md