Software Development
Hackathon Team Formation
Decide how participants at a hackathon end up on teams - the published team-size rule including whether solo entry is allowed, the matchmaking mechanic that runs on the day, what happens to someone still unteamed after it, when membership freezes relative to the opening, and any track-conditioned team-composition rule. Use whenever the user mentions hackathon team size, a pitch-and-join or team-matching session, whether solo hackers are permitted, a participant nobody picked, or teams changing mid-event - even if they never say "team formation". Do NOT use to match a stuck team to expertise - use samber/dev-event-organizer-skills@hackathon-mentoring; the rules text is samber/dev-event-organizer-skills@hackathon-brief-design.
- Publisher / source
- samber/dev-event-organizer-skills (found on skills.sh)
- Upstream record
- samber/dev-event-organizer-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
0b074a9ab472201e5e10d1d7782962b9fb80c45784a30faaee940474b778c6b2