What problem does it solve? Organizers of meetups, conferences, and hackathons face structural decisions - single-track versus multi-track, in-person versus hybrid, which session formats fill the day - that are expensive to reverse and easy to get wrong by copying other events or following rules of thumb. This Skill turns those choices into evidence-backed decisions with published triggers and named precedents. ## Core Features & Use Cases - Event-shape ladder: Graduates a recurring meetup toward an unconference day, hackathon, single-day, or multi-day conference based on content depth and risk tolerance, never headcount alone. - Track count and session mix: Decides single-track versus multi-track using the published 8-10x CFP oversubscription trigger, and composes the day from curated talks, ignite blocks, open space, fireside chats, and bracketed workshop days. - Delivery mode and hackathon judging: Weighs in-person, virtual, and hybrid delivery against published cost evidence (CHI's hybrid finances, MLH's anti-hybrid position), and picks hackathon demo structures from expo tables to two-stage finals. - Use Case: A meetup drawing 130 people monthly asks whether to launch a two-day conference. The Skill interviews the organizers, rejects the headcount rule of thumb, and recommends a single-day single-track conference with the graduation evidence and revision triggers written down. ## Quick Start Ask the assistant to help decide what format your developer event should take, for example whether your meetup should become a conference or whether to add a second track.
