The most useful line in the Opus 5.5 prompting guide is that most of the prompt work is now removal. If your system prompts still carry “think step by step,” you’re paying to scaffold something the model already does on its own.

For anyone running agent orchestration in production, this reads as an operations change more than a wording change: the prompt becomes a spec plus guardrails, and the reliability work moves into effort budgets, stop conditions, and evals. The HN discussion is worth reading for how teams are ripping “think step by step” out of saved system prompts and watching quality hold.

Early third-party takes are mostly on board. explainx.ai calls it a genuine shift toward specifying what “done” looks like and handing over whole tasks, and Tech Bytes argues the habits that squeezed quality from older models now just cost you time. PrompTessor is more measured — it endorses the approach but pushes back on ritual, warning that higher effort settings and longer instruction lists aren’t wins unless your evals say so. The line forming across all three is less “prompt harder” and more “prompt less, and measure what’s left.”

tags: [ llm-ops ] [ agentic-ai ]