Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Cinematic narration style guide for demo-conductor — ANSI-coloured banner formats, live pipeline scoreboard, audience-facing language, phase summaries, and error narration patterns. Keeps the demo presentation-quality throughout.
user-invocable
false
Demo Narration
Core Principle
Every phase transition is a story beat. The audience is watching live. Make it engaging, honest, and clear. Never expose raw error stack traces or agent-internal state. Narrate like you're presenting to stakeholders.
Use ANSI colour codes in all banners. The live agent ticker hook handles individual dispatch/return events — conductor handles phase-level narration.
ANSI Colour Reference
Use these escape sequences in all output blocks. Wrap in \x1b[0m (reset) after every coloured segment.
Purpose
Code
Label
Phase headers
\x1b[96m
bright cyan
Opus tier indicator
\x1b[31m
red
Sonnet tier
\x1b[33m
yellow
Haiku tier
\x1b[32m
green
Success / done
\x1b[92m
bright green
Warning / concerns
\x1b[93m
bright yellow
Error / blocked
\x1b[91m
bright red
Box borders
\x1b[36m
cyan
Dim labels
\x1b[2m
dim
Bold
\x1b[1m
bold
Reset
\x1b[0m
reset
When NO_COLOR env var is set, emit plain text only (no escape codes).
Opening Banner
The demo-opening.js SessionStart hook emits this automatically. demo-conductor does NOT reprint it. Instead, print the interactive prompt immediately:
\x1b[96m┌─────────────────────────────────────────────────────────────────────┐\x1b[0m
\x1b[96m│\x1b[0m \x1b[1mTell me what you want to build.\x1b[0m \x1b[96m│\x1b[0m
\x1b[96m│\x1b[0m \x1b[2mExample: "a CLI task manager in Python"\x1b[0m \x1b[96m│\x1b[0m
\x1b[96m└─────────────────────────────────────────────────────────────────────┘\x1b[0m
Pipeline Scoreboard
Print the scoreboard before each phase banner. It tracks all 7 autonomous phases (spec interview is pre-pipeline) — audiences can see exactly where the pipeline is at a glance.
Status icons:
\x1b[92m✓\x1b[0m — complete
\x1b[96m⚡\x1b[0m — active (current phase, blinking feel)
\x1b[93m⟳\x1b[0m — skipped
\x1b[2m·\x1b[0m — pending
Format (substitute {icon_N} for each phase's current icon):
\x1b[93m⚠\x1b[0m \x1b[1m{PHASE TITLE}\x1b[0m — applying recovery strategy
\x1b[2mIssue: {plain-language description — no raw error text}\x1b[0m
\x1b[2mRecovery: {what demo-conductor is trying next}\x1b[0m
After successful recovery:
\x1b[96m↻\x1b[0m \x1b[1m{PHASE TITLE}\x1b[0m — recovered with reduced scope, continuing...
When phase is skipped after recovery failure:
\x1b[93m⟳\x1b[0m \x1b[1m{PHASE TITLE}\x1b[0m skipped
\x1b[2m{brief explanation — what was skipped and why it doesn't block the remaining phases}\x1b[0m
Completion Banner
Print after Phase 7 completes. Substitute {workspace} with the resolved absolute $DEMO_WORKSPACE:
