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

envision-findings-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

Envision Findings Deck

Generate the slide-by-slide script for an RBA Envision recommendations deck: research findings, synthesized insights, and a strategic recommendation for a client leadership audience. This is RBA's most important Envision-phase deliverable. The non-negotiable rule: every slide title states a finding or conclusion, never a topic. Output is a script the user pastes into Claude in PowerPoint to assemble inside the RBA master template.

When this skill applies

  • User has synthesized Envision research and needs the leadership readout deck
  • User asks for the "Envision deck", "findings deck", "recommendations deck", or "research readout"
  • User wants insights framed as arguments, not topic labels

Skip when: the user wants a kickoff deck (project-kickoff-deck) or discovery interview questions (stakeholder-interview-guide).

Inputs

Collect these before generating. Vague inputs produce vague slide titles — push for real data, quotes, and stats.

Input Required Description Example
Client Yes Client name Riverside Health System
Deck title Yes Full deck title Primary Care UX — Envisioning Recommendations
Date Yes Month Year April 2026
Engagement description Yes What the Envision covered UX audit and redesign recommendations for the Primary Care patient portal
Agenda Yes 4-6 section names Context, Research & Insights, Concepts, Recommendation, Next Steps
Insights Yes Findings WITH data, quotes, stats 72% of users couldn't find scheduling in 2 min. 3/5 stakeholders named navigation as top frustration.
Concepts Yes Options presented Concept A — simplified nav. Concept B — role-based landing pages.
Recommendation Yes Direction + exactly 3 reasons why Concept A. Lower dev effort. Directly addresses nav pain. Fits timeline.
Next steps Yes Actions with owners and dates Client confirms concept by Apr 15 (Sarah). RBA begins wireframes Apr 16 (Kassie).

Workflow

Step 1 — Validate inputs are finding-grade

Check that each insight carries data, a quote, or a stat. If an insight is a bare topic ("navigation is hard"), ask the user for the evidence behind it before writing a slide. The recommendation must come with exactly three reasons; if fewer, ask for the rest.

Step 2 — Lay out the Context → Insights → Concepts → Recommendation → Next-Steps arc

Map the agenda onto the standard Envision findings arc (see templates.md). Each agenda section opens with a Section - Dark slide.

Step 3 — Write one insight per slide as a finding-titled slide

This is the core of the skill. Each research insight becomes its own Content - Title and Bullets slide — never combine two. The title must state the finding or conclusion:

  • GOOD: 72% of users can't find scheduling in under 2 minutes
  • BAD: Usability Research Findings

Convert any topic-style title into a conclusion before it ships. Use Quote - Dark for verbatim stakeholder quotes.

Step 4 — Build the recommendation on three reasons

Use Content - 3 Key Points for the recommendation: the chosen direction plus the three reasons why. The recommendation slide argues the case; it does not merely name the choice.

Step 5 — Write owner-and-date next steps

Format every next step Action — Owner: [Name] — By: [Date]. No ownerless or dateless actions.

Step 6 — Sequence and format the deck

Follow the deck-structure rules and per-slide block format in templates.md: Cover - Gradient → Agenda - Dark → section opens → finding slides → recommendation → next steps → Closing - Questions With Photo → Closing - RBA End Slide. Reference the master-template boilerplate slides (Research Methodology, RBA - Envisioning Phase, RBA - Designed to Deliver, RBA - By the Numbers) by name to duplicate. Brand tokens live in the master template — reference resources/rba-design-system.md only if a slide leaves it.

Step 7 — Append PowerPoint instructions and quality-check

Add the PowerPoint-assembly block from templates.md (master-template SharePoint source, [Client]_Envision_[MonthYear].pptx save-as). Verify against the quality bar, then return the full script.

Output format

A slide-by-slide script using the per-slide block format — SLIDE [#] — [LAYOUT NAME], TITLE (a finding/conclusion), BODY (• bullets), SPEAKER NOTES — followed by a POWERPOINT INSTRUCTIONS block. Full skeleton in templates.md.

Quality bar

  • Every slide title states a finding or conclusion — zero topic labels.
  • One insight per slide; no two insights combined.
  • The recommendation slide carries exactly three reasons why.
  • Every insight slide is grounded in data, a quote, or a stat.
  • Verbatim quotes use Quote - Dark; quotes attribute role, never personal name.
  • Next steps are formatted Action — Owner: [Name] — By: [Date].
  • Deck opens Cover → Agenda and closes Questions → RBA End Slide.
  • Layout and boilerplate names match the master-template list exactly.

Reference and template files

  • templates.md — the Context → Insights → Concepts → Recommendation → Next-Steps arc, available layouts, boilerplate-slide list, deck-structure rules, the finding-vs-topic title test, the per-slide block format, and the PowerPoint-assembly instructions.
Technical details
Plugin
envision-toolkit
Author
Kassie Gibbons
Skill name
envision-findings-deck
Maturity
experimental
Security review
No security review
Owners
  • strategy
Argument hint
[--client NAME] [--title "deck title"] [--date "Month Year"] [--engagement "what Envision covered"] [--agenda "4-6 sections"] [--insights "data, quotes, stats"] [--concepts "options"] [--recommendation "direction + 3 reasons"] [--next-steps "action, owner, date"]
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
Source
plugins/envision-toolkit/skills/envision-findings-deck/SKILL.md

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