Flows category icon
QA
Intermediate

Hackathon Judge Report

Evaluate a hackathon project like a rigorous judge: criteria scoring, evidence checks, and structured feedback.

5 steps15 verify checks30-60 minutes per projectWorks with: emergent · chatgpt · claude · cursor
Start Guided Walkthrough

The Route

0/5 verified

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack
PROJECT CONTEXT:
I need to evaluate hackathon projects (or my own, as a judge would) with fair scoring and useful feedback.

GOAL:
Produce a rigorous judge report: criteria-based scores with evidence, functionality verification, and actionable feedback.

REQUIREMENTS:
- Scoring against the stated criteria with weights
- Hands-on functionality verification, not demo-trust
- Evidence noted per score
- Structured feedback: strengths, issues, potential
- Comparable, consistent scoring across projects

CONSTRAINTS:
- Scores require observed evidence
- Judge what exists, not what is promised
- Same rubric applied identically to every project

DEFINITION OF DONE:
- Every criterion scored with evidence notes
- The app was actually used, not just watched
- Feedback is specific enough to act on
- Scores are consistent and comparable

COMMON FAILURES TO AVOID:
- Scoring from the demo video alone
- Halo effects from polished pitches masking dead apps
- Vague feedback ('great job, needs polish')
- Inconsistent standards between the first and last project judged

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.

Related routes

More QA flows that share ground with this one.

Flows category icon
QA
Generated

صياغة الفرق بين الأسئلة البحثية والمساهمات في ورقة أو مشروع بحثي

تدفق عملي لمساعدة المستخدم على التمييز بوضوح بين الأسئلة البحثية والمساهمات، ثم صياغتهما بشكل صحيح وقابل للاستخدام في مقترح أو ورقة بحثية.

01تحديد السياق الذي ستستخدم فيه المفهومين
02استخراج تعريفين منفصلين وغير ملتبسين
03بناء مقارنة مباشرة بين المفهومين

+6 more steps to Done

Best forbuilders who have shipped a basic app before

9 steps30-60 minutesIntermediate
Flows category icon
QA

API/Error Handling QA

Verify every API contract and failure path: status codes, error shapes, timeouts, and frontend recovery.

01Inventory the API contracts
02Test success and failure codes
03Normalize error responses

+2 more steps to Done

Best forproduction-grade builds with strict verification

5 steps60-90 minutesAdvanced
Flows category icon
QA

Accessibility QA

Make your app usable by everyone: keyboard, contrast, labels, focus, and screen-reader basics.

01Keyboard-only audit
02Fix keyboard operability
03Contrast and visual pass

+2 more steps to Done

Best forbuilders who have shipped a basic app before

5 steps60-90 minutesIntermediate

Made with Emergent