All classes Claude from Zero to Expert Syllabus · Episode 87 of 100

Claude from Zero to Expert Class #87: Planning Before Changing Code

0 views

Learn to plan before changing code: when a change needs a plan, use plan mode in Claude Code so Claude only reads and proposes, review the plan with a checklist, trim anything not requested, then carry it out step by step with a commit at each step. Episode 87 of 100, Session 18: Advanced Claude Code.

Software: Claude
Level: Advanced
Duration: ± 8 min
Series total: 15 h 1 min · 100 videos
Published: October 28, 2026

Episode 87 of 100 · view syllabus

Subscribe ▶ Watch the video lesson0 plays

Checking access...

Want to go deeper?

Join one of our courses or ask us directly on WhatsApp.

View the full 100-episode syllabus View Claude AI Courses Ask on WhatsApp

Recommended classes for you

Picked from the software, topic, and level of “Claude from Zero to Expert Class #87: Planning Before Changing Code”.

50 episodesFree preview

Agentic AI · Beginner–Intermediate

Agentic AI Without Coding

50 video lessons with PDF guides, 14 h 29 min in total. Starts with: Chatbots, Automation, and AI Agents: What's the Difference?.

14 h 29 min 66 0

View class

18 episodesFree preview

Python · Beginner–Advanced

Machine Learning Python

18 video lessons with PDF guides, 3 h 41 min in total. Starts with: Introduction to Machine Learning & First Model.

3 h 41 min 61 0

View class

6 episodesFree preview

Python · Intermediate–Advanced

Brain Tumor Segmentation with U-Net

6 video lessons with PDF guides, 1 h 10 min in total. Starts with: Brain MRI Dataset & Tumor Mask: Loading, Visualization & Patient-wise Splitting.

1 h 10 min 28 0

View class

Deep Learning CNN-LSTM Pneumonia Detection

6 episodesFree preview

Python · Intermediate–Advanced

Deep Learning CNN-LSTM Pneumonia Detection

6 video lessons with PDF guides, 57 min in total. Starts with: Chest X-ray Dataset: Loading, Exploration & Data Splitting.

57 min 22 0

View class

Need more than a video?

Other ways we can help with Claude.

Learn with a mentor

Scheduled AI & Machine Learning courses with live guidance and a certificate.

Course

Midjourney Course: Create Stunning AI Images from Text

★ 4.9

Course

DALL-E Course: Creating Professional AI Images from Text

★ 4.9

Course

Stable Diffusion Course: AI Art from Beginner to Professional

★ 4.9

See all in AI & Machine Learning →

Have it built for you

No time to learn Claude? Our team can do the project for you.

Service

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production

★ 4.9

Service

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business

★ 4.9

Service

AI Image Creation with Midjourney — Cinematic AI Art for Business

★ 4.9

See all in AI & Machine Learning →

Get notified about new Claude classes

At most one email a week. Unfollow anytime with one click.

Transcript

The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.

Show transcript

Introduction

Hi, and welcome back. In the previous episode we set up a safety net called Git. Now we learn a habit that keeps us from falling in the first place: planning before changing code. We'll ask Claude Code to draw up a plan without touching any files, review and fix that plan, and then carry it out step by step.

Step 1: When do you need a plan?

Not every request needs a plan. Changing the WhatsApp number on the website can be requested right away. But now Raka wants to add a menu page complete with a shopping cart. A small change usually touches just one file. A cart feature can touch five files or more: a new page, the styling, price data, and the order form. The risk of misunderstanding is different too. The sentence add a cart can be read many ways: does it need a login, online payment, or is sending through WhatsApp enough? And this feature involves important data: prices and customer orders. For changes like this, the rule is clear: plan first. Raka once tried the quick way in a practice project, writing only add a cart, with no other explanation. Claude worked on it seriously, but read far too much into it. The result: nine files changed, including a customer login system nobody ever asked for. Claude wasn't wrong; the request was simply too short for a job that big. Luckily there was Git, so everything could be undone. But a whole afternoon was lost checking and undoing. From that experience Raka learned: for big changes, agree on the plan first.

Step 2: Plan mode: reading without changing

Raka prepares the request carefully. The goal part explains what the customer experiences: choosing several products, seeing the total, then sending the order through WhatsApp. The context part names the price source, Sunset Coffee's shipping rules, and two things that are deliberately left out: login and online payment. Saying what you don't want is just as important as saying what you do want. The task part asks for a step-by-step plan, complete with a list of files touched and how to test them. And the limits are firm: don't change any files yet, and ask if anything is unclear. Raka presses Shift and Tab until the bottom of the terminal shows plan mode. In your version of Claude Code it may work slightly differently, so check the official documentation. What matters is the meaning: Claude only reads and proposes. Raka pastes in the request from before. Claude starts by reading the menu data: four products, complete with prices. Then it reads the home page, the styling file, and the existing order script. Notice that every tool used only reads. Not a single file is changed. Before drawing up the plan, Claude asks two questions: what's the maximum quantity per product, and should the customer's address be sent too. Questions like these prevent misunderstandings from the very start. Raka answers: a maximum of twenty per product, and name and address fields before the send button.

Step 3: Reading and reviewing the plan

Claude presents its plan. Step one creates a menu page that reads price data from the existing file, so prices stay in one place. Step two creates the cart script: add, remove with a limit of twenty, and calculate shipping by Sunset Coffee's rules. Then steps three to five: a name and address form, saving the cart contents in the customer's browser, and adding a menu link to the home page, finishing with a test on a phone. Finally, the file list: two new files, two changed files, and two files deliberately left untouched, including the secret file. A summary like this makes it easy to judge how big the change is. Now Raka reviews the plan with five questions. First, does this plan reach the goal? Yes: customers choose products, see the total, then send it through WhatsApp. Second, which files are touched? Clear and sensible. The secret file isn't touched. Third, is there any step nobody asked for? Yes: step four, saving the cart contents in the browser. It's not a bad feature, but Raka didn't ask for it, and it adds more to test. Fourth, personal data. Customers' names and addresses are sent straight through WhatsApp, not stored on the website. That's what Raka wants, so it's safe. Fifth, testing. Only step five mentions testing on a phone. Raka wants every step to have its own test. Raka asks for two fixes: remove the step that saves the cart, and add a test to every step. We're still in plan mode, so no files have changed yet. The plan now has four steps, each with a test. For example, three one-liter coffees must come to two hundred fifty-five thousand with free shipping. Test numbers like this are easy for anyone to check.

Step 4: Carrying out the plan step by step

Raka approves the plan and asks Claude to work step by step, stopping each time a step is done. Claude leaves plan mode and creates a task list with four steps. The list gets checked off one by one, so we always know where the work stands. Claude works on step one: writing the menu page. Then it stops and gives a way to test: the page should show four products with prices from the menu data. Raka tests it in the browser. It's right. Raka asks for a commit, then moves on to step two. The commit is saved, and step one is checked off. If the next step goes wrong, Raka can safely return to this point, just as we learned in the Git episode. In step two, something new comes up. The menu data doesn't have the sugar-free hamper yet. Claude doesn't decide on its own; it stops and asks, because this is outside the plan. Raka asks Claude to go back to plan mode to discuss it. This is a good habit: changes to the plan are discussed first, not done right away. Claude gives two options along with a suggestion: add it as a variant at the same price, which takes just one line in the menu data. Raka chooses A and asks Claude to continue. The decision stays with Raka; the work stays with Claude.

Step 5: The planning habit

Let's sum up the flow. Plan: Claude reads the project, asks questions, then proposes a plan, without changing anything. Review: you read the plan with five questions and cross out what isn't needed. Build: one step, test, commit, then the next step. If something new comes up, go back to the plan. This loop repeats until the feature is done. This habit is useful beyond websites. Dewi could ask for a plan before adding a new section to the monthly report script. Mr. Hendra could ask for a plan before reorganizing a question bank of hundreds of files. And Laras could ask for a plan before replacing the whole price list on the website. The plan mode screens in this video are simulations, so button names may differ in your version. The principle stays the same: for big changes, ten minutes of reading a plan saves hours of fixing.

Done!

We learned to plan before changing code: a plan mode that only reads, five review questions, crossing out what wasn't requested, and building step by step with commits. In the next episode, we see how Claude splits a big job across several helpers at once, called subagents, so tasks can run in parallel. See you there!

Practice exercises

Try these on your own after watching to lock in what you learned.

Ask Claude Code to draw up a plan for one feature in your project without changing any files
Review that plan with the five questions from this episode and cross out one thing that isn't needed
Carry out the plan step by step and make a commit after every step that works

Ask the class material

Type a question or keyword; we find the part of this episode that explains it and jump the video there.

My notes

Notes are saved with the current video time and are only visible to you.

Questions & answers

Stuck on a step? Ask here; the instructor and other learners can answer.

No questions yet.

Your instructor

Cerdas Inovasi Digital Team

Software developers, BIM & 3D engineers, and AI practitioners

53 video classes1,296 episodes

We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.

See our clients →

Memuat

Claude from Zero to Expert Class #87: Planning Before Changing Code

0 views

Software

Claude

Level

Advanced

Duration

± 8 min

Series total

15 h 1 min · 100 videos

Published

October 28, 2026

Episode 87 of 100 · view syllabus

▶ Watch the video lesson0 plays

Transcript

The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.

Show transcript

Introduction

Step 1: When do you need a plan?

Step 2: Plan mode: reading without changing

Step 3: Reading and reviewing the plan

Step 4: Carrying out the plan step by step

Step 5: The planning habit

Done!

Practice exercises

Try these on your own after watching to lock in what you learned.

Ask Claude Code to draw up a plan for one feature in your project without changing any files

Review that plan with the five questions from this episode and cross out one thing that isn't needed

Carry out the plan step by step and make a commit after every step that works

Your instructor

Cerdas Inovasi Digital Team

Software developers, BIM & 3D engineers, and AI practitioners

53 video classes1,296 episodes

See our clients →

Recommended classes for you

Need more than a video?

Transcript

0:03Introduction

0:22Step 1: When do you need a plan?

1:39Step 2: Plan mode: reading without changing

3:09Step 3: Reading and reviewing the plan

5:02Step 4: Carrying out the plan step by step

6:23Step 5: The planning habit

7:19Done!

Practice exercises

Ask the class material

My notes

Questions & answers

Your instructor

Recommended classes for you

Need more than a video?

Transcript

0:03Introduction

0:22Step 1: When do you need a plan?

1:39Step 2: Plan mode: reading without changing

3:09Step 3: Reading and reviewing the plan

5:02Step 4: Carrying out the plan step by step

6:23Step 5: The planning habit

7:19Done!

Practice exercises

Ask the class material

My notes

Questions & answers

Your instructor

Introduction

Step 1: When do you need a plan?

Step 2: Plan mode: reading without changing

Step 3: Reading and reviewing the plan

Step 4: Carrying out the plan step by step

Step 5: The planning habit

Done!

Introduction

Step 1: When do you need a plan?

Step 2: Plan mode: reading without changing

Step 3: Reading and reviewing the plan

Step 4: Carrying out the plan step by step

Step 5: The planning habit

Done!