Task 1. Connect Features Lab
Task 01: Save Sign-Up Data and Switch Screens (Feature Integration)
Control the sign-up form submit, save the input to local storage, then move to the done screen.
A hands-on AI teamwork Task board that uses Codex to automatically analyze and fix the data structure misunderstandings, scattered terms and change ripple problems startups face during MVP development.
From connecting features to static screens to checking user journeys and catching abnormal input errors — use Codex as a scenario coach and teammate to put together a well-finished service.
Task 01: Save Sign-Up Data and Switch Screens (Feature Integration)
Control the sign-up form submit, save the input to local storage, then move to the done screen.
Task 02: Find Lost Info Across Screens and Add a Keep Guard (User Scenario Review)
Find breaks in the user journey — like search filters resetting when going from list to detail and back — and fix them with sessionStorage caching.
Task 03: Lock Rapid Repeat Submits and Guard Time Boundaries (Feature Validation)
Find where rapid mouse clicks cause duplicate database inserts and where past-time bookings slip through, and insert guard logic.
ADD-D07-T01: Document 10 Rules like Campaign status, Budget and Target
Document at least 10 Business Rules — Campaign status, Budget, period, Target, Frequency Cap and more — before writing code, and define exceptions.
ADD-D07-T02: Separate Controller–Service–Repository responsibilities
Cleanly separate Controller–Service–Repository responsibilities and build Business Rules and DB saving in back-end code.
ADD-D07-T03: Concurrent requests, Budget exhaustion & DB failure tests
Run exception and validation tests including concurrent requests, Budget exhaustion, invalid state transitions and DB failures, and pass the exception policies.
Mission 01: Jointly check facts, assumptions and gaps in AI's diagnosis
Planners and developers review AI's quality diagnosis together and agree on the evidence and priority of fixes for loading feedback, save failures and policy breaks.
Mission 02: Planner–developer joint check of E2E user flows
Don't accept AI's suggested E2E scenario as-is; check together the path from a beginner's view, failure recovery and whether data is kept.