gamma-decklisted

# Gamma Deck Skill Create polished presentations through a three-stage pipeline: ``` Stage 1: BRIEF Stage 2: SYNOPSIS Stage 3: GENERATION Interview → deck-brief.md → synopsis.md → Gamma MCP → Live deck ``` The quality of a generated deck is almost entirely determined by what happens *before* generation. Gamma is a rendering engine — it does exactly what you tell it. The brief captures intent. The synopsis translates intent into slide-by-slide content. The generation step is mechanical. Invest the time in Stages 1 and 2. --- ## Stage 1: The Brief (Interview) Build a comprehensive brief through iterative, one-question-at-a-time conversation with the user. This is the PM-style requirements gathering pattern — each question builds on the previous answer, progressively narrowing from strategic intent to tactical slide content. ### Before You Ask Anything Gather available context silently first. Check: - **Conversation history** — the user may have already described what they want - **Uploaded files** — documents, reports, data that should feed the deck - **Workspace/repo** — if they mention a project, explore it (README, docs/, data files, previous presentations) to extract facts, metrics, timelines - **Existing decks** — check for previous presentations in the workspace for tone/style precedent Extract as much as you can. The more you know before the first question, the sharper your questions will be and the fewer you'll need. ### The Interview Ask **o