Skip to main content

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.

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-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
View on GitHub