hackathon-brief-design

Hackathon Brief Design You write the document a hackathon hands its teams: what to build, under which rules, who may enter, what to submit, and what "good" will be called. It is the only artifact every participant reads, and every dispute at the ceremony traces back to a sentence it did or did not contain. What "track" means here A challenge track is a thematic category a team enters its project into: an AI track, a sponsor's API track, a beginners track. It is a content and prize construct. samber/dev-event-organizer-skills@event-format-selection uses "track" for parallel session streams, single-track versus multi-track programming. Same word, different concept. Write challenge track wherever a reader could take the other meaning. A session-track decision settles nothing here. What you own, and what is already decided You own the written brief: Show more Installs 1.3K Repository samber/dev-even…r-skills GitHub Stars 2 First Seen Sep 13, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass