Builds a product demo script around the buyer's discovered pain – a 60-second situation recap opening, three to four before/after "moments" mapped to the buyer's metric, and a close that ends before the slot does.
Builds a product demo script around the buyer's discovered pain - a 60-second situation recap opening, three to four before/after "moments" mapped to the buyer's metric, and a close that ends before the slot does. Use when someone asks "help me script this demo", "how should I structure tomorrow's product walkthrough", "turn these discovery notes into a demo plan", or before any live or recorded demo. Do NOT use for staging and directing the demo environment, data, and rehearsal - use product-demo-director instead. Do NOT use when discovery hasn't happened yet - run discovery-call-prep first, because a demo without known pain is a feature tour.This is the skill's description: the text your AI reads to decide when the skill applies.
demo-script/SKILL.md
---
name: Demo Script
description: Builds a product demo script around the buyer's discovered pain - a 60-second situation recap opening, three to four before/after "moments" mapped to the buyer's metric, and a close that ends before the slot does. Use when someone asks "help me script this demo", "how should I structure tomorrow's product walkthrough", "turn these discovery notes into a demo plan", or before any live or recorded demo. Do NOT use for staging and directing the demo environment, data, and rehearsal - use product-demo-director instead. Do NOT use when discovery hasn't happened yet - run discovery-call-prep first, because a demo without known pain is a feature tour.
---
# Demo Script
A feature tour is not a demo. Buyers do not care about features - they care about outcomes, and the job of a demo is to make the buyer see themselves solving a specific problem they described in discovery. The costly failure this skill prevents is the tour that fills the whole slot, impresses the presenter, and leaves the buyer with no reason to take a next step.
## Operating procedure
The order is fixed: inputs gate everything (no discovery, no demo), moments are selected before the open is written (the recap promises what the moments deliver), and pacing is set last.
### Step 1: Gather inputs - the three-fact gate
Pull the discovery notes and extract:
1. The primary pain the buyer named, in their words.
2. The current workaround they use today.
3. The metric or outcome they care about improving.
Also collect: who is attending (roles), slot length (default 30 minutes), and whether the demo is live or recorded. If any of the three facts is missing, the demo should not happen yet - run discovery-call-prep first. If a fact is inferred rather than heard, label it a guess and open the demo by confirming it.
### Step 2: Select three to four moments
… load the full skill through Skill MeClick to play with sound.