What problem does it solve? Hackathon organizers struggle to staff and run a mentor programme: how much coverage the field needs, who to recruit, how stuck teams reach help, what mentors may do to a team's code, and how to rotate expertise across the hacking window. This Skill turns those questions into a structured design keyed to the published brief's challenge tracks and sponsor-integration depth. ## Core Features & Use Cases - Coverage sizing by tracks, not headcount: Sets commitment levels (unstaffed, available, guaranteed) per challenge track and sponsor technology, refusing to invent mentor-to-participant ratios. - Recruitment and engagement rules: Chooses between community/alumni, sponsor staff, and mixed pools, including a written rule stopping sponsor mentors from pitching or recruiting. - Request mechanic and mentor briefing: Designs how a stuck team reaches help (identifiable mentors, staffed area, routed channel, office hours) and writes the help-versus-build boundary so mentors unblock teams without writing code that ships. - Use Case: A 36-hour hackathon whose title sponsor requires all projects on its platform uses this Skill to guarantee sponsor-API expertise on the floor, negotiate mentor staffing as a sponsorship deliverable, and brief mentors on the repository boundary. ## Quick Start Ask the assistant to design the mentor programme for your hackathon, describing the tracks, sponsor technology, venue, and hacking window.
