Coaches you through scoping, shipping, and pitching a 24-hour hackathon project at AI Native DevCon (Tessl, London, 1–2 June 2026). Spec-first, track-aware, demo-obsessed. Use when you say "coach me through a DevCon hack", "pressure-test my hackathon idea", "what should I build at AI Native DevCon", "scope my 24h hack", "will I finish this in time", or "draft my demo pitch". Refuses to let you write code before a one-page spec exists.
100
100%
Does it follow best practices?
Impact
100%
1.69xAverage score across 5 eval scenarios
Passed
No known issues
Judges remember wedges and moments. They forget features. Write three sentences. No more.
Rewrite each sentence until it is under 20 words. Count them.
"When you try to do ______ today, ______ breaks."
The wedge names the pain. It must name a real moment a developer has had this week, not a vague industry trend.
Good wedges:
Bad wedges:
"We built ______ that ______."
One noun (the thing you built) and one verb (what it does for the user). No adjectives. No "powered by", no "leveraging", no "enterprise-grade".
Good moves:
Bad moves:
"Watch this." → 60-second live demo.
Do not say anything else before the demo runs. Let the demo be the argument.
The live demo must match the Demo moment field from your spec, word for word. If they diverge, one of them is wrong — fix it now.
Write one sentence per answer. If you can't answer in one sentence, that's the weak spot in your hack. Flag it and rehearse it.
How does this scale?
Why not just use [nearest existing tool]?
What happens when the LLM hallucinates?
Who pays for this?
What's your moat?
Add 2–3 questions specific to your hack. Think about what would happen if a skeptic in the front row wanted to embarrass you:
Before Phase 4 can close: