CtrlK
BlogDocsLog inGet started
Tessl Logo

paker-it/devcon-hack-coach

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

1.69x
Quality

100%

Does it follow best practices?

Impact

100%

1.69x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Evaluation results

100%

46%

Hackathon Coaching Session — Getting Started

Phase 1 interrogation flow

Criteria
Without context
With context

Phase announcement

25%

100%

Questions one at a time

33%

100%

Stack question asked

25%

100%

Track question asked

0%

100%

Itch question asked

87%

100%

Pushback on multiple itches

60%

100%

Single itch selected

100%

100%

Track matched or clarified

30%

100%

Exit gate verified

91%

100%

Voice and tone

66%

100%

100%

43%

Hackathon Coaching Session — Turning an Idea into a Spec

Phase 2 spec generation

Criteria
Without context
With context

Phase announcement

60%

100%

Skip-ahead refused

100%

100%

Exactly three angles proposed

0%

100%

Angles include one-line description

0%

100%

Angles include demo moment as stage directions

0%

100%

Angles include feasibility note

0%

100%

Feature cap enforced

100%

100%

All spec fields filled

70%

100%

Concrete demo moment in spec

100%

100%

What's out names temptations

100%

100%

Exit gate confirmed

62%

100%

No code started

100%

100%

100%

39%

Hackathon Coaching Session — Building the 24-Hour Plan

Phase 3 planning and checkpoints

Criteria
Without context
With context

Phase announcement

100%

100%

Four checkpoints present

10%

100%

Correct checkpoint hours

0%

100%

Pushback on vague milestone

100%

100%

Concrete artefacts at all checkpoints

33%

100%

Scope creep refused

100%

100%

Scope-creep phrasing

37%

100%

Checkpoint table format

100%

100%

Exit gate confirmed

50%

100%

No implementation code

100%

100%

No skipping to Phase 4 early

100%

100%

100%

44%

Hackathon Coaching Session — Crafting the Pitch

Phase 4 pitch and terminal state

Criteria
Without context
With context

Phase announcement

20%

100%

Priya's draft rejected

100%

100%

Exactly three sentences

100%

100%

Sentence 1 under 20 words

0%

100%

Sentence 2 under 20 words

0%

100%

Word counts shown

100%

100%

Sentence 3 is 'Watch this'

50%

100%

Five standard Q&A present

20%

100%

Q&A answers one sentence each

100%

100%

Terminal state phrase exact

0%

100%

No implementation help offered

100%

100%

Dry-run checklist in pitch.md

100%

100%

100%

33%

Hackathon Coaching Session — Handling Tricky Requests

Anti-patterns and out-of-scope refusals

Criteria
Without context
With context

Code-before-spec refused

100%

100%

Code refusal language

100%

100%

Model building refused

100%

100%

Auth flow refused

66%

100%

Auth refusal reasoning

50%

100%

DevCon info request redirected

33%

100%

DevCon URL provided

0%

100%

Voice maintained

70%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents