| name | mushanghai-demo-prep |
| description | muShanghai Demo Day preparation skill for Experiment Leaders preparing a 5-minute presentation for BioBloom Demo Day May 22 at OpenFlow Bazaar or Longevity Month Demo Day June 5. Use when shaping a demo narrative, backup plan, visual anchor, and rehearsal checklist. |
| when_to_use | Trigger phrases: 'prep my demo', '5-minute demo', 'demo day prep', 'plan B for demo', 'rehearse my demo', 'OpenFlow Bazaar demo', 'June 5 demo'. Do not trigger for proposal drafting or daily logging — use mushanghai-experiment-leader or mushanghai-participant-log instead. |
| allowed-tools | Read Write |
muShanghai Demo Prep
Valid for: May 2026 cycle. Use for BioBloom Demo Day on May 22 at OpenFlow Bazaar and Longevity Month Demo Day on June 5.
Prerequisite: Before doing anything else, read ../mushanghai-canon/references/safety.md and ../mushanghai-canon/references/four-musts.md. If they conflict with the repo role files, the role files win.
Always: show the canon safety banner first
Before any other content or question, surface this banner:
Before we start, do NOT paste:
- Identifiable health data (HRV with timestamps + location, blood labs, body weight, sleep records)
- Real names of other participants
- Other people's data without their explicit consent
- Details of medical conditions, pregnancy, or current medication
muShanghai skills help you plan, log, and reflect. They do not provide medical advice. All experiments are for education, exploration, and self-observation only - not diagnosis or treatment. High-risk interventions (anything beyond lifestyle, breath, movement, or off-the-shelf wearables) require Track Leader approval AND escalation to the Month organizer.
If the user pasted anything from the never-paste list, stop and ask them to redact before continuing.
Single-mode walkthrough
Goal: prepare a tight, reproducible 5-minute Demo Day presentation and write it to experiments/<track>/<seed-name>-demo.md.
First collect: experiment name, track, cohort, Experiment Leader display name, seed name, demo date, and source data or artifact links. Then show the proposed output path and filled content for confirmation before writing.
Use assets/demo-outline.md as the output template. Walk the user through exactly these steps:
- Restate Four Musts - restate Problem / Monitoring (or Observation) / Intervention (or Interaction for Proof of Living) / Deliverables, in that order. Keep each restatement one or two sentences and flag any vague item before continuing.
- Anchor visual or artifact - pick exactly one anchor from: chart, photo, video clip, prototype, dataset screenshot. Explain why that anchor proves the demo is about an observed experiment, not a generic idea.
- 5-minute structure - draft problem -> approach -> what we built -> validation -> reproduction. Suggest a minute budget per beat that totals no more than 5 minutes.
- Plan B for live failures - specify what the EL shows if a live demo crashes, data import fails, or a participant drops. Plan B must still show Problem, signal, action, and deliverable.
- Rehearsal checklist - load
assets/rehearsal-checklist.md and walk every item. Do not mark an item ready unless the user confirms it.
After step 5, present the complete markdown draft and ask: "Write this to experiments/<track>/<seed-name>-demo.md?" Write only after confirmation.
Output rules
- Write English-only markdown.
- Preserve bracketed placeholders only when the user has not provided the answer.
- Do not invent data, participant counts, outcomes, source files, or missing observations.
- Keep health data aggregated or de-identified.
- If the demo is for Proof of Living, use "Interaction" in Must #3 and restate the four required hashtags and platform handles per
../mushanghai-canon/references/proof-of-living.md.
References
../mushanghai-canon/references/safety.md../mushanghai-canon/references/four-musts.md../mushanghai-canon/references/may-2026-calendar.md../mushanghai-canon/references/two-cohorts.md../mushanghai-canon/references/proof-of-living.md
Assets
