Playbook: Create A Presentation or Document (Advisor)

 Playbook: Deliverable Handoff (Advisor)

Surface: Compass Advisor, used by a destination logged into their own Playeasy profile.

What this produces: a complete data package — plus explicit, format-specific build instructions — that a destination hands to a separate Claude, ChatGPT, or Copilot session to build a presentation, Excel workbook, Word document, or PDF from. Advisor has neither file-creation tools nor access to the destination's brand kit, so this playbook never produces the deliverable and never gathers branding — both happen on the receiving end.

What it is not: branded automatically. Nothing here supplies a logo, a color palette, or a font. If the destination wants a branded result, that's a conversation between them and whatever session builds the file — not something Advisor gathers or passes along.

Replaces: the four earlier format-specific hand-off playbooks (Presentation, Spreadsheet, Document, PDF). One format choice up front, in Step 2, replaces four nearly-identical files.

Why this looks the way it does

Advisor can read the destination's data. It cannot create a file, and — this is the change from earlier versions of this playbook — it does not have access to `brand_kit` or any other source of the destination's visual identity. Earlier versions asked about logo, colors, and fonts as part of the hand-off. That step is gone. If a branded look matters, the destination supplies it directly to whichever session builds the file, or that session asks them once it's building — Advisor's job stops at packaging the data and the instructions.

What doesn't change: propose the structure before building it, use real data only, never fabricate a comparison the data doesn't support, and flag anything that reads as an error rather than presenting it as a highlight.

Step 1 — Confirm what's being packaged

If no report has been completed yet in this conversation, don't proceed to packaging at all. Say so directly:

To create a presentation or report, you'll first need to run at least one playbook that supplies the data — you can run more than one before coming back here. Which would you like to run?

Then search platform_knowledge_search for the current Advisor Playbooks (search term: "playbook") and list what comes back — excluding this playbook itself — so the list always reflects what's actually published rather than a fixed list baked into this file. Let the destination pick, then step aside; this playbook has no role in running whatever they choose.

Once at least one report exists in the conversation, keep it in mind for the rest of the session — but don't force the moment. Periodically, and only where it fits naturally (after a report finishes, or when the destination seems to be wrapping up), offer to build a deliverable from what's there so far: "Want to turn this into a PowerPoint presentation, Excel workbook, Word document, or PDF?" Don't ask after every single exchange, and don't wait until they explicitly invoke this playbook by name either — a well-placed offer once real data exists is more useful than either extreme.

If a report already exists, identify every report completed in this conversation. If there's exactly one, use it. If there's more than one, ask the destination which one, several, or all of them they want included — don't assume a single-report choice, and don't assume the most recent one without asking.

If more than one report is selected, check whether they share an obvious reason to sit in the same deliverable. Two reports from the same destination in the same rough timeframe combine naturally. Two that don't obviously belong together are worth a one-line check before packaging them as one file.

Step 2 — Which format?

Ask directly, as a lettered list:

1. Presentation (PowerPoint slides)
2. Spreadsheet (Excel workbook)

1. Word document
2. PDF

The rest of this playbook branches on the answer at Step 4. Everything else is shared.

Step 3 — Package the data

Reproduce each selected report's actual output as clean markdown — its tables, its figures, its structure, whatever shape it happens to be. This step is deliberately generic: it doesn't reference any one report's specific tables by name, because the report behind it could be any playbook this conversation has run, today or in the future.

When more than one report is included, give each its own clearly labeled section. Never combine a figure from one report with a figure from another — don't sum two totals, don't merge two tables into one — unless the destination has explicitly asked for a combined number across them.

Step 4 — Apply the format-specific structure

Before assembling anything, propose the structure below to the destination and get sign-off. Catching a wrong section title or a missing report here is a one-line fix; catching it after the hand-off block is built is not.

If Presentation (A):

• The outline is the structure — a slide-by-slide plan, proposed before anything else.
• Ask slide count and how the destination wants to be credited on the deck, directly.
• For the look of it, ask an open question rather than a forced pick: "What kind of style are you looking for? For example: minimalist, colorful, graphs and data visuals where the data supports it, space for image placeholders, or plain text — describe it however makes sense to you." Let them answer in their own words; the examples are there to prompt a description, not to be chosen from like a menu.

If Spreadsheet (B):

• Sheet 1 is always "Overview," with a Table of Contents linking to every other sheet — even for a single-table export.
• One table per sheet, always. Never merged, never split.
• Tables from different reports never share a sheet; the Table of Contents groups sheets by the report they came from when more than one is included.
• Sheet names stay inside Excel's real limits — 31 characters, never \ / ? * [ ] :.

If Word document (C):

• A title page comes first, followed immediately by a real, native Table of Contents — Word's actual built-in TOC field, never a manually typed list standing in for one.
• One report becomes one major section, under its own Heading 1 — never blended into one continuous narrative unless the destination explicitly asks for a unified summary.
• Headings are real Word Heading styles, applied consistently. A faked heading (bold or larger plain text) is invisible to the TOC field and to Word's Navigation Pane — this isn't a style preference, it's what makes the whole template work.
• Tables inside a section are real Word tables, never an image of a table.

If PDF (D):

• Ask the design direction directly, as a lettered list: A. Images & illustration-forward. B. Data-forward. C. Minimalist. D. Something else — describe it.
• Ask the page count directly: a single-page leave-behind, a short 2–4 page summary, or a longer report-style piece.
• Ask if there's a preferred font — otherwise the receiving session picks something appropriate to the chosen style.
• Check for tension between the answers before moving on. An images-and-illustration-forward style on a single page, carrying several reports' worth of data, is a real conflict — say so and ask which one gives, rather than silently picking.
• The page-by-page plan is the structure here, proposed before anything else, the same way the outline works for a presentation.

Step 5 — Build the hand-off block

Assemble one block containing:

• The destination's name
• The destination's own website URL — pull it from profile_details(Destination). This is the only brand-adjacent thing Advisor supplies: not a color, not a logo, just a real link the receiving session can visit itself if it needs one.
• The chosen format and its structural requirements from Step 4
• The packaged data from Step 3, organized by proposed section/sheet/slide/page as appropriate to the format
• This explicit instruction list, addressed to the receiving session:

1. Follow the structure confirmed below — outline, sheet list, section list, or page plan, whichever applies. Don't restructure it without asking me first.
2. Confirm the format-specific choices below with me before building, even if I already indicated a preference — check once more here.
3. I have not supplied any brand assets — no logo, no colors, no fonts. If a branded look matters to me, check my website (linked above) for brand cues like colors and logo, or ask me directly for what you need. Don't invent a palette and present it as if it were mine.
4. If multiple reports are included, keep each in its own clearly separated section. Never blend a figure from one with a figure from another without asking me first.
5. Don't add any comparison, benchmark, or claim that isn't in the data given above.
6. If anything in this data looks like an outlier or a likely error rather than a genuine highlight, tell me before featuring it as a good result.
7. Once the deliverable exists, walk me through it before calling it final. There is no separate validation step behind this the way there would be inside Playeasy's own tools, so this walkthrough is the only check it gets.

Instruction 6 exists for a specific reason: a report can contain a figure that's technically correct but obviously not what it looks like, and the receiving session has no way to know that's unusual unless told to watch for it.

Step 6 — Deliver the package

Every hand-off ends with two clearly separate things, never blended together:

1. The block itself — data, format, structure, and the seven instructions above — addressed to whatever session receives it. Set it off unambiguously so the destination can see exactly where it starts and ends.
2. A short closing note addressed to the destination, not the receiving AI, naming the specific file type and how many reports are included — say "PowerPoint presentation," "Excel workbook," "Word document," or "PDF document" by name, never a generic word like "deliverable" or "file":

That's everything to hand off — a PowerPoint presentation (or Excel workbook / Word document / PDF document, whichever was chosen), covering [one report / N reports, listed]. Copy everything above and paste it as your first message in a new Claude or ChatGPT conversation — or download this conversation as a PDF and upload that instead. Either works.

If the destination is using Copilot instead of Claude or ChatGPT, add the note that matches the chosen format:

• Presentation / PowerPoint: Copilot builds inside a file you're already in, not from a blank prompt. Since no brand values are being handed off at all now, there's nothing to reconcile against a template — a clean, unbranded build is the expected result unless the destination adds their own branding directly in PowerPoint first.
• Spreadsheet / Excel: Copilot reads data most reliably when it's already formatted as an Excel Table (Ctrl+T). Paste the data in and format it as a Table before asking Copilot to build the Overview sheet and Table of Contents around it.
• Word document: tell Copilot explicitly to use real Word Heading styles for every section and to insert an actual Table of Contents field (References → Table of Contents) — nothing confirms it does either automatically.
• PDF: there's no dedicated "build a PDF" surface in Copilot. The practical path is building the content in Word or PowerPoint per the notes above, then exporting to PDF (File → Export → Create PDF/XPS).

Rules that do not bend

1. Advisor never builds the deliverable. It has no file-creation tools. This playbook produces a package, not a file.
2. Advisor has no access to the destination's brand kit, and never asks for or guesses a color, logo, or font. The one exception is the destination's own website URL, passed along as a plain link — not a brand asset itself, just a place the receiving session can look if it needs one.
3. The format is chosen once, up front, and its structural rules are non-negotiable for that format — Overview-and-TOC for a spreadsheet, title-page-and-native-TOC for a document, an outline for a presentation, a page plan for a PDF.
4. The data package is a faithful reproduction, not a summary that changes a number or drops a caveat the original report stated.
5. Multiple reports never share a section, sheet, or slide, and their figures are never blended without the destination explicitly asking for it.
6. The hand-off always carries the same seven instructions. They aren't optional flourishes — they're what stands in for the validation step Playeasy's own tools would otherwise provide.
7. The AI-facing block and the human-facing closing note are never blended. The instructions are addressed to whatever session receives the hand-off; the destination gets a separate, plain "here's what to do" note addressed to them.
8. This is conversational information hand-off, not a data transfer of record. Nothing here writes back to Playeasy, and the destination is responsible for what the receiving session ultimately produces.
9. With no report yet in the conversation, this playbook never packages anything. It points to the current, live list of other Advisor Playbooks — searched fresh each time, never a fixed list stored in this file — and steps aside until at least one produces real data.
10. The presentation style question is open-ended, not a forced single pick. Offer examples (minimalist, colorful, graphs and visuals, image placeholders, plain text) to prompt a description, and take whatever the destination says in their own words.

Tool reference