Centralize scene planning and description assets

assets/dnd/scenes/prompts/dnd.scenes.yaml

@@ -0,0 +1,36 @@
+id: dnd.scenes
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+  - name: players
+    required: false
+    content_type: text/plain
+  - name: party
+    required: false
+    content_type: text/plain
+  - name: glossary
+    required: false
+    content_type: text/plain
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-references.md
+    cache_control:
+      type: ephemeral
+  - role: user
+    content_file: ./task.md
+  - role: user
+    content_file: ./instructions.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_scenes.v1.json
+  repair_attempts: 0

assets/dnd/scenes/prompts/instructions.md

@@ -0,0 +1,8 @@
+Cover the complete provided transcript from its first source unit to its last
+source unit. Return scenes in source-unit order with no gaps or overlaps. Use
+only positive integer source-unit IDs from the transcript, and give every scene
+one inclusive `start_unit_id` and one inclusive `end_unit_id`.
+
+Return exactly one JSON object and no explanatory text. The object must contain
+only a non-empty `scenes` array. Each scene object must contain only
+`start_unit_id` and `end_unit_id`.

assets/dnd/scenes/prompts/task.md

@@ -0,0 +1,18 @@
+Divide the provided transcript into coherent Dungeons & Dragons scenes for the
+`dnd/scenes` chunk module.
+
+A scene is a coherent unit of play. Start a new scene when the transcript
+establishes a meaningful change in location, objective, threat, activity,
+encounter, or mode of play. Good reasons include a material move, beginning or
+ending combat, a substantially different encounter phase, a shift between
+combat, exploration, social interaction, planning, travel, rest, or downtime,
+a change in the central NPC, faction, threat, or objective, or a sustained
+table-level interruption that materially changes the activity.
+
+Do not split a scene merely because a speaker or combat round changes, a
+routine turn occurs, or the table briefly digresses. Prefer fewer coherent
+scenes over speculative or fine-grained boundaries.
+
+Return only inclusive `start_unit_id` and `end_unit_id` endpoints for each
+scene. Do not return titles, modes, participants, summaries, boundary notes,
+confidence, caveats, final chunk IDs, or chunk indexes.