plan-an-event-program
Shape sessions, formats, pacing, and transitions around audience needs and intended outcomes. Use when an event brief must become a coherent participant program.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- plan-an-event-program
- category
- start
- description
- Shape sessions, formats, pacing, and transitions around audience needs and intended outcomes. Use when an event brief must become a coherent participant program.
# plan-an-event-program
## Procedure
1. Translate each event outcome into participant questions, decisions, practices, or connections.
2. Segment the audience by knowledge, access, language, time zone, and participation needs.
3. Choose session formats based on the outcome rather than speaker availability alone.
4. Sequence orientation, learning, discussion, practice, breaks, transitions, and closing.
5. Balance perspectives and avoid overlapping sessions that force the same audience to choose.
6. Include access, caption, interpretation, quiet-space, movement, networking, and remote-participation needs.
7. Test capacity, timing, room, production, staffing, speaker, and cost dependencies.
8. Review the draft with representative participants and delivery owners.
## Guardrails
- Do not fill the program with unconfirmed speakers or duplicate promotional sessions.
- Never schedule in a way that removes necessary breaks, access, safety, or transition time.
- Keep selection criteria and conflicts visible when allocating scarce program space.
## Done
- A program plan links every session and format to an audience outcome
- Timing, access, capacity, dependencies, speakers, and fallback evidence are reconciled
- Participant and delivery-owner review is recorded
GitHubで見る