📌 Part 1. Introduction background - Why Day 10 is the service launch
Looking back on the 10 days of training so far, the most natural ending is Opening the service to the worldIt is. No matter how great your service is, if you don't introduce it well to users, no one will use it.
| date | topic | core activities |
|---|---|---|
| Day 1~2 | planning | Idea → Business model refinement |
| Day 3~4 | Requirements/Design | ERD, API specification, wireframe |
| Day 5~6 | UI/screen development | Publishing + Codex screen debugging |
| Day 7 | Feature completion | API integration, event handling |
| Day 8 | member service | Signup/Login/Onboarding UX |
| Day 9 | payment service | Payment flow, error relief, trustworthy UI |
| Day 10 | Service launch ✅ | Introduction, FAQ, Retrospective, Announcement |
📌 Part 2. Comparison of General AI vs Codex Workspace
| work area | General AI (conversational) | Codex Workspace (working directory linkage) |
|---|---|---|
| Service introduction letter | Provides a common SaaS introduction template | day10_service_overview.mdRead and create a customized introduction that reflects the actual service name, function, and target. |
| Write an FAQ | 20 examples of universal app service FAQs | Generate questions specific to the service by analyzing the list of actually developed functions |
| Result report | Typical project report format | day10_project_summary.mdRead the detailed report reflecting the actual development process and performance |
| Version 2.0 Roadmap | List common feature improvement ideas | Sprint planning with MoSCoW priorities and team size after analysis of completed/incomplete feature list |
📌 Part 3. Mapping practice results
- Task 01:
day10_launch_materials.md— Introduction + Channel-specific opening notice + Draft Terms of Use - Task 02:
day10_faq_guide.md— 20 FAQs (5 categories) + 5 customer response scenarios - Task 03:
day10_retrospective.md— Result report + Keep/Problem/Try retrospective + MoSCoW roadmap - Mission 01:
day10_launch_package.md— Complete launching package that integrates all materials - Mission 02:
day10_presentation.md+day10_v2_roadmap.md— Final presentation + 3-month sprint plan
📌 Part 4. Service launch journey flowchart
[Service completion] ➔ (one line definition of core value)
│
▼ (Task 01: Introduction + Notice for each channel + Terms of Use)
[Prepare launch materials] ➔ (So that users can understand within 5 seconds)
│
▼ (Task 02: 20 FAQs + response scenario)
[Preparing for user support] ➔ (Preventing a flood of inquiries on the first day)
│
▼ (Task 03: Result report + Retrospective + Roadmap)
[Project Summary] ➔ (Delivering results to investors and stakeholders)
│
▼ (Mission 01: Full integration)
[Launching package complete] ➔ (A level that can be distributed today)
│
▼ (Mission 02: 10 minute presentation + Q&A)
[Final Announcement] ➔ “The next project will start with Version 2.0”
📌 Part 5. Instructor guidance (topic of discussion)
- The future of communication with AI: “What was the most surprising moment during the 10 days of collaborating with Codex? In what work do you think you will utilize AI the most in the future?”
- Differences between planner and developer perspectives: “As you were preparing to launch the service, what did you feel was the biggest difference from a developer’s perspective and a planner’s perspective?”
- If you create Version 2.0: “If this project continues for three more months, what is one feature you definitely want to add?”
- Limitations and overcoming AI collaboration: “Have you ever experienced Codex leading you in the wrong direction? How did you fix it?”
📌 Part 6. Day 10 Key Message
💡 “AI is not a tool, but a partner in planning together.”
Day 10 is not just the end of a project; Service launch → Preparation for user support → Sharing of results → Retrospective and next planningIt is completed with training to perform the actual work of a service planner with AI (Codex). Creating the final Version 2.0 roadmap is not the end of training, but the beginning of the next project.