Step 0 Pull a key summary from a detailed transcript (cleanup)
📥 Step input
Raw 1st meeting transcript in back-and-forth chat form (meeting-notes-raw.md)
📤 Step output
Key summary notes file (meeting-notes.md)
🛠️ Detailed follow-along guide
- Get the raw notes: press the download button below to download
meeting-notes-raw.md, the raw 1st meeting transcript, and put it in your work folder, or create the file content. - Ask for cleanup: open your Codex/ChatGPT chat and send the Codex request example prompt below.
- Save the result: copy the clean summary notes AI pulled out of the raw chat and save them as
meeting-notes.md. (This file is the Input for the next step 1 lab.)
Mission situation
The raw notes from the planning meeting mix back-and-forth talk and small talk between team members (CEO, planner, developer, designer), so they're too messy to pull requirements from directly. Learners must use Codex as a cleanup tool to produce planning notes that summarize only the key business requirements.
Learner mission
Write or download the following raw 1st meeting transcript as meeting-notes-raw.md.
meeting-notes-raw.md original (scroll)# 1st Kick-off Meeting Notes: Building an Expert Consultation Service
**Date**: 2026-07-10 14:00 - 15:30
**Attendees**: CEO, Planner (PM), Developer (Dev), Designer
---
**CEO**: Hello, everyone. Today's meeting is to discuss the basic requirements and set the direction for the "online expert consultation service" we're launching. The core is a process where users come to our platform, find experts in various fields, book a session and finish paying smoothly.
**Planner**: Yes. Let's start with the basic sign-up process. Do users have to sign up to use the service?
**CEO**: Yes, that's right. Users should finish signing up first before they can properly use features like expert search and booking. Without an account, they can only browse a little.
**Designer**: After signing up they'll search for experts — how are you thinking about expert profile pages and categories?
**CEO**: Experts should be grouped by field first. For example, categories like IT consulting, legal advice and design coaching. Users should be able to pick a category or type a search term to quickly find the expert they want.
**Designer**: So search results show a list of experts, and you go into a detail page to pick a time. How do they choose the date and time?
**CEO**: Yes, when a user picks an expert, the expert's available schedule should show as a calendar or timeline. Users should be able to freely pick the date and time they want and request a booking.
**Developer**: How does payment work right after the booking request? Is the booking confirmed only when payment happens together with the request?
**CEO**: The booking should move to "confirmed" only when payment is complete. If payment fails because of a card limit or another reason, of course that booking must not be completed — it should stay pending or be cancelled.
**Developer**: So the business rule is that if payment fails, the booking isn't created or the slot is released. Where do experts check their booked schedule?
**CEO**: Experts should have their own dashboard in our system, where they can watch and manage booking requests and confirmed schedules in real time.
**Planner**: Expert sign-up must be different from regular sign-up — do we need a separate verification or approval process? We can't let just anyone work as an expert.
**CEO**: Good point. Experts can't start right after applying. We'll require an admin approval policy: a site admin reviews their documents or qualifications and "approves" them, and only then do they appear in the expert list and join the booking system.
**Planner**: When a booking is done, sending notifications to users and experts would help usability. Which notification channel do you prefer?
**CEO**: We definitely need notifications, to tell people when a booking is confirmed or cancelled. But whether to send them by email or SMS — we need to look more at dev resources and cost. Let's not decide that yet.
**Developer**: Do we need to set rules for cancellation fees or refunds now too?
**CEO**: The cancellation fee policy needs legal review and talks with marketing too. It's hard to decide today, so let's leave it as an undecided item as well. We'll settle it at the 2nd meeting.
**Planner**: Got it. I'll gather today's decided policies and pending items into cleaned-up meeting summary notes for the first spec draft.
Codex request example (cleanup prompt)
PromptRead the raw meeting notes in meeting-notes-raw.md, remove unneeded conversation and context between speakers,
and write compact, informal summary notes of about 15 lines covering service users, feature requirements, system policies and undecided items.
Don't imagine and add anything that isn't in the original.