Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

project-kickoff-deck

Installable Ships in envision-toolkit — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

Project Kickoff Deck

Generate a tight, 12-14 slide kickoff script for an RBA engagement. The deck drives a 60-90 minute conversation — it aligns the room on scope, working norms, ownership, and assumptions before they become problems. Output is a slide-by-slide script the user pastes into Claude in PowerPoint to assemble inside the RBA master template, where fonts, colors, logos, and the reusable boilerplate slides are already built.

When this skill applies

  • User is starting an engagement and needs a kickoff deck
  • User asks to "build the kickoff", "prep the kickoff meeting", or "make kickoff slides"
  • User has the basics (client, team, timeline, assumptions) and wants them structured on-brand

Skip when: the user wants discovery interview questions (stakeholder-interview-guide) or a findings/recommendations deck (envision-findings-deck).

Inputs

Collect these before generating. Ask for missing required inputs; never invent scope, owners, or dates.

Input Required Description Example
Client Yes Client name Banner Health
Project Yes Project name Navigation Redesign
Date Yes Kickoff date April 14, 2026
Engagement type Yes What the engagement is Envision — UX Strategy and Wireframes
RBA team Yes Name, title, role per person Kenya Chestnut, PM; Kassie Gibbons, UXD; Dan Lopez, BA
Client team Yes Name, title for known attendees Sarah Miller, Product Owner; James Cho, IT Director
Timeline Yes Phases + key dates Discovery: Apr 14-25 · Wireframes: Apr 28-May 16 · Review: May 19-23
Tools Yes Tools/platforms the team uses Figma, SharePoint, Teams, Azure DevOps
Key assumptions Yes SOW assumptions worth surfacing One stakeholder interview scoped; client provides analytics access by Apr 16
Action items Yes First-week actions with owners Client grants Figma access by Apr 15 (Sarah); Kenya shares SharePoint by Apr 14

Workflow

Step 1 — Confirm scope and surface "out of scope"

Restate the engagement type and timeline. Explicitly ask the user what is out of scope — the most valuable kickoff slide is what RBA is not doing. If they can't name it, push: an unstated boundary is a future change order.

Step 2 — Pick the team layout

Choose Team - 3/4/5 Person to match the RBA roster size. RBA team goes left, client team right. Use exact layout names from templates.md.

Step 3 — Build the slide sequence

Follow the fixed 13-slide order in templates.md. Key beats: Cover (Gradient) → Agenda (Dark) → Team → Project Overview (scope + success metrics + out of scope) → Approach/Timeline → the boilerplate block → Tools & Access → Next Steps → Closing. Keep to 12-14 slides; every slide past 12 is a minute not spent talking.

Step 4 — Duplicate the master-template boilerplate slides

Reference these RBA boilerplate slides by name so Claude in PowerPoint duplicates them from the master template rather than rebuilding them: PM Deliverables, Project Cadence (update <Client> only), How We Work Together (update <Client> only), Project Risks (update <AE Name> only), Dependencies and Constraints. Update only the bracketed fields — never rewrite the boilerplate body.

Step 5 — Write owner-and-date next steps

Every next step must read Action — Owner: [Name] — By: [Date]. Reject "RBA will…" with no owner or date. The RASCI on the kickoff is intentionally light (8-10 rows); point the user to a dedicated RASCI skill for the full version.

Step 6 — Format every slide and append PowerPoint instructions

Use the exact per-slide block format and the closing PowerPoint-assembly instructions in templates.md, including the master-template SharePoint source and the [Client]_[ProjectName]_Kickoff_[MonthYear].pptx save-as convention. Brand tokens are not duplicated here — they live in the master template; reference resources/rba-design-system.md if a slide leaves it.

Step 7 — Quality check before returning

Verify against the quality bar, then return the full script plus the PowerPoint instructions block.

Output format

A slide-by-slide script (12-14 slides) using the per-slide block format — SLIDE [#] — [LAYOUT NAME], TITLE, BODY (• bullets), SPEAKER NOTES (2-3 sentences) — followed by a POWERPOINT INSTRUCTIONS block for assembling the deck in the master template. Full skeleton in templates.md.

Quality bar

  • 12-14 slides maximum.
  • "Out of scope" is explicitly stated on the Project Overview slide.
  • Every next step has a named owner and a date — no "RBA will…".
  • Boilerplate slides are referenced by exact name with only <bracketed> fields updated.
  • Layout names match the master-template list exactly (case and spacing).
  • Cover title reads [Project] — Project Kickoff | [Client] | [Date].
  • Speaker notes give the presenter something to say, not a re-read of the bullets.
  • PowerPoint instructions include the SharePoint master-template source and save-as naming.

Reference and template files

  • templates.md — the 13-slide kickoff sequence, the available layout names, the boilerplate-slide list, the per-slide block format, and the PowerPoint-assembly instructions.
Technical details
Plugin
envision-toolkit
Author
Kassie Gibbons
Skill name
project-kickoff-deck
Maturity
experimental
Security review
No security review
Owners
  • strategy
Argument hint
[--client NAME] [--project NAME] [--date "Month D, YYYY"] [--engagement TYPE] [--rba-team "name, title, role; …"] [--client-team "name, title; …"] [--timeline "phase: dates · …"] [--tools "…"] [--assumptions "…"] [--actions "…"]
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
Source
plugins/envision-toolkit/skills/project-kickoff-deck/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.