Xmind Notes To Deck V2

Narrative Broker Deck V2

Purpose

This v2 skill transitions the toolchain from rigid AST parsing to a Narrative Broker Architecture.

The HTML generator never parses raw XMind logic directly. It consumes an LLM-generated Intermediate JSON Manifest.

Workflow:

1. Asset Passthrough Ingestion: parse .xmind zip, extract embedded image assets to local assets directory.
2. Intermediate JSON Manifest: map slides + visuals with a strict schema.
3. LLM Narrative Synthesis: rewrite speaker protocol for conversational delivery.
4. Deck Render: generate HTML Reveal.js deck with presenter notes.
5. Script Export: generate timestamped teleprompter markdown script.

Input Contract

Required Intermediate JSON Manifest schema:

• deckTitle: string
• deckSubtitle: string
• slides: array
  • slideId: string
  • visualArchetype: split-screen-analogy | hero-metric | execution-pipeline | technical-deep-dive
  • speakerProtocol: object
    • hook: string
    • teleprompterVO: string
    • stageDirections: string
    • theDelta: string
  • blocks: array
    • title: string
    • bodyText: string
    • items?: string[]
  • visuals: array of local paths

Critical writing rule for teleprompterVO:

• teleprompterVO must sound conversational and optimized for listening, not a verbatim repeat of slide text.

Runtime Guarantees

• Strict schema validation for manifest fields and speakerProtocol.
• Embedded .xmind assets are extracted and explicitly mapped into visuals to survive LLM synthesis.
• Reveal presenter notes are populated from speakerProtocol.
• RevealNotes plugin enabled for dual-screen presenter mode (press S).
• Programmatic auto-scroll is disabled.
• Fractal noise/dither overlay is applied to prevent H.264/VP9 banding artifacts.

Commands

From this folder:

npm install npm run build

Path A: Manifest-first render

npm run deck -- --input examples/sample-manifest.json --out examples/sample-deck.html

Path B: XMind passthrough to intermediate manifest, then render

npm run deck -- --xmind ../../Pi\ Architecture/PiArchitecture_course_videos_ai_enriched.xmind --manifest-out examples/pi_narrative_manifest.json --assets-dir examples/assets --out examples/pi_narrative_deck.html

Output Artifacts

• HTML deck: cinematic Reveal.js + GSAP presentation.
• Teleprompter script: Teleprompter_Script.md.
• Optional intermediate manifest from .xmind ingestion.

Upstream Invocation Contract

• transcript-to-notes, md-to-notes, and pdf-to-notes must invoke this skill after narrative-manifest generation.
• Upstream runs are incomplete if they stop at manifest creation and do not emit both the deck HTML and a teleprompter script.
• When an upstream skill wants deterministic filenames, it should pass --script-out <target.md> explicitly.

Shared Manifest Authoring Templates

• Prompt template:
  • skills/xmind-notes-to-deck-v2/templates/narrative_manifest_prompt_template.md
• JSON skeleton:
  • skills/xmind-notes-to-deck-v2/templates/narrative_manifest.template.json

All notes skills that generate <CourseName>_narrative_manifest.json should use these shared files to keep schema and behavioral mandates synchronized.

Notes

• Keep this v2 skill isolated from legacy xmind-to-pitch-deck until migration parity is complete.
• The LLM director stage is responsible for narrative quality and conversational teleprompterVO style.