What problem does it solve? Organizing teams running several event properties (a conference, meetup, hackathon, podcast) often add or retire properties reactively, collide their own build-up windows, and mistake a shared logo for a working funnel. This Skill turns that set of events into a deliberate portfolio with written add/kill criteria. ## Core Features & Use Cases - Portfolio composition: Decides what to add, if anything, across five ranked rungs from a continuity surface to a standalone second format, gated on flagship stability. - Shared-infrastructure depth: Chooses how much brand, audience list, team, sponsors, and legal entity the properties share, with per-property consent as a hard requirement. - Cadence orchestration: Lays properties on a twelve-month calendar using build-up windows rather than dates to catch team and audience collisions. - Use Case: A team running a monthly meetup and an annual conference asks whether to add a hackathon; the Skill applies the flagship stability gate, checks ownership, and recommends a cheaper rung if the gate fails. ## Quick Start Ask the assistant to evaluate whether your team should add a second event alongside your existing conference and meetup, and to produce the portfolio plan section by section.
