Monthly Team Meeting Deck

Lead the meeting. Delegate the production.

The first time most people use an AI assistant for a team presentation, the reaction is the same: it found the content, organized it, and produced something close to usable — faster than expected. That moment is the baseline, not the ceiling.

The step that separates occasional users from people who get consistent value is leading the work rather than just starting it. A capable assistant is genuinely strong at collecting information across email and documents, synthesizing what is relevant, and turning it into structured, readable output. What it cannot supply on its own is the strategy of the meeting — what the story is this month, what your team needs to hear, what decision the room has to make. That is leadership work, and it stays with you. The files and details that support it are production work, and that is what you delegate.

This guide builds that division in. It sets up a workspace that carries your template, your process, and optionally your writing style forward from one session to the next. You direct. The assistant produces.

I built and run this in Claude, so Claude is the worked example throughout. Most of it — my estimate is 90% — carries to ChatGPT or Microsoft Copilot with small adaptations; the table below maps the terms. And an honest disclosure: I designed this for a colleague and it has not yet been through months of field use. Run it and tell me what breaks.

The same idea in each tool

Names move fast in these products; treat the table as a map, not a spec, and check your tool’s current documentation. The process in this guide is the part that transfers.

This guide gives you three things

How to use this guide

• Read Part 1 and follow the setup steps once.
• Copy Part 2 into your workspace instructions field exactly as written.
• Copy Part 3 into a plain text file, name it DeckSkill.md, attach it to the workspace. (Both are also downloadable below.)
• Optional steps are marked. Skip them and the system still works. Do them and the deck sounds like you.

Setup Guide — do this once, about 20 minutes

Step 1 — Create a workspace

In your assistant, create a new project (Claude or ChatGPT) or the equivalent persistent workspace in your tool. Name it something clear:

All your monthly deck work — and any future communication skills — lives here. The workspace stores your instructions and reference files so the assistant carries context into every new session automatically.

Step 2 — Add the instructions

Open the workspace settings and paste in the text from Part 2 exactly as written. About ten lines. It tells the assistant that skill files are how this workspace works and where to look for them.

Do not put the full deck process in the instructions field. That goes in a file — see Step 3.

Step 3 — Create and attach the Deck Skill File

Part 3 is the full deck process in plain text. Copy it into any plain text editor — Notepad, TextEdit, Notes — or use the download link under the block. Fill in the four fields in brackets:

• Your title
• Your team name, size, and function
• Who is in the room for these meetings
• Two to four standing themes your team cares about year-round

Save the file as DeckSkill.md and attach it to your workspace. A capable assistant finds it by description — you do not need to name it precisely each session.

Step 4 — Create a slide template reference

Start a new chat thread inside the workspace. Say:

Save the output as a plain text file and attach it to the workspace. Name it something obvious.

OPTIONAL — Step 4a: Build your writing style guide

This step makes the deck sound like you wrote it. Skip it and the output will be clean and professional. Do it and the deck will carry your own craft and voice.

What this does. The assistant analyzes slides you have already made and extracts a personal style guide: how you title things, how much text you put on a slide, how you structure an argument, what your native diagram patterns look like. That file goes into your workspace and the assistant refers to it every session.

What you need. Ten to twenty slides that honestly represent how you communicate. Variety beats polish. Slides from different decks are fine.

The session — do this once in a new thread. Start a new thread inside the workspace. Attach your sample slides. Say:

The assistant reads your slides, then asks a few questions about choices you made. That conversation is where your intent gets captured. Save the result as a plain text file and attach it to the workspace.

Update it over time. After a few sessions you will notice things it missed. Start a thread, paste the relevant section, say update this.

Step 5 — Start your first deck session

Start a new chat thread inside the workspace — one thread per meeting, no exceptions. Say:

The assistant finds the deck skill file, loads the process, and walks you through it step by step. Attach any month-specific files directly in the thread.

Workspace Instructions — paste exactly as written

This is a router, not a spec. About ten lines. Do not add to it or reformat it.

Download: project-instructions.md

Deck Skill File — save as DeckSkill.md

Copy everything below into a plain text editor, or download the ready-made file. Fill in the four fields in brackets. Save as DeckSkill.md. Attach to your workspace. Plain text only — no formatting.

Download: deck-skill.md