What problem does it solve? Launching a brand-new tech event with no track record invites two failure modes: over-scoping edition one into an unmanageable production, or under-scoping it into an unconvincing one. This Skill takes an organizing team from "we decided to do this" to doors open with a right-sized scope, a viable founding team, a realistic timeline, and pre-planned circuit breakers. ## Core Features & Use Cases - Scope tier selection: Chooses between a single-focus standalone edition, a borrowed edition inside existing infrastructure, or a full-footprint edition, with written no-gos that stop mid-planning scope creep. - Team gate and formation: Enforces the floor of three organizers from three organizations before venue or date is locked, and scales delegation from a 3-person core to a 9-role team. - Reverse timelines and compression levers: Applies the sourced ~12-month conference or 4-9-month hackathon timeline, with levers like borrowed venues and invited-speaker programs when the deadline is shorter than the runway. - First-edition pre-mortem: Categorizes risks as Tigers, Paper Tigers, and Elephants with named owners, decision dates, and go/no-go dates wired to Good/Better/Best budget-tier downgrades. - Use Case: Three meetup organizers want to turn their 250-person monthly meetup into a one-day conference in eight months. The Skill validates demand evidence, sets appetite and no-gos, confirms the team gate, builds the reverse timeline, and delivers a launch brief section by section. ## Quick Start Ask the assistant to build a launch plan for the first edition of your conference or hackathon, including your team size, available hours, deadline, and any demand evidence you have collected.
