Event Team Structure

samber/dev-event-organizer-skills/skills/event-team-structure

by samberaf0a7c0dcec0MIT3 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 10 days ago

Design the standing organizing team of a recurring technical event - the structure that persists between editions. Covers legal-entity posture (none, fiscal sponsorship, own non-profit), decision-rights shape (board-plus-organizers split, domain-lead federation, consensus committee), the role taxonomy, succession and bus-factor planning, burnout guardrails, and the volunteer-to-paid-staff hiring gate. Use whenever the user mentions structuring or governing an organizing team, forming an association or non-profit for an event, splitting decision rights, organizer succession or rotation, organizer burnout, or hiring the first paid staff - even if they never say "team structure". Do NOT use for day-of staffing - use samber/dev-event-organizer-skills@event-volunteers instead.

Instructions onlyBusiness & Finance
  1. af0a7c0dcec0Currentcommit af0a7c0Published Oct 9, 2026

Source and attribution

Source:samber/dev-event-organizer-skillsinskills/event-team-structureat commitaf0a7c0

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal