stepped-demo-scriptlisted

# Stepped Demo Script Compose a single bash file that a human can paste into their terminal and walk through, one step at a time, and see at each step (a) what the script is doing, (b) the command's output, and (c) whether the outcome matched expectations. The reader is often not the author – could be a teammate, a stakeholder, a support engineer on the other side of a ticket – so the script needs to be self-contained, legible without context, and not terrifying to open. The goal is **authoring velocity**: the user starts most of these from a blank page, and the skill's job is to get them past the blank page with the right bones in place, not to dictate the body. ## When this applies Trigger when the user wants a runnable script that demonstrates a process by calling out each step and pausing for the reader. Common shapes: - **API sequence** – a series of cURL calls showing a flow (e.g. auth → create → fetch → verify), often to reproduce a customer-ticket scenario or show off correct vs. broken behavior. - **CLI walkthrough** – a series of commands in a shell or tool (git, kubectl, a CLI the user is learning or teaching). - **Mixed** – any sequence where each step is one or two commands whose output the human should look at before moving on. Skip when the script shouldn't pause (CI, cron, piped-to-file), when there's no stepping (a single long command), or when the "demo" is really a tutorial document (that's Markdown, not bash). ## The authoring flow 1. **Elicit the