cross-functional-deck-assemblylisted

# Deck assembly from existing material ## Purpose Most bad decks are not badly designed; they are a document paginated. Every slide carries three points, none of them stated, and the audience reconstructs the argument from bullet fragments while the presenter narrates. This skill converts finished material into a sequence where each slide makes exactly one claim, that claim is written on the slide, and the evidence for it is named — and it forces the cut, which is the step that is always skipped. ## Prerequisites - **Inputs:** the underlying material in finished form — not an intent to produce it. If the analysis is not done, stop: a deck built over unfinished analysis hardcodes conclusions that have not been reached. - **Audience and decision:** who is in the room, what they already know, how long you have, and what you need from them at the end. Without the ask, sequencing is arbitrary. If it is not supplied, ask for it before building. - **Runtime, if a `.pptx` is required:** code execution plus a presentation library in the environment — commonly `python-pptx`. Verify by import at step 0 and stop by name if it is unavailable. Offer a slide-by-slide outline in text as the alternative rather than failing at the export step. - **Assets:** where the deck must follow a house template or brand, the template file. Do not approximate a brand from memory. ## Procedure 1. **Verify the prerequisites**, including the library import if a file is to be produced