hackathon-kickofflisted

# Hackathon Kickoff Judges score against a rubric, not against "cool tech." This skill reads the problem statement and marking scheme first and works backward from what actually earns points, before anyone touches an editor. ## When to activate - A problem statement + judging criteria / marking scheme just dropped. - Someone asks "what should we build" or "how do we make this urgent" before a solution exists. - Re-run mid-hack if the team pivots and the angle needs re-scoring. ## Prerequisites Nothing required to run this skill itself. The phase plan it produces names companion skills for later phases (`superpowers`, `ui-ux-pro-max`, `gstack`); none of them are hard dependencies of this plugin, on purpose (see [README: Built lean on purpose](../../README.md#built-lean-on-purpose)). Install each only when you actually reach that phase. ## Inputs to gather Ask only for what's missing: 1. The problem statement (paste or file). 2. The judging rubric / marking scheme, with weights if published. 3. Total hackathon duration and the hard submission deadline. 4. The pitch time limit judges give (e.g. "5 minutes + 2 min Q&A"). 5. Team roster (names, and any strong suits worth routing work to). ## Workflow 1. **Extract criteria verbatim.** List every judged dimension with its weight. If no weights are published, ask the team to gut-rank them 1st/2nd/3rd. Don't silently assume equal weight. 2. **Reverse-engineer what wins.** For each criterion, write the concrete, demo