90-Second Demo and Loom Script

What it does

/demo-script is a Cursor slash command. Type it in chat to run a saved workflow: 90-Second Demo and Loom Script.

Writes what you say on camera. You still record. No fake view counts.

Spoken script, shot list, three titles. Unlike a skill, a command is something you invoke on purpose. The agent does not decide to run /demo-script for you.

Why it exists

Founders retype the same multi-step prompt until it rots. /demo-script exists so the pipeline, all 4 steps of it, is a file in .cursor/commands, versioned with the repo.

It ships in the Marketing Kit. It is wired to the Demo & Video Producer (video-producer) and Product Marketing (Every Ship) (product-marketer) agents. Required skills: Product Demo & Loom Scripts; Eugene Schwartz 5 Stages of Customer Awareness.

When to use it

• Use before recording a product demo, Loom, or YouTube walkthrough.
• Use /demo-script when you want that pipeline, not a freeform chat. If you only need one step, use a narrower command or a single agent.
• Start a new chat. Do not run this command in a thread that just touched production SQL.

When not to use it

• Do not run /demo-script as a substitute for reading the diff. The command produces files; you still gate them.
• Do not chain it into a 40-turn chat. Fresh context is part of the design.
• Do not run it if you have not filled CURSOR.md. The pipeline will invent a stack.

Example workflow

1. video-producer sets audience and awareness level
2. Write spoken script + shot list
3. Three titles and on-screen text
4. Auto-save docs/marketing/demo-script.md

Example usage

Type this in Cursor chat: /demo-script 90s demo of /ship for solo founders, plus Loom outline

The command file tells the session which agents to adopt and which skills to read. You should see phase headers, not a single dump of code.

If a phase fails its gate, stop. Do not add 'just continue'.

Example output

• Expected artifact: docs/marketing/demo-script.md

Best practices

• Keep the prompt specific. /demo-script 90s demo of /ship for solo founders, plus Loom outline is the shape: object, constraint, and outcome.
• Let the listed agents work in order: video-producer → product-marketer.
• Save outputs in the repo. Chat-only answers evaporate.
• Marketing commands write to docs/marketing/ so the next command can read positioning before it writes a landing page.

Common mistakes

• Typing /demo-script with no object ('do the thing'). The pipeline will guess.
• Re-running the command in the same chat after a failed gate instead of fixing the failing file.
• Editing the command file to skip review so it 'goes faster'.
• Skipping the Product Demo & Loom Scripts skill that the command depends on.