What problem does it solve? Hackathon organizers must publish a single participant-facing document covering rules, eligibility, challenge tracks, problem statements, submission requirements, and evaluation categories, and every dispute at the ceremony traces back to a sentence that document did or did not contain. This Skill produces that brief with defensible defaults, explicit boundaries against sibling skills, and a pre-publication structural gate. ## Core Features & Use Cases - Rules and eligibility drafting: Adopts a published forkable rule set (MLH-style), names the event-specific fields that must be edited, and routes IP or legal questions to counsel rather than drafting legal-sounding text. - Problem statement and track design: Sizes prompt specificity to the time box across four rungs (open theme to fully specified challenge), structures challenge tracks around sponsor and judging capacity rather than headcount, and writes sponsor prompts as buildable problems with published fallback sentences. - Submission checklist and categories: Derives the submission checklist from the already-chosen demo format (expo, stage, video, hybrid), names evaluation categories without weighting them, and publishes an exclusion list of what is not judged. - Use Case: An organizer with a 36-hour event, two sponsors, and a beginners track uses the Skill to produce the full participant brief, including carve-out wording, a wall-clock deadline with late policy, and a seven-item structural pass check before publication. ## Quick Start Write the participant brief for my 48-hour hackathon with two sponsor tracks, covering rules, eligibility, problem statements, submission requirements, and evaluation categories.
