Prompting for Step-by-Step Reasoning

"Think step by step" is the minimal chain-of-thought instruction and it works. Adding those three words to a prompt measurably improves accuracy on reasoning tasks. But it is the bluntest instrument available. A structured reasoning prompt — one that specifies the steps, the criteria at each step, and the format of intermediate outputs — produces more consistent, auditable reasoning chains than the open-ended instruction to think step by step.

Pattern 1: Minimal CoT — effective for most tasks
"Analyze the attached proposal section and identify the three most significant contractual risks.
Think step by step before giving your final answer."

Pattern 2: Structured steps — higher consistency, auditable reasoning
"Analyze the attached proposal section and identify the three most significant contractual risks.

Follow this reasoning process:
Step 1: List every clause that creates a financial or delivery obligation.
Step 2: For each clause, identify whether the obligation is bounded or unbounded.
Step 3: For each unbounded obligation, assess the maximum potential exposure.
Step 4: Rank the three clauses with the highest potential exposure as the top risks.

Present your Step 1-3 work, then your Step 4 conclusion."

Pattern 3: Visible vs. invisible reasoning
"[Reason through this internally, then provide only your final answer]
Evaluate whether this vendor contract clause creates an indemnification obligation for our client."

"[Show your reasoning, then provide your conclusion]
Evaluate whether this vendor contract clause creates an indemnification obligation for our client."

1. 1. Start with "think step by step" For new tasks, use the minimal instruction first. If accuracy is sufficient, you are done. If not, move to a structured reasoning specification.
2. 2. Specify the reasoning steps if needed Write out the reasoning procedure explicitly: what to analyze first, what criteria to apply, what conclusions to reach at each stage. The more complex the task, the more value explicit step specification adds.
3. 3. Decide visibility Determine whether the intermediate reasoning should appear in the output. If you are auditing quality or the reasoning chain has independent value, make it visible. If you need a clean final answer, specify that the reasoning should be internal.