# Claude Slides for Product Managers: 32 Claude Skills for Every Deck You Have to Make Every deck a product person makes — the board pre-read, the QBR, the roadmap review, the all-hands, the sprint review, the launch deck — drafted in Claude Slides from your own sources, with every number traced. - Page: https://lantern.meet-polar-bear.com/skills/slides-for-product-managers-pack - Download: https://lantern.meet-polar-bear.com/skills/slides-for-product-managers-pack.zip - Source: https://github.com/polar-bear-org/claude-skills/tree/main/packs/slides-for-product-managers-pack - Price: free ## Install in Claude Code ``` /plugin marketplace add polar-bear-org/claude-skills /plugin install slides-for-product-managers-pack@polar-bear-skills ``` ## The 32 skills you get The set follows a deck from setup to the version people read cold, in six stages: the start every deck runs from, the decks for leaders, the updates for everyone, the team decks, the decks for customers and the market, and the passes that make a deck hold up. ### 1 · Start every deck - **Deck Context File** — use when: Every deck starts from zero and Claude guesses your metrics. Output: deck-context.md: product, users, metric dictionary with owner, source, base and period, audiences, house words. - **Slide Design System** — use when: Every deck looks different and AI slides ignore your brand. Output: Layout library, grid, type scale, colour roles, chart and table styles, components, do and don't rules. - **Deck Brief** — use when: You cannot get to the point for execs, and decks end with no ask. Output: Audience and decider, the one belief or decision, live or read cold, facts with sources, the ask with a date. - **Ghost Deck Storyline** — use when: Decks eat days of rework and the draft has no argument. Output: Action title per slide, evidence per title, executive summary in SCR order, slide budget, titles-only read. - **Doc to Deck** — use when: The doc exists and the room still wants slides. Output: Deck drafted from a PRD, PR-FAQ, strategy doc or report, keep-in-the-doc list, doc-versus-deck check. - **Audience Cuts** — use when: One update, many audiences, and four files to keep in sync. Output: Exec, sales, company and customer cuts, each with its own first slide and ask, one change log. ### 2 · Decks for leaders - **Executive Summary One-Pager** — use when: The exec reads one slide and decides from it. Output: One slide: bottom line, ask with a date, three reasons with one sourced number each. - **Executive Summary Two-Pager** — use when: One slide loses the story and ten is too many. Output: Key points and the ask on slide one, sourced insights worth knowing on slide two. - **Roadmap Review Deck** — use when: Dates become promises and the loudest leader sets the roadmap. Output: Strategy recap, shipped vs said, Now Next Later with confidence, not doing and why, decision needed. - **Product Strategy Deck** — use when: There is no clear strategy to say no against. Output: What is and what could be, diagnosis, guiding policy, coherent actions, what we will not do, endorsement asked. - **Quarterly Business Review Deck** — use when: QBR prep is days of chasing data and green is not green. Output: Headline, asks first, commitments vs actuals, metrics with base and period, defined RAG, customer variant. - **Business Case Deck** — use when: The business case numbers are guesses everyone sees through. Output: The ask, cost of doing nothing, options including do nothing, value as ranges, kill criteria. - **Board Deck Product Section** — use when: The work is invisible to the board and rebuilt every quarter. Output: Three to five pre-read slides, the question for the board, fewest correct metrics, shipped vs planned. ### 3 · Updates for everyone - **Stakeholder Update Deck** — use when: You spend Friday on an update people skim in seconds. Output: What changed, what is at risk, what we need from you, sourced metric, dates with confidence, recurring version. - **All-Hands Deck** — use when: The company sees ticket lists and never the why. Output: Where we are, what shipped and for whom, the honest metric, decisions and reasons, thanks by name, Q&A prompts. - **Research Readout Deck** — use when: Research is scarce and the readout must change something. Output: The finding that changes a decision, method and sample, findings with quotes, contradictions, the decision asked. - **Product Onboarding Deck** — use when: New joiners get a sixty-slide history lesson that is out of date. Output: Product and users, strategy, roadmap now, how we decide, who owns what, first 30 days, glossary. ### 4 · Team decks - **Sprint Review Deck** — use when: Sprint reviews turn into slide shows and stakeholders only watch. Output: Sprint goal, done and ready to try, demo order, questions for stakeholders, backlog changes, five slides at most. - **Sprint Retrospective Deck** — use when: Retros repeat the same complaints and nothing changes. Output: Prime Directive, chosen format, last actions and what happened, prompts, one to three experiments with owners. - **Working Agreement Deck** — use when: The team argues about the same habits and nothing is written down. Output: The friction, draft agreements as testable behaviours, non-negotiables, a decision rule, a review date. - **OKR Check-In Deck** — use when: OKRs are set in January and reviewed in panic in March. Output: Key results with current value and source, confidence and why it moved, blockers, decisions needed. - **Kickoff Deck** — use when: Kickoffs are read aloud and nobody leaves knowing who decides. Output: Why now, goal and success measure, scope in and out, roles and decision rights, risks, first milestones. - **Team Offsite Deck** — use when: The offsite is a week away and the agenda is a list of talks. Output: Agenda with an outcome per session, announcements, recognition, connection moments, decisions, what happens after. ### 5 · Decks for customers and the market - **Go-to-Market Launch Deck** — use when: Sales and support learn about the launch from customers. Output: Launch in one customer sentence, positioning and proof, tier and date, readiness by owner, sales cut, success metric. - **Customer Case Study Slides** — use when: Case slides show results with no baseline and logos nobody cleared. Output: One or five slides: the change in the title, before, what they did, results with base and period, approved quote. - **Sales Demo Deck** — use when: Thirty slides of company intro delay the product. Output: What we heard, the outcome wanted, the result shown first, two or three workflows, proof, a dated next step. - **Customer Advisory Board Deck** — use when: The advisory board turns into a sales pitch and the loop never closes. Output: What you told us and what we did, product forks framed as options, a concept to react to, exercise prompts. - **Conference Talk Deck** — use when: A talk turns into a pitch with figures that cannot leave the building. Output: One idea, a sourced hook, what is vs what could be, three stories, what to try on Monday, confidential-number check. ### 6 · Make it hold up - **Numbers Check** — use when: Made-up or mismatched numbers reach the board. Output: Every figure with slide, source, base, period and status, mismatches, draft marks, the chart each figure needs. - **Build in Your Design System** — use when: The content is right but every draft drifts from the brand. Output: Storyline laid out with your layouts and components only, a rule check per slide, exceptions to approve. - **One Claim per Slide Restyle** — use when: The Claude Slides draft is competent but plain and reads as AI. Output: Dense slides split, sentence titles, evidence instead of bullets, AI tells removed, before and after list. - **Pre-Read Slidedoc** — use when: The deck will be read, not presented, or people will not attend. Output: Read-cold version with full-sentence slides, the decision on page one, source appendix, cover note. ## Workflows - **Set up once** (Before the first deck, so Claude stops guessing your metrics and inventing its own layouts.) Deck Context File → Slide Design System - **Start any deck** (A deck is due and nothing is drawn yet.) Deck Brief → Ghost Deck Storyline → Audience Cuts - **From a doc to a deck** (The PRD or the strategy doc already exists.) Doc to Deck → Audience Cuts - **Decks for leaders** (The roadmap review is next week.) Roadmap Review Deck → Product Strategy Deck → Quarterly Business Review Deck → Business Case Deck → Board Deck Product Section - **Customers and the market** (The deck leaves the building.) Go-to-Market Launch Deck → Customer Case Study Slides → Sales Demo Deck → Customer Advisory Board Deck → Conference Talk Deck - **Make it hold up** (The deck is drafted and has to survive the room.) Numbers Check → Build in Your Design System → One Claim per Slide Restyle → Pre-Read Slidedoc ## The quality bar - One method, applied properly: each skill uses the real mechanics of its method — the answer-first order, the action titles, the delivery confidence definitions, the Now Next Later horizons — not a generic gather, analyse, recommend - Story before slides: the audience, the decider and the ask come first, then a ghost deck of titles, then Claude Slides draws - Every skill says where its method breaks, and what fits instead - Numbers that hold: every figure carries a source, a base and a period, anything without one stays marked as a draft, and the same figure is checked across slides - Built for Claude Slides as it is: the skills use only the drafting, editing, commenting, presenting, sharing and exporting that Anthropic has published, and your look comes from written design rules, not from a claim that Slides reads your template - Work is described, people are not: team decks describe how the work works, thanks go by name and are never ranked, and no slide scores, ranks or profiles a person - The red line: Claude Slides drafts the deck from your sources; every number on a slide traces to one, nothing is invented to fill a gap, and you decide what the room is asked to decide ## Questions people ask ### What is in the Claude Slides for Product Managers pack? 32 Claude skills for the decks a product person makes, in six stages: start every deck, decks for leaders, updates for everyone, team decks, decks for customers and the market, and make it hold up. Each skill is one deck type or one deck method. ### How do I install these Claude skills? In Claude Code, two lines install all 32 at once. In Claude.ai or Claude Desktop, download the zip, open Settings, Skills, Add, and upload the skills you want. Either way it takes about five minutes. ### Do I need Claude Code to use them? No. The skills work in Claude.ai, Claude Desktop and Claude Code. In the app you upload them yourself; in Claude Code one command installs the whole pack. ### Do the skills work with ChatGPT or other assistants? They are built as Claude Skills, and installing them is a Claude feature. Each one is a plain Markdown file, so you can read it and reuse the method elsewhere, but it will not load and trigger by itself outside Claude. ### Will Claude decide what the deck asks for? No. Claude Slides drafts the deck from your sources. Every number on a slide traces to one, nothing is invented to fill a gap, and you decide what the room is asked to decide. ### Is the pack free? Yes. It is free to use inside your company and in client work, and not for resale. There is no signup: the download and the install command are on this page. ## About Written by Polar Bear (https://meet-polar-bear.com/). Published on Lantern (https://lantern.meet-polar-bear.com/), which turns your notes, documents and call transcripts into social post drafts you review and publish.