# Demo Script

> Write a short, natural, spoken demo script for a product or feature that explains what changed, shows it working, and ties it to business value. Use for demo scripts, sprint demos, feature walkthroughs, show-and-tell, or explaining a change to stakeholders.

- Skill: `christopheralphonse/demo-script` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx get-skill add christopheralphonse/demo-script`
- Raw SKILL.md: https://api.skillmd.com/api/skills/christopheralphonse/demo-script/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ChristopherAlphonse (https://skillmd.com/u/christopheralphonse)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/christopheralphonse/demo-script

---


# Demo Script

Write a short script someone can say out loud to explain what was built, show it, and say why it matters to the business. The point is the "why it matters", not a feature tour.

## Guardrails

- Do not invent facts, metrics, percentages, savings, or performance gains. If a number is missing, describe the benefit in plain terms or ask for the real figure.
- Do not assume the audience. If it has not been stated, ask. Audiences: engineers, technical leaders, executives, product managers, business stakeholders, customers, or mixed. Set the technical depth and business emphasis from it.
- Do not assume the "before". If you cannot tell how the process worked previously, ask.

## Steps

Read the reference for each step when you reach it. Do not load them all up front.

| Step                        | What you do                                                                | Read                      |
| --------------------------- | -------------------------------------------------------------------------- | ------------------------- |
| 1. Discover                 | Read docs, repo, PR, ticket and notes. Ask only for what is missing. | `references/discovery.md` |
| 2. Find the business reason | Pick the one or two outcomes that are true here.                           | `references/discovery.md` |
| 3. Write                    | Previously, Now, Demonstration, Result, Business impact. Spoken style.     | `references/script.md`    |
| 4. Check                    | Read it aloud in your head, then cut.                                      | `references/script.md`    |

For a sample of the finished tone, read `references/example.md`.

## Output

Deliver these parts:

- **Feature overview:** two or three sentences on what the feature does.
- **Demo script:** the spoken script in the structure above.
- **Business value:** the problem addressed and the value created.
- **Metrics:** real measurements if provided (time saved per task, manual steps removed, processing time, cost, errors). If none exist, name which measurements would quantify the impact.
- **Output location:** where to output the script (for example, a shared doc, wiki page, or Markdown file).

