demo

Files (1)

• SKILL.md

SKILL.md (first lines)

# demo

Produce a watchable proof: drive a real feature on the real app and record it. A demo is
[prove-it-works](../prove-it-works/SKILL.md) made visible — the recording exercises the
actual user path, never a staged or mocked one.

## Process

1. **Reuse the verify machinery.** The repo's `verify-<app>` skill (from
   [verify-setup](../verify-setup/SKILL.md)) owns Launch, Doctor, and Drive; a demo is a
   Drive with recording on. No verify skill in the repo: offer to run verify-setup
   first — it's the same work minus the recording, and the repo keeps the skill.
2. **Pick the recording medium by surface:**
   - Web/desktop UI: screen or tab recording via the browser/driver tooling (video or
     GIF). Capture the interaction, not a slideshow of end states.
   - CLI/TUI: a terminal recording or transcript with the invocations and their real
     output, trimmed to the signal.
   - API/service: a narrated request/response sequence — the commands run and the
     actual responses, plus the observable side effect (row inserted, file written).
3. **Script the walkthrough before recording:** the feature's map file (features/) names
   the entry path and the observable end state; the demo follows the map, start to
   proven end state, including the side-effect check. One take that shows the whole
   path beats three fragments.
4. **Run it**: doctor first, drive with recording on, stop at the proven end state,
   cleanup per the verify skill — the recording is evidence and survives cleanup, saved
   to a named location.
5. **Deliver**: hand over the file with one line per step of what it shows. Working a
   bd ticket: attach the demo location to the ticket's evidence note.

From baranbingol1/bbstack, MIT.

More from baranbingol1/bbstack