This lesson is being recorded

Every video of this course is being uploaded to my YouTube channel. Subscribe so you do not miss it.

Bruno AshfordBruno Ashford @brunoashfordSubscribe

Module 3 · Lesson 3.1 · 10 min

How Claude Code Thinks and Acts

Understand the loop Claude Code runs (read, plan, act, check) so you know what it is doing and when it will ask you first.

Module 3
Your First Real Task

From testing the tool to delegating real work

Bruno Ashford
Bruno Ashford · Module 301 / 12
The shift

A chatbot waits. An agent goes and looks.

Claude Code works inside a folder on your computer.

  • Reads and searches your files
  • Plans before it acts
  • Asks before it changes anything
  • Checks its own work when asked
Bruno Ashford · Module 302 / 12
The loop

Explore, Plan, Execute, Review

  1. 1ExploreRead the data. No output yet.
  2. 2PlanApprove the approach first.
  3. 3ExecuteLet it work.
  4. 4ReviewIt checks, then you check.
Bruno Ashford · Module 303 / 12
A truth that hurts
Most bad AI output starts with asking for the answer before anyone looked at the problem.
Bruno Ashford
Bruno Ashford · Module 304 / 12
Safety first

Plan mode: think without touching

Press Shift+Tab until plan mode shows.

  • Claude reads and proposes
  • Nothing changes until you approve
  • Use it for anything touching real data
Bruno Ashford · Module 305 / 12
Messy spreadsheets

Five moves to clean data

Your original file is never touched.

  • Protect the original
  • Get a mess report
  • You set the business rules
  • Ask business questions
  • Reconcile the totals
Bruno Ashford · Module 306 / 12
Illustrative example, practice file

What a mess report finds

30rows in the sample file
4date formats in one column
3spellings of one customer
0changes to the original
Bruno Ashford · Module 307 / 12
Analysis vs. judgment

Ask for a decision, not a summary

Weak requestStrong request
What do you think?Choose between these 3 options
Summarise the dataCite numbers and source files
Give me insightsRisks and what proves us wrong
Write a reportOne page, recommendation first
Bruno Ashford · Module 308 / 12
The Delegation Brief

Brief it like a new hire

  1. 1GoalWhy the task exists
  2. 2ContextWhat a new hire needs
  3. 3InputsExact files to use
  4. 4OutputFormat, length, file name
  5. 5GuardrailsOff limits, and when to ask
Bruno Ashford · Module 309 / 12
Habits

Four habits of owners who delegate well

Small habits, big difference.

  • Ask it to look before acting
  • Read every permission prompt
  • Ask which files it used
  • Type /clear between tasks
Bruno Ashford · Module 310 / 12
Your project

A one-page diagnosis of your data

Real data, three recommendations, evidence for each.

  • Original file untouched
  • Totals reconciled
  • Every claim cites a number
  • An owner for every action
Bruno Ashford · Module 311 / 12
Recap
You do not need to be technical. You need to brief well and check the work.
Bruno Ashford
Bruno Ashford · Module 312 / 12
01 / 12

Use ← → to move. The marker highlights text and the pencil draws on the slide; navigation locks while you annotate. Undo removes the last mark, Esc exits.

1Start Claude Code inside the right folder

Claude Code sees the folder you start it in and everything below it. Open your terminal, move into your Company folder from Module 2, and start it there. Starting in the wrong folder is the number one reason people get strange answers.

Terminal
cd ~/Company
claude
2Ask it to look before it does anything

Your first message should never be an order. Ask Claude to describe what it can see. You will watch it list and read files on its own, which is the agent behaviour you are paying for.

Prompt for Claude
Look around this folder and tell me, in plain English, what kind of business files are here, what seems to be missing, and what you would need from me to help with sales reporting. Do not change anything yet.
3Watch the permission prompts

When Claude wants to create or edit a file or run a command, it stops and asks. Read the prompt: it tells you exactly what it wants to do. Approve once, approve for the session, or say no and explain why. Saying no is not failure, it is management.

4Use plan mode when the stakes are higher

Press Shift+Tab to cycle through permission modes until you see plan mode. In plan mode Claude can read and think but cannot change anything. It writes you a plan, and nothing happens until you approve it. This is the safest way to start any task that touches real data.

5Ask it to show its work

An agent you cannot audit is an agent you cannot trust. Make it a habit to ask which files it read and how it got a number. Good work survives this question.

Prompt for Claude
Before you continue: which files did you read, which ones did you ignore, and why?

The first time I watched Claude Code open a folder of invoices, read twelve files, notice two were duplicates and ask me before deleting anything, I stopped thinking of it as a chatbot. A chatbot waits for you to paste things in. An agent goes and looks.

That is the whole shift. Claude Code works inside a folder on your computer. It can read files, search them, write new ones, edit existing ones and run commands, and it asks for your permission before anything that changes your files, unless you have told it otherwise. Once you understand that loop, you stop being nervous and start delegating.

Key points

  • Claude Code works inside the folder you start it in.
  • It reads, plans, acts and checks, and asks before changing files.
  • Plan mode (Shift+Tab) lets it think without touching anything.
  • Always ask which files it used and how it got the answer.

Avoid

  • Starting Claude Code in your home folder and wondering why it is slow or confused.
  • Approving every permission prompt without reading it.
  • Opening with a big order instead of asking it to look first.
  • Treating a clear answer as a correct answer without asking for the working.
Real-world example: a dental clinic

Maria runs a two-chair dental clinic and exports her appointment book every month into a folder she never opens. She started Claude Code in that folder and asked it to look around before doing anything. It found 14 monthly exports, noticed March was missing, and pointed out that no-shows were recorded in two different ways. Nothing was changed, yet in five minutes she knew more about her own data than she had in a year.

Bruno Ashford Subscribe