Asked about Reasoning, and improving a prompt honestly

When would you split one prompt into several calls?

An answer that works

When it is doing several distinct jobs. Quality on each drops when they compete, and a single failure gives you no information about which step went wrong. Separate calls cost more and are far easier to debug and evaluate.

Then they push further

What does splitting cost you?

More latency, more calls to pay for, and more places for errors to creep in between steps. It is worth it when each step becomes easier to get right and to test on its own.

What gets marked up

Marked up for weighing testability and reliability against latency and cost, rather than treating chains as always better.

Reading an answer is not being able to give one. The section that teaches this is Reasoning, and improving a prompt honestly, 4 hours of Prompting.

Learn this properly

Also asked about Prompting

A prompt works most of the time but occasionally returns the wrong format. What do you do?How do you stop a model inventing data during extraction?Does telling a model it is an expert improve results?When would you use few-shot rather than zero-shot?How many examples should you use?What is a risk of few-shot prompting?Does chain-of-thought prompting still help?How do you know a prompt change actually improved things?