Day 21 of 21
Final build day - plan, build, test, and ship one real improvement
Goal: This is the last day of the challenge. Today you use every skill from all 21 days together — on one real, small improvement that you will take from an idea all the way to a tested, committed result. You will plan before building, approve only what you understand, preview on desktop and mobile, check the diff, and write a short summary of what you shipped and what safety habit helped you most.
What to do
Create your final branch and update AGENTS.md
Open GitHub Desktop. Create a branch named "day-21-final-build" and confirm it is your active branch. Then open your AGENTS.md file in a text editor and update the Current Goal line to describe your one improvement. Save AGENTS.md. Now when you open Codex it will know exactly what you are building today.
Ask Codex for a plan — do not approve anything yet
Open a terminal in your project folder, start Codex, and give it your improvement as a planning-only request. Do not say "go ahead" or approve anything in this step. You are only asking for a written plan.
Read my AGENTS.md first. Then write me a plan for this improvement: [PASTE YOUR ONE IMPROVEMENT SENTENCE]. Include: which files you will change, exactly what you will do to each one, and anything that could go wrong. Do not touch any files yet. Wait for me to approve the plan.Approve phase 1 only and watch the build
Read the plan Codex gave you. If it mentions multiple steps or multiple files, approve only the first step — not the whole plan at once. Type your approval like this: "Approved: go ahead with step 1 only. Do not proceed to step 2 until I review the result." Watch what Codex does. If it starts changing files you did not expect, type "stop" immediately.
Approved: go ahead with step 1 only. Stop after step 1 is complete and wait for my review before continuing.Preview on desktop and on your phone
Before committing anything, preview the change in your browser. Open the page in your main browser on your computer first. Then open the same page on your phone — either by using your phone as a Wi-Fi hotspot or by using your browser's mobile view (press F12 in Chrome, then click the phone/tablet icon at the top). Check: does the change look right on a large screen, Does it still look right on a small screen, Are any buttons too small to tap?
Review the diff — do not skip this step
Open GitHub Desktop. Click on each changed file in the left panel and read the diff carefully. Ask these three questions: Did only the files in the plan change, Does the number of changed lines feel right for what I asked, Are there any removed lines (red, marked with -) that I did not expect to be deleted, If anything looks unexpected, go back to Codex and ask it to explain before committing.
Commit the improvement with a clear message
If the diff looks right and the preview looks right, commit the change in GitHub Desktop. Click in the "Summary" box at the bottom-left and write a clear commit message — describe what changed in plain English, for example: "Change homepage hero heading to Build without coding." Click "Commit to day-21-final-build." Then click "Push origin" at the top to save it to GitHub.
Write your three-sentence project summary
Open a note app, a text file, or a piece of paper. Write exactly three sentences: (1) What did I ship today that I could not have built 21 days ago, (2) Which safety habit from this course saved me from a mistake at some point, (3) What is the one thing I want to build next, Keep these sentences specific — this is your record of what you have learned.
Expected result
One complete improvement is planned with Codex, built one phase at a time, previewed on desktop and mobile, checked with a diff review, committed to GitHub with a clear message, and documented in three written sentences. You have finished the 21-Day ChatGPT Codex Challenge.
Key takeaway
- You started this challenge not knowing how to use AI safely on a real project. You finish it able to branch, plan, approve incrementally, preview, review a diff, commit, and recover from mistakes. That is a complete non-developer safety toolkit. Now go build something real.