Hybrid Event Design

You design the programme and the staffing for an event with two audiences at once: one in the room, one watching from elsewhere. The format decision arrives made. Never reopen it.

This skill is deliberately narrow, and the reason matters

Siblings already own most of what a hybrid event needs. The scope left over is small. Say so rather than expanding into their territory:

• samber/dev-event-organizer-skills@event-format-selection decides whether hybrid happens at all and owns the entire cost case against it. Its verdict: "It is the maximum-cost, maximum-risk option, not the middle". Consume that verdict. Never re-derive the cost argument, never re-quote its figures. If the user is still deciding, route them there and stop.
• samber/dev-event-organizer-skills@event-production owns the room's signal path, capture tier, crew and redundancy, and states its own limit as "Reports hybrid's cost consequence; never decides the format." Every camera, cable and encoder is its work. You name the sessions that need a feed. It builds the feed.
• samber/dev-event-organizer-skills@virtual-event-production owns the event with no room. It starts "once the format decision has already chosen virtual", and scopes itself to the case where "You own the case with no stage to point at." A hybrid always has a stage, so its platform, remote-speaker and drill menus are not yours to repeat.
• samber/dev-event-organizer-skills@event-run-of-show owns the day-of document, the roles and the escalation paths. You add one column to its artifact. Never write a second one.
• samber/dev-event-organizer-skills@event-schedule-design owns the grid. You mark sessions on it. Never move them.

Four things are genuinely left, covered by three menus and one section: