Day 1 PBL lesson plan Codex Client

Day 1. Planning requirements definition training plan

This is a summary of university course specifications for setting up a project workspace and developing collaboration specifications using Codex Client for non-majors and planners.

Part 1. Why Codex? (5 minutes)
Part 2. Practice objectives (5 minutes)
Part 3. Follow along (20 minutes)
Part 4. How it works (10 minutes)
Part 5. PBL mission (10 minutes)

Critical difference between ChatGPT and Codex Client

The general ChatGPT web chat window and Codex Client on a multi-file project basis differ in their approach when designing requirements.

Compare items General ChatGPT (web browser) Codex Client (Workspace-based)
task cognitive scope Recognizes only one-shot text entered in the current input window Recognize all files within the project folder (Workspace)
File control method Manually copy and paste the result code displayed on the screen AI directly creates and partially modifies designated Markdown files
Multi-file inference Manual upload is required each time to modify linkage of previous files Simultaneous inference of contents of other linked files when changing one plan

Project-based development method

We have a dedicated folder designated on the desktop automationDeclare and practice as AI workspace. Under this designated folder structure, AI seamlessly connects the input-output chain of each specification file, from level 0 summary memo to level 5 email report.

Final result to be created today

Starting from long, unprocessed meeting minutes, we derive a final approved definition with error linting completed and send a decision request email.

  • πŸ“„ requirements-specification.md: Integrated business requirements and flow definition
  • πŸ“§ Planning approval request email: Undecided policy coordination draft email to be delivered to representatives (decision makers)

Hands-on Data Pipeline (Interactive Map)

When you press each step, the data conversion method (Input -> AI -> Output) is updated to the card below.

P
Preparation stage. Folder settings
S0
Step 0. Conversation log preprocessing
S1
Step 1. Analysis of memo requirements
S2
Step 2. FR sentence definition
S3
Step 3. Scenario supplement
S4
Step 4. Write planning questions
S5
Step 5. Integration and mailing
Preparation stage. Local work folder and AI linkage settings Workspace Config
πŸ“₯ Workspace (Input Environment)
Desktop
Explorer environment on the learner's computer
automation/ (create an empty folder)
Codex AI βž” Setup Workspace
πŸ“€ Integration results (Output Workspace)
Codex Client dialog box
AI workspace with folders enabled
[Folder linking completed] When you select a project Project file linkage control possible

Prepare a path for users to read and write Markdown specification documents by building a dedicated directory locally and opening the path in the Codex AI or editor environment.

Create an [automation] folder on the desktop in the local environment and run Codex Client.

Tutorial Guide & Actual Codex Client UI Flow

Click the left buttons one by one to check the **action positions (red guide boxes)** that the actual learner must click and enter directly on the Codex Client screen.

How it works and context dependency map

This is a logical architecture map where AI recognizes the files in the project folder and continues the planning stage.

Original text of conversation notes (meeting-notes-raw.md)
β–Ό (Step 0: Noise purification pretreatment)
Summary planning notes (meeting-notes.md)
β–Ό (Steps 1 to 3: Specify role/function/normal/exception flow)
Requirements definition (functional-requirements.md)
↔
Open Questions (open-questions.md)
β–Ό (Step 5: Integrate documents and share decision request email)
Creation of integrated requirements specifications and reports
β–Ό [Next session linked design roadmap]
Database Model Design (ERD)
Backend API specification
Front-end wireframe

The Markdown specification document produced step by step like this does not stop at the planning stage, but is used in the next Day 2 to Day 10 curriculum. DB ERD design, backend API specification, frontend wireframe codeis inherited as the core basic data (Context) automatically created by the codex.

PBL mission: Respond to additional requirements changes and send Gmail plugin

PBL practical tasks

Adding new policies and operating a feedback loop for representatives

During the actual development process, a representative added a new requirement to the end of the meeting minutes.
β€œLet’s also add a membership cancellation feature. When a user cancels their membership, all scheduled consultations should be automatically canceled and refunds issued immediately.”

Mission follow-up sequence

  • 1. Modify the original file: local meeting-notes-raw.md Add the representative's virtual additional lines (membership withdrawal and automatic reservation cancellation) at the bottom of the document.
  • 2. Codex Client specification update instructions: In the AI prompt window "Please update functional-requirements.md with the member withdrawal feature (FR-005) and the resulting reservation cancellation exception flow to reflect the new conversation in meeting-notes-raw.md." He instructs:
  • 3. Updated workbook and questionnaire: Lint verifies the changed requirements, activates the linked **Gmail plugin** sending function, and immediately sends an approval email regarding undecided issues related to membership withdrawal to the representative.