Lesson 22 of 32 · Part One, the principles
The Chain of Thought
A big task thrown at the machine in one piece comes back as a plausible blur: everything mentioned, nothing checkable. Break it instead into a chain of small steps, ask for one step at a time, check that step against what you actually know - your prices, your syllabus, the tools already in your shed - and then feed the corrected step into the next one. You stay the builder; the machine lays one brick at a time, where you can inspect it.
How to use The Chain of Thought in Claude
Give the chain a shape in tags and the discipline looks after itself: a <steps> block listing all four so it knows where it is going, a <this_step> block naming the one you want now, and a <stop> rule telling it to halt and wait. Two things make the chain durable across days rather than one long chat. A Project holds the approved steps as files - step 1 as finally corrected, step 2 with the real dealer prices - so a new chat begins from checked bricks instead of remembered ones. And the final plan or note is worth asking for as an Artifact, which you can keep editing and download for the committee.
- List all the steps, then name the single step you want now.
- Add a stop rule or it will finish the whole chain unasked.
- Save each approved step as a Project file, not a chat message.
From GenAI for Everyone: Prompt Engineering Handbook, First Edition 2025, by Raja Rajeshwari Seshadri and Shreeram Iyer.
Give the chain a shape in tags and the discipline looks after itself: a <steps> block listing all four so it knows where it is going, a <this_step> block naming the one you want now, and a <stop> rule telling it to halt and wait. Two things make the chain durable across days rather than one long chat. A Project holds the approved steps as files - step 1 as finally corrected, step 2 with the real dealer prices - so a new chat begins from checked bricks instead of remembered ones. And the final plan or note is worth asking for as an Artifact, which you can keep editing and download for the committee.
From the book Create a Project for a long piece of work like a workshop plan, and add each approved step as a file, so every new chat starts from the steps you have already checked. Ask for the final plan as an Artifact you can download.
- List all the steps, then name the single step you want now.
- Add a stop rule or it will finish the whole chain unasked.
- Save each approved step as a Project file, not a chat message.
- Make it state assumptions before it multiplies anything.
- Ask for the final note as an Artifact you can keep editing.
Instead of
Give me a full business plan for a welding workshop.
Claude version
<me>Welder, 12 years on the job, opening my own small fabrication workshop in Ludhiana. Gates, grills, sheds.</me> <steps> 1. Machines and tools needed. 2. Rough costs - I will verify these with dealers in the market. 3. Getting the first customers. 4. Licences and registrations to take to a local CA. </steps> <this_step> Step 1 only. Two groups: must have on day one, and can buy later. One line on why each item sits where it does. </this_step> <language>Simple Hindi-English, the words a dealer in the market would actually use. No English technical jargon where a common word exists.</language> <stop> End after step 1 and wait for me. Do not start step 2, do not outline the remaining steps, do not offer a full plan. </stop> <if_unsure> If something about my workshop would change the list - shed size, three-phase supply, how much I can spend - ask me before listing, rather than assuming a figure. </if_unsure>
Then loop it
- Step 1 is good, but I already own an arc welding machine and an angle grinder. Remove them and move to Step 2.
- Using the Step 2 cost list, now do Step 3: ten ways to find my first customers within 50 km.
Why it worksEach approved step becomes the foundation for the next, so Baldev can correct one link without rebuilding the whole plan.
Instead of
Write a UPSC answer on urban flooding.
Claude version
<exam>UPSC Mains, GS Paper 1. I am in Delhi, from Patna, practising answer writing.</exam> <question>Discuss the causes of urban flooding in Indian cities and suggest measures. (250 words)</question> <what_i_want> The working, not a model answer. I have to perform this reasoning myself in the hall, so show me each link. </what_i_want> <chain> 1. What the directive "discuss" demands - and what it rules out. 2. The causes under clear heads, with natural causes separated from man-made ones. 3. Two Indian city examples, one line each on what each one demonstrates. 4. One measure tied to each cause, so no measure floats free. 5. Only then, the 250-word answer, with introduction and conclusion. </chain> <task> Work through the chain with each link under its own heading. Where a link rests on a figure or a report, name it and mark it [verify] - I will check it before I write it in an exam. At the end of link 5, give the actual word count. </task>
Then loop it
- Your step 2 mixes natural and man-made causes. Separate them and redo steps 4 and 5.
- Here is my own answer to the same question. Compare it with your steps and tell me which step I skipped.
Why it worksSeeing the reasoning laid out link by link teaches Rohan the structure, not just one model answer.
Instead of
Should our society buy an ice machine?
Claude version
<our_society> Fishermen's cooperative in Malpe, near Udupi. 60 member boats. I am the secretary. Ice now costs us about ₹3,000 a day, for roughly nine months of the season. A supplier has quoted ₹9 lakh for a small ice plant. </our_society> <chain> 1. Our yearly spend on ice as things stand. 2. The running costs I must ask the supplier about - power, water, staff, repairs, and anything I have not thought of. 3. A plain method for working out how many years it takes to recover ₹9 lakh. 4. The risks, with the ones that bite hardest in a short season named first. </chain> <rules> State your assumptions before you calculate anything - how many days you are treating as the season, and why. Put every figure on its own line as working, not inside a sentence. For step 2, give me questions to ask, not estimates to believe. Leave a blank where a number is missing and name who should supply it. </rules> <do_not> Give a final yes or no. The committee decides. Your job is to make their arithmetic checkable. </do_not>
Then loop it
- Power here is about ₹8 a unit and the supplier says 150 units a day. Redo step 3 with these numbers.
- Turn steps 1 to 4 into a one-page note in Kannada for our committee meeting.
Why it worksVisible working lets Sunitha check every number before the committee relies on it.
Questions
What is The Chain of Thought in prompt engineering?
A big task thrown at the machine in one piece comes back as a plausible blur: everything mentioned, nothing checkable. Break it instead into a chain of small steps, ask for one step at a time, check that step against what you actually know - your prices, your syllabus, the tools already in your shed - and then feed the corrected step into the next one. You stay the builder; the machine lays one brick at a time, where you can inspect it.
When should I use this technique?
When the job is too big for one answer - a business plan, a long exam answer, a purchase the committee must justify - and a wrong figure buried in the middle would spoil everything built on top of it.
How do I apply it in Claude?
Give the chain a shape in tags and the discipline looks after itself: a <steps> block listing all four so it knows where it is going, a <this_step> block naming the one you want now, and a <stop> rule telling it to halt and wait. Two things make the chain durable across days rather than one long chat. A Project holds the approved steps as files - step 1 as finally corrected, step 2 with the real dealer prices - so a new chat begins from checked bricks instead of remembered ones. And the final plan or note is worth asking for as an Artifact, which you can keep editing and download for the committee.
What are the limits of this technique in Claude?
Claude will do the whole chain in one go if your prompt leaves it any room, and the result is pleasant to read and impossible to audit - hence the explicit stop rule. On numbers, be more careful still. Asked to show its working it will lay out tidy lines of arithmetic, and a wrong multiplication inside tidy lines is harder to spot than a wrong answer on its own. Tell it to state its assumptions before it calculates - how many days of season, how many units of power - and redo the sums on paper yourself before anything goes to a committee or a bank.
How do I improve the answer after the first try?
Looping fits this principle naturally: every step is a small loop of its own. Ask for one step, read it, and check it against what you know - your real prices, your real syllabus, your real tools. Correct the weak link ("Redo step 2 with this figure"), then say "Now use that to do step 3." If an answer jumps straight to a conclusion, ask, "Show your reasoning step by step before the answer." When the chain works, save it to reuse next time.
Loop it
Looping fits this principle naturally: every step is a small loop of its own. Ask for one step, read it, and check it against what you know - your real prices, your real syllabus, your real tools. Correct the weak link ("Redo step 2 with this figure"), then say "Now use that to do step 3." If an answer jumps straight to a conclusion, ask, "Show your reasoning step by step before the answer." When the chain works, save it to reuse next time.
This lesson on the other tools
The technique is the same; the way you write it is not. ChatGPT, Gemini.Perplexity.