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で見る