Hackathon Judge Report
QA
30-60 minutes per project0/5 steps0%
Step 1 of 5
Set up the rubric
Fix the criteria and standards before seeing any project.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Prompt Capsule
Set up my judging rubric. I will paste the competition's criteria below. Produce: each criterion with its weight and a 1-10 scale anchored with concrete descriptions (what a 3, 6, and 9 look like - observable behaviors, not adjectives); the functionality-verification checklist applied to every project (core action works, data persists, no dead buttons on the main path); and the report template (scores, evidence, strengths, issues, potential). Lock it before judging starts. 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
An anchored, weighted rubric plus a universal verification checklist and template.
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.
Pass the Verify Gate to complete this step