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.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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
GitHub에서 보기