What problem does it solve? A 71-skill event-organizing collection is too large for any single skill to see the others, so organizers cannot know which skill fits their task or whether one exists at all. This Skill acts as the entry point and router: it detects project state, interviews the organizer within a strict question cap, routes the task to exactly one sibling skill or names the gap, and maintains a shared context artifact so every later session starts warm. ## Core Features & Use Cases - Detection-first cold and warm starts: Decides cold versus warm start from the presence of an event-context.md artifact, reads git history and existing files (budgets, grids, contracts) to answer questions before asking them, and caps cold-start interviews at 5-7 multiple-choice questions. - Gated routing tables: Routes to exactly one of 71 skills using format gates (hackathon, virtual, hybrid, in-room, conference, workshop), lifecycle gates (first, recurring, properties), and a company gate, with boundary-pair rules for colliding skills. - Ranked output and context artifact: Delivers a route, a 5-8 skill short-list ordered by value per unit of effort, dependency-ordered chains, a not-now list with unblocking conditions, and gap statements, while writing a versioned event-context.md that makes the next session a warm start. - Use Case: An organizer says their company approved a budget for a possible hackathon but nothing exists yet. The Skill detects a cold start, asks only what the message did not answer, routes to an existence-check skill rather than logistics skills, and records the session in the context artifact. ## Quick Start Start a new event-organizing session by describing your event and goal, and ask the kickoff router which skill in the collection you should use first.
