What problem does it solve? Hackathon organizers must decide how participants end up on teams: the published team-size rule, the day-of matchmaking mechanic, what happens to participants nobody picks, and when rosters freeze. This Skill turns those decisions into a structured, interview-driven process with explicit trade-offs instead of ad-hoc improvisation. ## Core Features & Use Cases - Team-size and composition rules: Decide the size range, whether solo entry is allowed, and any track-conditioned composition fraction, with guidance on protected-characteristic carve-outs. - Matchmaking mechanic selection: Choose among pitch-and-join rounds, facilitated mixers, persistent project boards, pre-event matching, or no formal mechanic, each with promotion and deletion conditions. - Unteamed-participant safety net: Design the stocked project backlog, floor sweep, and time-boxed escalation, including safeguarding posture where minors participate. - Use Case: An organizer with 180 signups, mostly solo registrants, uses the Skill to publish a 1-4 team-size rule, run a one-minute pitch round after the welcome, and set a roster cut-off after the sweep but before judging. ## Quick Start Ask the Skill to design the team formation plan for your hackathon given your registration data, venue, and hacking window.
