DOC-DRIVEN BUILD Codex × Antigravity PBL

REAL PROJECT 02 · DOCUMENT-DRIVEN PBL

Turn conversations into specs,
and specs into a working service.

Turn your requirements conversation with Codex into a reviewable Markdown contract, then in the Antigravity IDE build a mobile customer ordering screen and a PC admin screen based on it, and verify both the design and the service.

  • 16–24hSuggested study time
  • 4 MissionsDocs → Build → Verify
  • 100 ptsTotal score
  • 2 ViewsMobile ordering · PC admin

YOUR PROGRESS

0 / 32 checkpoints done

0%

MISSION 01 · FRAME

Rebuild the conversation into project requirements

Split the conversation's requests into facts, assumptions, questions and decisions, and set the build scope and success criteria yourself.

25POINTS
Input Requirements conversation log Output PROJECT_BRIEF · DECISION_LOG Done signal Assumptions separated from final decisions
01

Write a one-sentence definition of the service yourself

Starting from "Customers order sandwiches and drinks on their phones, and the admin manages menu, stock and order status on a PC," redefine the target users, problem to solve, key actions and out-of-scope items in your own words.

💡 Student-first rule: Before opening Codex, always write your own draft (users·key flow·out of scope) and 5 questions you can't answer yet.
02

Ask Codex to structure requirements and find counter-examples

Set limits so AI can't invent features, and have it surface missing exceptions and data questions.

CODEX STRUCTURE PROMPT
Structure the following conversation into a draft service spec.
Don't invent new facts; clearly label [Fact], [Assumption], [Question] and [Decision].
Separate the requirements for the customer mobile ordering screen and the PC admin screen,
and suggest missing exceptions, data consistency and verification questions with priorities.
03

The student, not AI, must own the decisions

Separate facts stated in the conversation from AI guesses, and leave evidence and review criteria for every final decision.

FACTA requirement stated in the conversation ASSUMPTIONA guess by AI or the team QUESTIONSomething that needs checking DECISIONReason · owner · criteria
04

Fix separate responsibilities for the four top-level folders

Planning, analysis, building and verification are independent areas with different responsibilities. Keep the folders' roles from mixing.

📦 kiosk-pbl/ PROJECT ROOT
📁 service-planning/ Planning · Specs

Service requirements, shared policies, customer mobile/PC admin screen specs, design concept (Fresh Route)

📁 service-analysis/ Metrics · Analysis

Key performance indicators (KPI), event taxonomy, data quality rules, analytics collection·query API policy

📁 service-implementation/ Service build

Antigravity IDE-based customer mobile ordering (customer) · PC admin (admin) · live store (shared) and AI work log

📁 service-validation/ Design · Service checks

Design verification plan·results, service run scenarios, standard test data, defect reports and retrospective

PASS GATE

Mission 1 done checklist

0 / 8

EDITOR WORKSPACE · 4 CORE DOMAINS

Project work files and run environment

The class page and the real sample project (planning·analysis·build·verification) are in the same folder. Click a card to open a doc or run the built app.

🚀 Open built service launcher ↗

DOWNLOAD CENTER · MARKDOWN GUIDES

Class guides and mission guides

Original Markdown files per mission that students can read and use as templates. Click to preview or download.

EVALUATION · 100 POINTS

We grade traceability, working flows and human verification over looks

Beyond the final screens, we grade student drafts, ID traceability across requirements-build-tests, run evidence and human judgment on AI suggestions.

Download detailed rubric MD ↓
01 · 25 pts

Requirements framing

Student draft·questions first
5 pts
Separate facts · assumptions · questions · decisions
7 pts
MVP scope·success/failure criteria
7 pts
Reasons for adopting·changing·rejecting AI suggestions
6 pts
02 · 25 pts

Markdown spec package

Mobile·PC screen·state specs
7 pts
Menu data·API·analytics contract
7 pts
Design principles·safety/copyright boundaries
5 pts
REQ→UI→DATA→API→TEST traceability
6 pts
03 · 30 pts

Antigravity service build

Key customer mobile ordering flow
8 pts
PC admin order checking·status changes
7 pts
Exceptions·recovery·totals·status consistency
6 pts
Matches approved doc IDs
5 pts
AI work log·human judgment records
4 pts
04 · 20 pts

Design·service verification and retro

Design verification (doc consistency·gaps)
5 pts
Service verification (reproduce mobile·PC·exceptions)
6 pts
Defect records and re-check after fixes
5 pts
AI vs human judgment retro·presentation clarity
4 pts
Final pass criteria 70+ total points (50%+ on each mission) All 4 mission outputs submitted Key customer mobile + PC admin flows run 0 Critical defects A person verifies·explains AI output directly
⚠️ Safety·ethics and AI accountability rules you must follow (violation = automatic fail)
  • Never store real personal data (names·phone numbers·addresses), real payment info or secret API keys in code or analytics events.
  • Don't copy logos, signature text, product images or source code from commercial services (like Subway); use your own design concept (Fresh Route) and sample menu data.
  • Write your own draft before opening AI, and don't let AI add requirements that weren't in the conversation as if they were facts.
  • Record at least 2 cases where you rejected or changed AI suggestions, and explain your architecture and verification evidence in your own words in the final presentation.

SAVE YOUR WORK

Save your current progress as a Markdown file

Checklist progress is saved in your browser automatically, and you can download it right away as a progress log for submission (DOC_DRIVEN_PBL_PROGRESS.md).