What problem does it solve? Company-run developer events (user conferences, community days, developer summits, roadshows) often launch without an agreed goal, a named budget owner, or any measurement plan, leaving organizers unable to justify the spend when finance or executives ask what the event returned. This Skill settles those three decisions before registration opens. ## Core Features & Use Cases - Goal-mix selection: Chooses among adoption-first, pipeline-first, blended adoption-and-pipeline, or ecosystem-goodwill postures using explicit promotion conditions, and deletes attendance count as a goal. - Budget-ownership modeling: Picks between marketing sole ownership, product or sales co-funding, or a multi-function committee with an executive sponsor, checking that each funder matches the chosen goal. - Measurement commitment: Requires four fields per goal (named metric, owner, source system, read date) written before registration opens, plus three pre-launch reviews covering legal terms, attendee-data privacy, and hosted-guest gifting rules. - Use Case: A CRO demands a sourced-pipeline number from a user conference whose room is 85% existing customers with no CRM join. The Skill rejects the pipeline goal on its failed conditions, recommends adoption-first, and writes the four-field measurement commitment. ## Quick Start Ask the assistant to help decide what your company-run developer conference is funded to accomplish, who should own the budget line, and what to measure before registration opens.
