Demo and facilitator scripts

Based on this meeting transcript of a product demo, produce a demo
script that another team member could use to run the same demo. The
script should encode what the demo presenter actually did — the
sequence of moves, the specific phrasings that landed, the questions
they asked, the transitions between sections.

Be faithful to the source session. Do not invent demo moves that
weren't shown. If something was improvised, mark it as
"Improvised — confirm if this should be standard."

Format:

# Demo Script: {Product / Feature / Use Case}
**Source session:** {Meeting name — date}
**Demo length (source):** {duration}
**Audience profile (from source):** {who was in the room, role, context}

## Demo overview
Two to three sentences on what this demo accomplishes. The single core
point this demo lands.

## Pre-demo setup
- [ ] Demo environment / sample data / accounts loaded
- [ ] Tabs / windows / contexts pre-arranged
- [ ] Materials at hand (one-pagers, pricing sheets, references)
- [ ] Customer context reviewed (notes from prior calls, CRM data)

## Opening (target: {N} minutes)
**Goal:** {what this segment accomplishes}
**Beats:**
1. {Opening beat — what to say or do}
   - Sample phrasing: "{verbatim from the source session if it landed}"
2. {Next beat}

**Facilitator note:** {anything important about how to do this segment}
**Transition into next section:** "{verbatim transition}"

## {Section name} (target: {N} minutes)
**Goal:** {what this segment accomplishes}
**Key point to land:** {the single most important takeaway}
**Beats:**
1. {Beat} — sample phrasing: "..."
2. {Beat}

**Questions to ask the audience:**
- {Question that was asked in source session}
- {Question that drew good engagement}

**If they ask...** (anticipated questions and responses)
- **Q:** "{question}" → **A:** "{answer}"
- **Q:** "{question}" → **A:** "{answer}"

**Compression option:** If running short on time, {what to cut and what
to preserve}

**Transition:** "{verbatim transition}"

[Repeat for each section]

## Closing (target: {N} minutes)
**Goal:** {Define next step; create commitment}
**Beats:**
1. {Beat}

**Asks of the audience:**
- {Specific commitment to seek}

## Common adjustments
- **For technical buyers:** {adjustments}
- **For executive buyers:** {adjustments}
- **For champions running internal demos:** {adjustments}

## Recovery moves
If you lose your place or the audience disengages:
- {Move the source presenter used}

## What NOT to do
Anti-patterns this demo deliberately avoids:
- {Anti-pattern} — why

Based on this meeting transcript of a workshop / training / research
session / retro, produce a facilitator guide that another person could
use to run the same session.

Be faithful to the source. Do not invent facilitation moves that
weren't used.

Format:

# Facilitator Guide: {Session name}
**Source session:** {Meeting name — date}
**Source facilitator:** {Name}
**Session length:** {duration}
**Audience type:** {who attends and why}
**Stated goal:** {what the session accomplishes}

## Pre-session setup
- [ ] Materials needed
- [ ] Room setup (or virtual setup — Miro board, breakout rooms)
- [ ] Pre-reads sent to participants
- [ ] Facilitator's own prep

## Session arc (overview)
1. {Phase 1} ({N} min)
2. {Phase 2} ({N} min)
3. {Phase 3} ({N} min)

## Phase 1: {Name} ({N} minutes)
**Purpose:** {what this phase accomplishes in the arc}

**Facilitator opens with:**
"{Verbatim or close paraphrase of the actual opening}"

**Activity / prompts:**
1. {Activity} — {N} minutes
   - What you say: "{specific phrasing}"
   - What the group does: {their activity}

**Facilitator moves to watch for:**
- {Move that worked — e.g., "When silence lasts more than 10 seconds,
  {source facilitator} reframes with..."}
- {Engagement-checking move}
- {How to handle the dominant voice}
- {How to draw out quiet participants}

**Transition into next phase:**
"{Phrasing the source facilitator used}"

[Repeat for each phase]

## Facilitator presence notes
How {source facilitator} showed up that's worth replicating:
- {Specific behavior — e.g., "Repeats participant statements back to
  confirm understanding before moving on"}

## Common failure modes and recovery
- **If the group goes off-topic:** {recovery move}
- **If energy drops in the middle:** {recovery move}
- **If one participant dominates:** {recovery move}
- **If you're running over time:** {what to cut, what to preserve}

## Closing
**The close (verbatim from source):** "{closing language}"

## What NOT to do
- {Anti-pattern}

## Materials and references
- {Link to slide deck, Miro template, doc template}
- {Link to source recording}

Based on this meeting transcript where someone is explaining or
demonstrating a process, produce a step-by-step process document. The
document should let someone unfamiliar with the process execute it
correctly.

Be faithful to what was shown. If the source person skipped a step
(because it was obvious to them) but the step is needed, flag it as
"Inferred — confirm with {source person}."

Format:

# Process: {Process name}
**Source:** {Meeting name — date}
**Process owner:** {Name}
**When to use:** {what triggers this process}
**Outcome:** {what this process produces when done correctly}
**Estimated time to complete:** {duration}

## Prerequisites
- [ ] Access to {systems, tools, accounts}
- [ ] Permissions: {list}
- [ ] Inputs: {what you should have in hand}

## Steps

### Step 1: {Verb-led step name}
**What to do:** {Specific action}

**How to do it:**
1. {Substep}
2. {Substep}

**Why this step matters:** {One sentence — gives the executor context
to do it intelligently rather than mechanically}

**Common mistakes at this step:**
- {Mistake} — {what happens if you make it}

**Output of this step:** {What you should have after completing}

### Step 2: {Step name}
[Same structure]

[Repeat for each step]

## Verification
How to confirm the process completed correctly:
- [ ] {Check}

## Recovery
If something goes wrong:
- **Symptom:** {problem} → **Action:** {how to recover}

## When NOT to use this process
Situations that look similar but require different handling:
- {Situation} → {use this other process instead}

Based on this meeting transcript (a prep session, a rehearsal, or a
source presentation by someone else), produce a prep document for the
upcoming event.

Format:

# Presentation: {Event name}
**Date:** {Event date}
**Audience:** {Who, size, context}
**Duration:** {target length}
**Source:** {Meeting name — date}

## The single message
The one thing the audience should remember if they remember nothing
else. One sentence.

## Audience analysis
- **What they know coming in:** {baseline}
- **What they care about:** {interests, motivations}
- **What they're skeptical of:** {pushbacks to anticipate}
- **What they want from this presentation:** {stated or implied}

## Presentation structure

### Opening (target: {N} minutes)
**Goal:** Hook + frame
**Sample opening:** "{one to three sentences}"

### Main arc

**Beat 1: {Title} (target: {N} minutes)**
- Point to land: {single point}
- Supporting material: {data, story, demo, quote}
- Sample phrasing: "{language that worked or fits}"

[Repeat for each beat]

### Closing (target: {N} minutes)
**Goal:** {Specific call to action or memorable close}
**Sample closing:** "{language}"

## Anticipated Q&A
- **Q:** "{question}" → **A:** "{response, anchored in your message}"

## What NOT to say
Topics to avoid, language that doesn't serve the message:
- {Item}

## Logistics
- [ ] Slides ready
- [ ] Demo working
- [ ] Backup plan if tech fails
- [ ] Time to review before going live
- [ ] Pre-event materials sent
- [ ] Post-event follow-up plan

## Rehearsal notes
If the source was a rehearsal, what to refine before the live event:
- {Refinement}