📌 Part 1. Background - why Day 10 is the service launch
Looking back on the 10-day flow, the most natural ending is releasing the service to the world. No matter how great a service is, nobody uses it if it isn't introduced well to users.
| Day | Topic | Key activity |
|---|---|---|
| Day 1~2 | Planning | Idea → business model |
| Day 3~4 | Requirements/design | ERD, API spec, wireframes |
| Day 5~6 | UI/screen development | Building pages + Codex screen debugging |
| Day 7 | Finishing features | API integration, event handling |
| Day 8 | Member service | Sign-up/login/onboarding UX |
| Day 9 | Payment service | Payment flow, reassuring errors, trust UI |
| Day 10 | Service launch ✅ | Introduction, FAQ, retro, presentation |
📌 Part 2. General AI vs Codex Workspace
| Work area | General AI (chat) | Codex Workspace (linked to the work folder) |
|---|---|---|
| Service introduction | Gives a generic SaaS introduction template | Reads day10_service_overview.md and creates a tailored introduction with the real service name, features and audience |
| Writing FAQs | 20 generic app FAQ examples | Analyzes the list of features actually built and creates questions specific to the service |
| Results report | A generic project report form | Reads day10_project_summary.md and writes a specific report reflecting the real development process and results |
| Version 2.0 roadmap | Lists generic feature improvement ideas | Analyzes finished/unfinished features, then gives a sprint plan with MoSCoW priorities and team size applied |
📌 Part 3. Mapping of lab outputs
- Task 01:
day10_launch_materials.md— introduction + opening notices per channel + draft terms of use - Task 02:
day10_faq_guide.md— 20 FAQs (5 categories) + 5 customer support scenarios - Task 03:
day10_retrospective.md— results report + Keep/Problem/Try retro + MoSCoW roadmap - Mission 01:
day10_launch_package.md— complete launch package combining all materials - Mission 02:
day10_presentation.md+day10_v2_roadmap.md— final slides + 3-month sprint plan
📌 Part 4. Service launch journey diagram
[Service finished] ➔ (define the core value in one line)
│
▼ (Task 01: introduction + notices per channel + terms of use)
[Prepare launch materials] ➔ (so users understand within 5 seconds)
│
▼ (Task 02: 20 FAQs + support scenarios)
[Prepare user support] ➔ (head off the flood of first-day questions)
│
▼ (Task 03: results report + retro + roadmap)
[Sum up the project] ➔ (share results with investors and stakeholders)
│
▼ (Mission 01: combine everything)
[Launch package done] ➔ (ready to release today)
│
▼ (Mission 02: 10-minute talk + Q&A)
[Final presentation] ➔ "The next project starts with Version 2.0"
📌 Part 5. Instructor guidance (discussion topics)
- The future of communicating with AI: "What was the most surprising moment working with Codex over 10 days? In what work do you think you'll use AI most from now on?"
- Planner vs developer views: "Preparing the launch, what felt most different between the developer's and planner's views?"
- If you built Version 2.0: "If this project continued for 3 more months, what one feature would you most want to add?"
- Limits of AI teamwork and how to overcome them: "Did Codex ever lead you in the wrong direction? How did you fix it?"
📌 Part 6. Day 10 key message
💡 "AI isn't just a tool; it's a partner you plan with."
Day 10 isn't just the end of a project. It completes the course by doing a real service planner's work with AI (Codex): service launch → user support prep → sharing results → retro and next planning. Writing the final Version 2.0 roadmap isn't the end of the course but the start of the next project.