presentation-factory-create-flow

name	presentation-factory-create-flow
description	The main orchestrator for the Slalom Presentation Factory. Walks the user through the Frame → Draft → Compose → Ship pipeline end-to-end. Uses AskUserQuestion for discrete decisions; conversational input for free-text. Routes through stage orchestrators and pulls specialty skills from the presentation-factory plugin (slalom-brand, higgsfield, napkin, design-layout, animations, html-player, humanize) plus consulting, design, marketing, and brand plugins. Auto-activates when a user runs /presentation-create or starts a new chat in the Presentation Factory Cowork project. Output is the HTML player (canonical); PDF and PPTX are optional derivatives.
type	skill
plugin	presentation-factory
tags	["type/skill","plugin/presentation-factory","scope/orchestrator","topic/pipeline"]
status	active

Goal

Take the user from "I need a deck on [topic]" to a finished, branded, interactive HTML player in the right folder. End-to-end. Cowork-native. AskUserQuestion at every discrete decision.

When to invoke

• User runs /presentation-create
• User starts a new chat asking for a deck and the intent is unambiguous
• User asks any version of: "build a deck for [audience]," "I need slides for [event]," "make a pitch for [client]"

For partial workflows, route to the stage orchestrator directly via the matching slash command: /presentation-frame, /presentation-draft, /presentation-compose, /presentation-ship.

Required context

For pipeline mechanics, the two styles, the three brands, the 25 templates, the full skill graph, anti-patterns: ../../references/presentation-factory-foundations.md.

For the toolchain (Higgsfield, Napkin, Flaticon, Chromium, PowerPoint MCP): ../../references/presentation-factory-toolchain.md.

For Slalom brand patterns from the May 2026 crawl: ../../references/slalom-brand-patterns.md.

Do not re-explain the pipeline. Cite the foundations file.

Stages

Stage 0: Diagnose intent (30 sec)

Before invoking any stage, confirm what the user wants. Use AskUserQuestion:

Question: "What would you like to do?"
Options:
1. Create a new presentation from scratch (full pipeline). Recommended.
2. Update an existing deck (refresh content, re-render, or change brand)
3. Run only one stage (frame / draft / compose / ship)
4. Check status of decks in WIP

• New from scratch: proceed to Stage 1.
• Update existing: ask for the deck name. Load the existing WIP/[deck]/ (or restore from Archive/). Skip to the stage the user wants to begin from.
• Single stage: route to the matching orchestrator skill.
• Status: call presentation-factory-status. List WIP/ decks and which stage each is at. Stop.

Stage 1: Frame

Hand off to presentation-factory-frame. That skill:

1. Walks the intake via AskUserQuestion:
   • Style (informational | presentational)
   • Brand (Slalom | Composable DXP | Client)
   • Audience, runtime, purpose, context
2. Calls the presentation-factory-scaffolder agent to create WIP/[deck]/.
3. Calls presentation-factory-slalom-brand (or the DXP / Client equivalent) to populate WIP/[deck]/brand/ with tokens and logo.
4. Writes 00_Intake_Brief.md.

Returns when intake is complete and brand assets are in place.

Pause point: confirm intake before drafting.

Question: "Intake complete. Ready to draft the content?"
Options:
1. Yes, start drafting. Recommended.
2. Yes, but draft only the title plus first 3 slides so I can review the framing
3. Pause. Let me add more context first.

Stage 2: Draft

Hand off to presentation-factory-draft. That skill:

1. Calls presentation-factory-content-author to:
   • Lock the narrative arc
   • Author each slide's content with italic-emphasis applied per brand
   • Specify image / infographic / icon needs as prompts in 10_Content.md
2. Calls presentation-factory-design-layout to:
   • Pick a template from the 25-template catalog for each slide
   • Set visual hierarchy and density
   • Run the four checks (swap, squint, signature, token)
3. Calls presentation-factory-speaker-notes to ensure every slide has 3 to 5 sentence speaker notes.
4. Calls specialty skills from other plugins:
   • consulting:consulting-management-consultant for POV alignment
   • marketing:marketing-copywriter for body copy
   • brand:brand-voice-tone for register
5. Calls presentation-factory-humanize (Pass 1) on 10_Content.md to strip AI tells.

Returns when WIP/[deck]/10_Content.md is complete and humanized.

Pause point: review content before composing.

Question: "Content draft complete ([N] slides). Ready to compose into HTML?"
Options:
1. Yes, compose all slides. Recommended.
2. Yes, but I want to refine slides X, Y, Z first
3. Pause. Let me read 10_Content.md and edit directly.

Stage 3: Compose

Hand off to presentation-factory-compose. That skill orchestrates a sequenced set of specialty skills:

1. Asset generation (parallelizable by slide):
   • presentation-factory-higgsfield for stills (nano banana 2), video (seedance 2), and text-in-image (chatgpt image 2)
   • presentation-factory-napkin for diagrams, frameworks, value chains
2. Slide composition: presentation-factory-slide-composer reads the templates from resources/templates/, substitutes content from 10_Content.md, embeds assets from assets/, and writes one HTML file per slide to WIP/[deck]/slides/.
3. Animation choreography: presentation-factory-animations annotates slides with data-animate attributes and writes slides/animations.manifest.json.
4. Player assembly: presentation-factory-html-player builds WIP/[deck]/slides/player/ with index.html, player.css, player.js, and manifest.json (presenter-mode player).
5. Humanize Pass 2: presentation-factory-humanize runs on the rendered slide HTML to catch anything composition introduced.

Returns when WIP/[deck]/slides/player/index.html is loadable and verified.

Pause point: review the rendered player.

Question: "Slides composed and player assembled. How does the deck look?"
Options:
1. Ship it. Promote and optionally export PDF + PPTX. Recommended.
2. Re-compose specific slides (I'll tell you which)
3. Re-render assets (a slide image didn't land)
4. Go back to content and revise

Stage 4: Ship

Hand off to presentation-factory-ship. That skill:

1. Calls the presentation-factory-promoter agent to move the deck to its canonical home based on intent (library / pursuit / talk / solution / client-one-off).
2. Optionally calls presentation-factory-html-to-pdf to render each slide HTML to PDF and merge into deck.pdf (for leave-behinds).
3. Optionally calls presentation-factory-pdf-to-pptx to convert into editable PowerPoint (deck.pptx).
4. Archives WIP.

Returns when promotion is complete.

Done: surface the deliverables

Deck complete.

[Open the HTML player](computer://[full-path-to]/slides/player/index.html)
[Download PDF (optional export)](computer://[full-path-to]/exports/deck.pdf)
[Download PowerPoint (optional export)](computer://[full-path-to]/exports/deck.pptx)
[Source content](computer://[full-path-to-archive]/10_Content.md)

Offer to schedule a quarterly review if the deck is in the internal library (likely to get reused).

Anti-patterns (orchestrator-level)

• Don't skip the intent diagnosis. Assuming "new from scratch" when the user wanted a refresh wastes a lot of work.
• Don't auto-advance past pause points. Every pause is a chance for the user to catch a wrong assumption cheaply.
• Don't invoke specialty skills out of order. Content must come before layout. Layout must come before assets. Assets must come before composition. Composition must come before the player.
• Don't let the brand setup get skipped on Client decks. A "Slalom-branded" client deck is a credibility hit.
• Don't ship without running presentation-factory-humanize twice. Once after Draft, once after Compose. Both are mandatory.
• Don't ship a PPTX as the primary artifact. The HTML player is the canonical deliverable. PPTX is a derivative export.