Chain-of-thought: making the model show its work
Asking the model to reason step-by-step before answering raises accuracy on hard problems · know when it earns its cost.
::TL;DR · the whole lesson in three lines
- MOVEAsking the model to reason step-by-step before answering raises accuracy on hard problems · know when it earns its cost.
- DRILLYou will run the same hard question two ways · answer-only and chain-of-thought · and feel where the reasoning trace catches the failure that the direct answer hid.
- WINYou ran the same hard question both ways and can compare.
::concept · what's actually happening
Chain-of-thought (CoT) prompting is the practice of asking the model to lay out its reasoning explicitly before producing a final answer. The phrase 'think step by step' became famous, but the technique is more general · any instruction that forces sequential reasoning ('first list the constraints, then identify the conflicts, then propose a resolution') is CoT.
read full concept · 4 more paragraphs →collapse concept ↑
On hard reasoning problems · math, multi-step logic, planning, debugging · CoT meaningfully raises accuracy. The model uses the intermediate reasoning as scratch space, and writing it down keeps it from collapsing complex logic into a guess. On easy problems, it is overhead.
Modern reasoning-tuned models (Claude with extended thinking, OpenAI o-series, Gemini Thinking) bake CoT into the model itself · they produce hidden reasoning before they answer, often visibly to you, sometimes not. For these models, you do not need to ask · they already are.
Two failure modes are common · the model produces beautiful reasoning that arrives at the wrong answer (sounds smart, is wrong), or the model produces reasoning that contradicts its own final answer (the chain says 'A is impossible,' the answer says 'so the answer is A'). Read the chain, not just the conclusion.
CoT is verification fuel · when the model shows its work, you can spot the wrong step. When it just hands you an answer, you cannot. For any decision you actually care about, the reasoning trace is the audit log that lets you catch the failure before you ship on it.
::drill · do the thing
You will run the same hard question two ways · answer-only and chain-of-thought · and feel where the reasoning trace catches the failure that the direct answer hid.
::L42 drill · copy-paste into any AI chat
I want to feel the difference chain-of-thought makes. Here is a real problem I am working through: [DESCRIBE A REAL MULTI-STEP PROBLEM YOU HAVE · e.g. a planning decision with constraints, a debugging puzzle, a math word problem, an ambiguous policy question]. I will ask you the same question two ways and want your most honest work each time: Round 1 · 'What is your answer? Just the answer, one or two sentences.' Round 2 · 'Walk me through this step by step. List the constraints first, then the implications, then your conclusion. Show every step.' After both rounds, tell me: did the reasoning in Round 2 catch anything Round 1 hid? Was there a step in Round 2 you are least confident about? Where would you most want me to push back?
::steps
- 01Pick a real problem with at least three moving parts.
- 02Run Round 1 · answer-only.
- 03Run Round 2 · explicit chain-of-thought.
- 04Compare the two answers · are they the same? Different?
- 05Read the chain for any step that feels weak · push back on that step.
- 06Note: when do you want CoT going forward, and when do you skip it?
::outcome · what should be true
- You ran the same hard question both ways and can compare.
- You found at least one place where the chain revealed something the direct answer hid.
- You can name when CoT is worth its extra tokens and when it is not.
- You read a chain critically rather than skimming to the conclusion.
::trap · the most common failure
Operators ask for chain-of-thought, then skim past the chain to read the bolded conclusion. The chain is the value. If you are not reading it, you are paying for explanation you do not use.
::end of the curriculum
You're at Pilot level. There's no Level 6.
The next move is doing the work, not another lesson. If you want operator-grade infrastructure, that's /orangebox. If you want the lab's working journal, /founders-view. If you want to collaborate on the curriculum itself, the source is public on GitHub.
::other lessons at Operator level
Local AI · Ollama — privacy, offline, and the limit of free
At Operator level you need an honest opinion about local-only AI. Even if you don't use it daily, you should have run it once.
Model routing — switching between Claude, GPT, Gemini mid-task
Operators don't pick one AI. They route each task to the model that does it best. Knowing the strengths is the skill.
MCP servers — the plug socket that turned AI into a real tool
Model Context Protocol is the standard plug. Knowing what plugs in changes what your AI can actually touch — your files, your inbox, your calendar, your repos.
Agent mode — when AI takes action, not just answers
The frontier of useful AI is agents that DO things — browse, click, file, send. The actual skill is the safety pattern, not the magic.
Computer use — when AI takes the mouse and keyboard
Claude in Chrome, ChatGPT Atlas, computer-use beta — the frontier is AI that drives your browser like a human. Knowing the safety pattern is the actual skill.
What AI cannot replace — taste, judgment, relationships
The operators winning in 2026 are the ones who learned what AI is for and what is theirs. Knowing the line is more valuable than any prompt.
Agents 101: model plus tools plus loop
An agent is a model with tools running in a loop until done · know when you need one and when you don't.
MCP: structured tools for AI
Model Context Protocol is the USB-C of AI tooling · learn the shape before you wire anything.
Skill primers: teach a session your context in 30 seconds
A skill is a reusable file that primes a fresh AI session with your project, voice, and rules · stop re-explaining yourself.
Local models with Ollama
Run Llama, Qwen, or Mistral on your own laptop · no API, no logs, no monthly bill for the work that should stay home.
Vision models: when to use them
Vision lets the model see images · powerful for screenshots and diagrams · weak for precise spatial work · know the line.
Audio and Whisper transcription
Whisper turns audio into text · meetings, voice memos, interviews · the AI-era replacement for note-taking.
RAG vs long context: when to retrieve, when to dump
RAG fetches the right slice of your data at query time · long context stuffs everything in · know which problem you actually have.
Embeddings: meaning as numbers
An embedding is a list of numbers that captures the meaning of text · learn the shape and you unlock semantic search, deduplication, and clustering.
Fine-tuning vs prompt engineering
For individuals, fine-tuning is almost never worth it · know exactly when it actually is.
AI safety in personal use
PII, NDAs, financial data, and other people's secrets · know the rules of what you do not paste.
Multimodal prompting: combining text, image, audio
The strongest prompts use the medium that fits the question · sometimes you describe, sometimes you show, sometimes you do both.
Tool use and structured output
Function calling makes the model return JSON your code can use · know the contract before you build on it.
Cost optimization: tokens, caching, model selection
AI is metered · the operators who stay profitable measure what they spend and choose the model that fits the task.
::part of the AtomEons /learn curriculum · 45 lessons · 5 levels · cc-by 4.0