prompt engineering guide (1)

Stop Writing Incantations. Start Writing Briefs.

Reasoning models have internalised chain-of-thought, so some prompting tricks that worked in 2023 now make output worse. Here is what current guidance actually says to do instead.

A person writing in a notebook beside a laptop at a desk Prompting is closer to writing a brief than to writing code. Photo: Shixart1985, via Wikimedia Commons (CC BY 2.0)

By the UISC BD Editorial Desk · United Information Service Center · Published 13 September 2026 · 7-minute read

Most prompting advice circulating online was written for models that no longer exist. The advice has not been updated. The models have.

The Single Biggest Change

Reasoning models have internalised chain-of-thought. Telling a modern reasoning model to "think step by step" is instructing it to do something it already does by default.

Current guidance is blunt about the consequence: with the rise of reasoning models, some techniques can actively hurt the output. Forcing an explicit reasoning script onto a model that already plans internally can interrupt the plan it would otherwise have made.

This does not mean prompting stopped mattering. It means the job moved. The work in 2026 is choosing the right frame for the problem, not reciting a formula.

What Still Works, and Why

Be specific, and show one example. Current models pay very close attention to the details inside examples. If your example contains a stray formatting quirk, expect that quirk in every output. One carefully built example beats three careless ones.

Give explicit permission to be uncertain. This is the highest-value single line you can add to any prompt. Telling the model it may say it does not know reduces invented answers, because otherwise the only alternative to guessing is silence, and models avoid silence.

Separate the reasoning from the answer. Ask for working in one clearly marked section and the conclusion in another. You get something you can check rather than a verdict you have to trust.

State the constraints. Length, audience, format, tone, what to leave out. Every constraint you do not state is a decision you have handed to the model.

Define the role narrowly. "You are an editor checking for factual claims that lack a source" beats "you are a helpful assistant" by a wide margin.

A Structure Worth Copying

Five parts, in an order that reads naturally:

  • Task. What you want, in one sentence.
  • Context. Who it is for and what they already know.
  • Constraints. Length, format, what to avoid.
  • Example. One short sample of the output shape you want.
  • Permission. "If you are unsure of a fact, say so rather than guessing."

That is a brief. It is the same document you would write for a competent freelancer who cannot read your mind, and the resemblance is not accidental.

The Discipline Nobody Mentions

Prompt engineering in 2026 is described as a repeatable workflow rather than a writing trick. In practice that means three unglamorous habits.

Version your prompts. Keep the ones that work in a file. A prompt you cannot find again is a prompt you did not write.

Test comparatively. Run the same task through two prompt versions on the same input and read both outputs side by side. It takes four minutes and settles arguments that otherwise run for weeks.

Watch the context length. Long conversations degrade. As covered in our explainer on context windows, models recall the beginning and end of a long context far more reliably than the middle. Start a fresh conversation more often than feels necessary.

Where This Is Heading

The term now used for the broader skill is context engineering: managing long context, memory, tool access and multi-step behaviour, rather than crafting one clever paragraph.

That is a different discipline, and it is the one behind AI agents and the protocol that connects them to real tools.

If you take one thing from this piece: the people getting good results are not the ones with secret phrases. They are the ones writing clearer instructions.

Related reading

Sources

Read more…