| name | mushanghai-track-leader |
| description | muShanghai Track Leader operations skill. Use when a Track Leader needs to: (1) define track scope + core questions, (2) lock the track's tech stack (wearables, logging tools), (3) do on-the-spot BioBloom pitch triage at Recruitment Night (May 17), (4) run daily 🟢🟡🔴 traffic-light check-ins during the run window, (5) synthesize the track at end-of-cycle. Routes between five modes. |
| when_to_use | Trigger phrases: 'as a Track Leader', 'TL scope brief', 'BioBloom pitch triage', 'pitch triage', 'traffic light check', '🟢🟡🔴', 'track synthesis', 'Recruitment Night', 'mid-experiment status', 'tech stack decision', 'good night hackers communication'. |
| allowed-tools | Read Write |
muShanghai Track Leader
Valid for: May 2026 cycle. Refresh track leads and dates before later reuse.
Prerequisite: Read ../mushanghai-canon/references/safety.md, ../mushanghai-canon/references/three-tracks.md, ../mushanghai-canon/references/may-2026-calendar.md, and ../mushanghai-canon/references/four-musts.md before responding to the user.
Always: show canon safety banner first
Mode router
Ask the user:
Which Track Leader workflow?
(A) Define track scope + core questions (before May 12)
(B) Lock the track tech stack (before May 12)
(C) On-the-spot BioBloom pitch triage (at May 17 Recruitment Night)
(D) Daily 🟢🟡🔴 traffic-light check-in (May 19+)
(E) End-of-track synthesis (June 5)
Mode A — Track Scope Brief
Goal: produce a 1-page brief ELs read before the Experiment Jam.
Walk through:
- Track name + lead
- 2–4 core questions
- What's in scope
- What's out of scope
- What success looks like for this track
Output to assets/track-scope-brief.md filled in.
Mode B — Tech Stack Decision
Walk through:
- Which wearables this track will accept (Oura, Apple Watch, RingConn, CGM, etc.)
- Daily log format (template link)
- Data export format (CSV, JSON, raw export)
- Where data is stored
Output to assets/track-scope-brief.md section "Tech Stack."
Mode C — BioBloom Pitch Triage
Load references/biobloom-pitch-triage.md. Use the 5-question rubric in assets/pitch-triage-rubric.md. Goal: give an in-scope / out-of-scope / reshape verdict in ≤ 2 minutes per pitch.
Also load references/good-night-hackers-tl.md so the TL knows the exact language to use about the dual-enrollment option.
Mode D — Daily Traffic-Light Check-in
Load assets/traffic-light-check.md. For each experiment in the track, output a 1-line status.
Mode E — End-of-Track Synthesis
Load assets/track-synthesis.md. Aggregate final reports across the track's experiments.
References
Assets
