Skip to main content

plan-event-production

Design the technical systems, crew, cues, handoffs, and recovery needed to deliver an event. Use when audio, video, lighting, staging, streaming, recording, or presentation systems must work together.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
plan-event-production
category
media
description
Design the technical systems, crew, cues, handoffs, and recovery needed to deliver an event. Use when audio, video, lighting, staging, streaming, recording, or presentation systems must work together.
# plan-event-production ## Procedure 1. Confirm venue, program, formats, audiences, access, recording, stream, budget, and operating hours. 2. Translate sessions into signal, equipment, power, network, stage, scenic, lighting, playback, caption, and communication needs. 3. Draw system and signal-flow diagrams with primary, backup, ownership, and critical dependencies. 4. Build equipment, crew, content, credential, frequency, bandwidth, and venue-interface schedules. 5. Define file delivery, naming, versioning, playback, presentation, media, and backup standards. 6. Plan load-in, testing, rehearsal, show call, fault isolation, change control, and load-out. 7. Test power loss, network loss, device failure, speaker absence, caption failure, and stream interruption. 8. Record acceptance, unresolved limitations, recovery authority, and live contacts. ## Guardrails - Do not bypass electrical, rigging, fire, venue, radio, or occupational safety authority. - Never assume venue internet or supplier redundancy without a load and failure test. - Protect credentials, unpublished content, personal data, and licensed media. ## Done - A production plan contains system diagrams, equipment, crew, cue, content, and schedule records - Rehearsal and failure tests prove primary and fallback paths for critical systems - Venue, access, production, and recovery acceptance is recorded
View on GitHub