Atom of Thoughts
Solve a hard question by repeatedly boiling it down to a simpler one that has the same answer. Atom of Thoughts maps a problem into a graph of dependent subquestions, resolves the parts that can be settled, and folds them back into a new self-contained question. Each new question carries no history, so the model always reasons over a clean, focused state instead of an ever-growing transcript.
*These are learning tools, not prompts. They teach you to write your own, think of them as training wheels that guide you while you learn, then fall away once you can ride on your own.
Shrink the Question, Keep the Answer
Most decomposition methods keep adding to the record. They break a problem into sub-steps and pile each result onto a running transcript, so by the final step the model is reasoning over a long, cluttered history. That accumulated context is both expensive and distracting; the model has to re-read everything to find the few facts that still matter.
Atom of Thoughts takes the opposite approach: it contracts. It treats the problem as a dependency graph of subquestions, resolves the independent ones, and then rewrites the whole problem into a new, smaller question that already absorbs those resolved parts. Crucially, that new question is answer-equivalent to the original, solving it gives the same final answer, but it is self-contained and depends on no prior history.
Because each new question stands on its own, the process is memory-less in the Markov sense: the next reasoning state depends only on the current atomic question, not on the path that produced it. The model keeps working on progressively simpler, fully-specified problems until one is trivial to answer.
A long reasoning transcript spreads the model's attention thin and lets early mistakes linger in context. By contracting each solved part into a fresh, self-contained question, Atom of Thoughts gives the model a clean state at every step. There is less to re-read, fewer places for an error to hide, and the compute is spent on the part of the problem that is still open rather than on re-processing what is already settled.
The Atom of Thoughts Process
A repeating loop of decompose, contract, and continue
Decompose into a Dependency Graph
Break the current question into subquestions and map how they depend on each other. Some subquestions can be answered on their own; others wait on those answers. This graph makes the structure of the problem explicit instead of leaving it tangled in one prompt.
"A train leaves at 2pm going 60 mph; another leaves the same station at 3pm going 80 mph. When does the second catch the first?" Subquestions: head start distance, closing speed, time to close.
Resolve the Independent Parts
Answer the subquestions that do not depend on anything still open. These become known facts. The dependency graph tells you exactly which parts are ready to be settled now, so no effort is wasted guessing at pieces that are not yet determined.
Head start distance: the first train travels one hour at 60 mph, so it is 60 miles ahead when the second departs.
Contract into a New Atomic Question
Fold the resolved facts back into the problem and rewrite it as a new, self-contained question that no longer references the parts already solved. This contracted question has the same answer as the original but is simpler and carries no history.
New atomic question: "How long to close a 60-mile gap when gaining 20 mph?" The head start and speeds are absorbed; nothing else is needed.
Repeat Until Trivial, Then Answer
Treat the contracted question as the new starting point and run the loop again if it is still complex. Each pass produces a simpler self-contained question, until one is easy enough to answer directly. That answer is the answer to the original problem.
60 miles divided by 20 mph is 3 hours, so the second train catches the first at 6pm. Done.
See the Difference
Accumulating context versus contracting to a clean state
Accumulating Decomposition
Step 1 result, plus step 2 result, plus step 3 result, all kept in context. By the final step the model re-reads every earlier line to find the two numbers it still needs.
Context grows with every step. Attention is spread across stale detail, and an early error stays in view, where it can mislead later steps.
Atom of Thoughts
Each solved part is folded into a fresh question. The model only ever sees one small, self-contained problem: "Close a 60-mile gap at 20 mph."
The state stays small and clean at every step. Compute focuses on what is still open, and the new question is answer-equivalent to the original.
Practice Responsible AI
Always verify AI-generated content before use. AI systems can produce confident but incorrect responses. When using AI professionally, transparent disclosure is both best practice and increasingly a legal requirement.
Most US states are actively legislating AI transparency and accountability. Critical thinking remains your strongest tool against misinformation.
Atom of Thoughts in Action
See how contracting to atomic questions handles multi-part problems
"In what year did the director of the film that won Best Picture at the 96th Academy Awards make their feature directorial debut?"
Decompose: (a) which film won Best Picture at the 96th Awards, (b) who directed it, (c) the year of that director's debut feature.
Resolve and contract: Once (a) and (b) are settled, the problem contracts to a single atomic question: "In what year did [that director] make their debut feature?" The earlier hops are absorbed and no longer cluttering the state.
Answer the atom: The model now answers one clean lookup rather than juggling a three-part chain in a single growing prompt.
"A shop buys 120 shirts at 8 dollars each, sells 70 percent at 20 dollars, and the rest at a 50 percent discount. What is the profit?"
Decompose: cost, full-price revenue, discount revenue, then profit.
Resolve and contract: Cost is 120 x 8 = 960. Full price sells 84 shirts at 20 = 1680. The problem contracts to: "Add discount revenue on 36 shirts at 10 dollars to 1680, then subtract 960."
Answer the atom: 36 x 10 = 360, so revenue is 2040, and profit is 2040 - 960 = 1080. Each contraction left a smaller, fully-specified question.
"A project needs design, then two parallel build tracks, then a merge and a review. Design takes 3 days, the tracks take 5 and 7 days, merge 1 day, review 2 days. What is the shortest finish time?"
Decompose: the parallel tracks depend on design; merge depends on both tracks; review depends on merge.
Resolve and contract: Design is 3 days; the slower track governs the parallel phase at 7 days. The problem contracts to: "Add 3 + 7 + merge 1 + review 2."
Answer the atom: 13 days. By resolving the parallel dependency first, the contracted question is a simple sum with no branching left.
When to Use Atom of Thoughts
Best for multi-part problems with clear dependency structure
Perfect For
Questions that chain several lookups benefit from contracting each resolved hop, so the model never carries the whole chain at once.
Problems where some parts can be settled before others map naturally onto a dependency graph, and each contraction leaves a cleaner sum or deduction.
When context length is the bottleneck, contracting solved parts keeps each step small, which controls both cost and the loss of focus that long traces cause.
The contracted atomic question can be handed to any solver, so Atom of Thoughts can wrap around existing reasoning techniques as a structuring layer.
Skip It When
If a problem has no internal structure to resolve, there is nothing to contract, and the decomposition overhead buys nothing.
When every subquestion depends on every other, there are no independent parts to settle first, so the contraction step has little to work with.
Because the method discards solved detail as it contracts, it is a poor fit when a complete, auditable record of every intermediate step must be preserved.
Use Cases
Where Atom of Thoughts delivers the most value
Research Question Answering
Resolve multi-hop questions over knowledge bases by contracting each settled hop, keeping the working question small and the retrieval focused.
Quantitative Analysis
Work through layered financial or scientific calculations where settling independent terms first turns a daunting problem into a short final sum.
Project Planning
Compute critical paths and timelines by resolving parallel dependencies into a single contracted schedule question the model can answer directly.
Long-Context Pipelines
Keep token usage and latency under control on reasoning pipelines by contracting resolved sub-results instead of carrying an ever-growing transcript.
Wrapping Existing Solvers
Use the contraction loop as a front end that hands a clean atomic question to whatever reasoning method you already trust for the final answer.
Exam-Style Problem Sets
Tackle structured problems that build in stages, settling early parts and contracting so the hardest remaining step is faced in isolation.
Where Atom of Thoughts Fits
A contraction-based turn in the decomposition family
Use Atom of Thoughts to keep the problem state small and self-contained, then apply a solver like Chain-of-Thought or Least-to-Most to the final atomic question. The contraction handles structure and context; the solver handles the last clean step.
Related Techniques
Explore complementary decomposition techniques
Reason Over Clean States
Try structuring a multi-part problem as atomic questions in the Prompt Builder, or explore how Atom of Thoughts relates to the wider decomposition family.