event-schedule-designlisted

Lay a technical event's already-selected talks into a published session grid - session-length standardization, room and capacity matching, the four clash types with multi-speaker intersection, break and lunch placement, buffer sizing, keynote and plenary placement as re-sync points, synchronized versus staggered track starts, energy-curve pacing, and speaker travel windows against slot assignment. Use whenever the user mentions building a conference schedule or agenda, a multi-track layout, session clashes or speaker double-booking, matching talks to rooms, sizing breaks, or when to publish the grid - even if they never say "schedule". Do NOT use to decide the track count or session-format mix - use samber/dev-event-organizer-skills@event-format-selection instead.
samber/dev-event-organizer-skills · ★ 2 · Web & Frontend · score 76

Install: claude install-skill samber/dev-event-organizer-skills

# Event Schedule Design You lay already-selected sessions into a physical grid: which talk runs at which time, in which room, with what between them. Your inputs arrive decided, fixed by these sources: - **Track count, event shape, session-format mix, delivery mode** - `samber/dev-event-organizer-skills@event-format-selection`, which states the split from its own side: "You do not build the schedule - grid layout, clash avoidance, and room-capacity matching belong to `samber/dev-event-organizer-skills@event-schedule-design`. Single vs multi-track is decided here, because it follows from size, audience, and content-mix strategy; placing sessions into that structure is decided there." - **Accepted talks, with format and track tags** - `samber/dev-event-organizer-skills@event-talk-selection`. - **Speaker travel and availability windows** - `samber/dev-event-organizer-skills@event-speaker-experience`, which collects them; this skill binds them to a slot. You stop at the published grid. How staff execute it minute by minute on the day, and how they respond live to a no-show or an AV failure, is `samber/dev-event-organizer-skills@event-run-of-show`. Every ranking below is a default, not a law - it shifts with context and with who executes it. After the interview, re-rank all three menus against what you know about this event: - A venue whose rooms open onto one narrow corridor. - A scheduling tool already in use that computes clashes for free. - A returning audience that told