What problem does it solve? Event organizers struggle to decide which communication channels to open, where each class of message should be announced, how multiple volunteer writers stay consistent, and what to do with channels after the event ends. This Skill produces a complete channel architecture so announcements actually reach attendees and no channel is left unmoderated. ## Core Features & Use Cases - Channel Roster Design: Ranks announcement lists, chat spaces, status pages, and event apps on reach, speed, effort, and efficiency, with explicit promotion and deletion conditions for each rung. - Message-Class Routing: Builds a routing rule from a nine-class message taxonomy (disruption, live change, day logistics, and more) with optional escalation tiers, so volunteer writers route messages correctly on the first try. - Multi-Writer Consistency: Scales from a shared quick-reference to a pre-written message bank with timestamped day scripts, executing a fixed register without editorial bottlenecks. - Wind-Down Planning: Chooses between read-only archive, export plus scheduled deletion, and community hand-off, with per-rung checklists and a counsel review list. - Use Case: A 500-person two-track conference asks whether to buy an event app; the Skill rejects it on reach and effort grounds, keeps the email list as the floor channel, and defines routing and wind-down before any channel is created. ## Quick Start Ask the Skill to design the attendee communication channels for your event, describing its size, duration, number of writers, and any channels that already exist.
