What problem does it solve? Technical events blur together when organizers skip positioning: teams describe the event inconsistently, sponsors mislabel it, and differentiation claims rest on guesses instead of evidence. This Skill structures the strategic decisions - governance, alternatives, audience, category, and statement - before any tagline or marketing copy is written. ## Core Features & Use Cases - Governance-spectrum placement: Classify the event as community-run, foundation-run, media-run, or vendor-owned, and enforce honesty rules such as the ~30-40% single-vendor content threshold that forfeits a neutrality claim. - Competitive-alternatives mapping: Map all five alternative types (direct rivals, adjacent events, eventless options, delegation, doing nothing) per segment using a 15-20 interview script with repeat attendees and sponsors. - Category strategy and levers: Choose between subcategory, head-to-head, and new-category frames with ranked effort/value/efficiency trade-offs, then invest via contrast sentences, track-structure declarations, lineup-as-brand, or a gated rebrand. - Use Case: A vendor's user conference wants to market itself as "vendor-neutral" while 73% of sessions are product content. The Skill refuses the claim, offers rebalance-or-drop remedies, and produces an honest vendor-pole positioning statement with 2-3 candidates. ## Quick Start Ask the assistant to position your conference, meetup, or hackathon - for example, "Help me position our new platform-engineering conference against the two cloud events already running in our city."
