Database phase
Collect competitions, eligibility, grade limits, citizenship rules, deadlines, costs, submission requirements, judging criteria, and links.
Level 2
One-shot prompting asks AI to jump straight to the answer. Sequencing isolates each phase of a serious project so the final recommendation has evidence behind it.
The bad prompt
This prompt is too compressed. It asks for discovery, eligibility, historical analysis, fit assessment, and strategy in one move.
Worked example
Collect competitions, eligibility, grade limits, citizenship rules, deadlines, costs, submission requirements, judging criteria, and links.
Find winners from recent years. Record project titles, methods, institutions, mentor involvement, datasets, and visible judging signals.
Ask the harness to identify what separates ordinary submissions from winning submissions, with confidence ratings and source gaps.
Upload the student's resume, project history, skills, school constraints, equipment access, and calendar.
Generate project directions, choose one, and convert it into milestones, datasets, GitHub commits, mentor needs, and verification checks.
Prompt template
Alfred, we are in the database phase. Do not recommend a project yet. Create a competition database with these columns: - competition name - eligibility - deadline - cost - required artifact - judging criteria - past winner links - source URL - confidence rating Return the database structure first. Then tell me what sources you need to search.
A database, memo, repo, deployed site, dashboard, or roadmap should come out of the process.
The model has fewer chances to hide gaps when every phase has its own verification step.
Students learn why a recommendation is strong instead of accepting whatever the model says first.