What problem does it solve? Event organizers often launch a podcast or YouTube channel without deciding who owns it between editions, where guests come from, or what happens when an organizer leaves, so the show quietly dies in public. This Skill turns that into a deliberate decision: whether to run a channel at all, what cadence the team can actually keep, and how the property survives staff changes. ## Core Features & Use Cases - Existence posture menu: Choose between no channel, an archive-only feed, a low-cadence original show, or a heavy-cadence show, with named owners and explicit promotion and deletion conditions for each rung. - Guest sourcing pipeline: Scope guest sourcing from the speaker pool outward, with a written vetting bar and a strict separation between stage recording consent and episode-specific releases. - Feed relationship and handover: Write the two-direction feed map between the event cycle and the channel, plus a dated handover document covering accounts, back-catalogue, and release-record custody. - Use Case: A volunteer conference team voted to launch a fortnightly podcast but nobody owns the quiet months; the Skill recommends declining or going archive-only, deletes the unowned cadence options, and records the decision with a reopening condition. ## Quick Start Ask the assistant to help you decide whether your conference should run a standing podcast or YouTube channel and to draft the cadence commitment, guest pipeline, and handover plan.
