Flows workflow logoFlows
Hackathon Submission
0/5 steps0%

Step 1 of 5

Build the judge narrative

Judges score dozens of projects - clarity in 30 seconds wins.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Build my hackathon narrative. I will paste the project description and the judging criteria below. Produce: the 30-second story (problem someone has, what we built, the impressive part, why it matters) in plain words; the one-sentence version for the submission title/tagline; explicit mapping of the project to EACH judging criterion (what we say and show per criterion); and the anticipated judge questions with honest answers (including 'what would you do next').

PROJECT AND CRITERIA: [paste here]
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A 30-second story, tagline, criterion-by-criterion mapping, and Q&A prep.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent