← ClaudeAtlas

hackathon-flowlisted

Router for the hackathon pipeline. Looks at what already exists (HACKATHON.md, source code, a deck, a script) and says which skill or command to invoke next. Use when a team isn't sure what phase they're in or what to do next.
zghanw/hackathon-skills · ★ 0 · Data & Documents · score 62
Install: claude install-skill zghanw/hackathon-skills
# Hackathon Flow A thin router, not a state machine: it infers phase from what's already on disk and points at the right skill. No progress file to maintain beyond the `HACKATHON.md` that `/hackathon-kickoff` already writes. ## Prerequisites None to run the router itself. The skills and commands it points to below aren't hard dependencies of this plugin; check `/plugin` before assuming one is installed, and fall back to the companion-install commands in [README.md](../../README.md#companion-installs) if it isn't. ## How to use it 1. Check for `HACKATHON.md` in the repo root. - Missing → team hasn't done kickoff yet. Run `/hackathon-kickoff` first; nothing downstream should start before the rubric-aligned angle exists. 2. Check for a fleshed-out spec / feature list beyond the one-line angle. - Missing → hand off to `superpowers`' `brainstorming` skill to turn the angle into a concrete, buildable spec through dialogue, then its own `writing-plans` skill to break the spec into a task-by-task plan. 3. Check for an app (package.json, src/, etc.) with working core features. - Nothing yet → don't build features one at a time. Get a **Feature Zero** working first: one thin end-to-end slice, mock data is fine, deployed and demo-able, so there's always something to show no matter when time runs out. `superpowers`' `executing-plans`/`subagent-driven-development` builds this with full TDD rigor and per-task review; for a throwaway hac