Presentation Deck

What it is: the content of a business presentation - what each slide says, why it is there, what evidence backs it and what the speaker says while it is on screen.

Overview

Works out the smallest useful deck for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a slide register. The slide register - CSV, SQL DDL, JSON Schema, Notion mapping - is produced on request, from one field list and check field names, nullability and constraints across the requested formats before delivery.

Layer: Layer 6: Engage. Fits: Growth stage. Table code: n/a.

The rule this table exists to enforce: a slide has one job, and the register names that job. Key Message is a sentence a listener could repeat afterwards, and Bullets is at most three supporting points - a slide with six bullets and no key message is a document being read out. Data Source is required for every slide carrying a number, because a figure with no source is the single most common way a business loses a room.

The second rule: the deck is a derivative of everything else in this pack. The brand tokens are in design-theme-guide, the proof in gbp-local-seo-intent, the offer in business-website-setup. A deck built before those exist is a deck of opinions.

When to Use This Skill

• presentation, deck, slides, pitch, pitch deck
• "we have to present to a bank", "investor deck", "client pitch"
• what should our slides say, story structure, narrative
• sales deck, proposal deck, board update, team briefing
• speaker notes, timing, rehearsal
• turning a report into a presentation

Do not use it for: the printed leave-behind (brand-kit-print-collateral), a written proposal document, a website page, or the brand identity itself (design-theme-guide, logo-image-design).

How It Works

Use the self-contained intake and validation steps below. Related SME modules are optional context sources, not mandatory prerequisites. Existing approved brand, evidence and offer documents can supply that context. Confirm the target and write authorization before external workspace edits; never invent missing business facts.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "make" / "build" / "we have to present" -> artifacts wanted; go to Step 2.
• "review" / "check" / "does this work" -> a check, not a build.
• "help me structure" / "what should I say" -> a decision question; answer, then offer the build.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: Who is this presentation for, and what do you want them to decide or do afterwards?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything already answered. Ask the rest one at a time, and stop as soon as the remaining answers would not change the slide list.

• Audience - Who is in the room - customers, a bank, investors, a board, a partner, the team? / What do they already believe about the business? / How many people, and how long is the slot?
• Ask - What exactly must happen after the presentation - a decision, a signature, a payment, an introduction, an internal approval? / What is the one sentence that, if they remember nothing else, should they remember?
• Evidence - What can be shown - revenue, customers, reviews, photos, a process, a team, a track record? / Is any of it confidential? / Where does each number come from?
• Constraints - Any template, brand tokens or house format to follow? / Any content that must not appear? / Is the presenter comfortable with the numbers, or should those be in an appendix?
• Setup - Who presents, and is there a second presenter? / Will it be in person, on a call, or recorded? / How much rehearsal time is there?

Never invent an answer. Figures, revenue, growth rates, customer names, dates, market sizes and outcomes the user has not supplied are Unknown. A business case with invented projections is worse than no deck.

Step 3 - Hold the internal context

module: presentation-deck
intent: null            # set up | review | report | import
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:

…