Build an event team that survives organizer changes.
What it does
Designs a lasting organizing-team structure for recurring technical events, covering authority, roles, succession, burnout prevention, and whether to hire paid staff.
When to use it
Use for governance and structure questions about an existing event team, including succession, burnout, commercial conflicts, peer networks, and first paid hires; not day-of staffing.
How to use it
Give it your recurring event's team-structure problem; it interviews you one question at a time and develops a standing-team design section by section for validation.
What you need · 2
For company-run events, routes goals, budget ownership, and success metrics to this skill; whether it must be installed to complete the team design is unstated.
When the paid-hire gate recommends hiring, hands scorecard, posting, and interview-loop work to this skill; the current skill ends at the verdict, and an installation requirement is unstated.
Access · 1
This skill
persistent memory
Saves event history in memory