AI in 2026 demands more from you than simple instructions. Modern systems can plan, critique, revise, and work across long context windows. They are no longer moved by vague guidance such as "be clear" or "add detail". They need a defined environment to operate within.
Modern prompting is about shaping the system, not decorating the request. When you set the frame, the workflow, and the output contract, the model gains the structure it needs to behave predictably. You do this once, and the benefits carry through every answer. You set the constraints. The model works inside them on your behalf.
If you do this, just once, your AI output will be steady and structured, and you will find it much quicker and easier to work with. When you tell the AI how to respond, you apply guardrails for the system to work within. Guardrails set by you, not the AI.
1. Start with the system, not the request #
AI has advanced quickly. Its answers can now be broad, deep, and varied. To keep that power under control, you begin by defining the frame the model must work within. This frame sets the role, the tone, the limits, and the rules for handling uncertainty. It is the foundation the rest of the prompt stands on.
Most prompt failures do not come from unclear questions. They come from the model having no stable footing. Without a frame, the AI will guess at how formal to be, how cautious to be, and how much structure to use. Those guesses shift from run to run, which leads to drift and inconsistency.
A system frame removes that guesswork. It tells the model what it is, how it should behave, and what matters most. It defines what is in scope, what is out of scope, and how to respond when the request touches the edges. With this in place, the rest of the prompt becomes lighter and more reliable.
The frame does not need flourish. It needs clarity, discipline, and a steady tone. With that foundation, the model behaves less like a pattern generator and more like a tool working inside a defined brief.
In practice, the system frame is the architecture behind the output. It does not need flourish or personality. It needs to state the role, the rules, and your expectations.
SYSTEM FRAME
You are an analytical engine. You work with steady reasoning, cautious claims, and plain structure. When the request is unclear, you and ask
for what is missing. You avoid invention and keep within the boundaries set
for you.
TASK
Summarise the key points from the supplied text in three short sections.
OUTPUT CONTRACT
Produce:
- Context
- Reasoning
- Conclusion
Rules:
If the request is ambiguous, list interpretations and ask for clarification.
If information is missing, state what is missing before answering. Do not invent facts.
Keep the final answer concise and structured.
WORKFLOW
- Identify assumptions.
- Plan the answer.
- Produce the answer.
- Critique it for clarity and accuracy.
- Produce a revised final version.
The AI is told "You are an analytical engine" as that gives the model a defined role to work from. Without a role, the model guesses at how formal to be, how cautious to be, and how much structure to use. A simple line such as "You are an analytical engine" sets the tone and keeps the behaviour plain, steady, and predictable. It avoids personality, avoids flourish, and keeps the work focused on reasoning rather than style.
If you do not supply the role, the AI will provide one; and that one will vary, creating work for you. How to minimise the work you need to do and have the AI manage and apply the prompt is dealt with in the section [Having the AI Manage the Prompt
Template](#ai-manage-prompt).
2. Define the output contract #
Modern models behave more reliably when you specify the shape of the answer: structure, scope, exclusions, formatting, and the rules for handling missing or ambiguous information. This is far stronger than broad guidance such as "be concise".
When you define the output contract, you are not telling the model what to think. You are telling it what form the answer must take. This removes a large amount of guesswork. Modern systems have wide latitude in how they respond, and if you do not narrow that down, they will choose a structure for you. That choice will vary from run to run, which means more tidying and more checking on your side.
An output contract fixes the frame. It tells the model which sections to produce, how to handle gaps, and how to behave when the request is unclear. It also removes the temptation to drift into style, flourish, or padding. You are giving the model the rails to run on.
A good contract does four things. It sets the structure. It sets the limits. It sets the rules for uncertainty. And it sets the standard for brevity. Once these are in place, the model has far less room to wander. You get answers that are steadier, easier to scan, easier to compare, and easier to work with.
The contract also acts as a safeguard. By telling the model what to do when information is missing, you prevent it from filling the gaps with invention. By telling it how to behave when the request is ambiguous, you prevent it from guessing. These two points alone remove a large share of common errors.
In short, the output contract is the quiet discipline behind the work. It keeps the model inside the brief, keeps the structure predictable, and keeps the answer focused on what you asked for rather than what the model feels like producing.
3. Use decomposition as a control mechanism #
Modern models already break tasks into steps, but the steps they choose may not match the work you want done. Light guidance prevents the model from wandering and keeps the task anchored to your brief.
When you state the assumptions the model is allowed to make, you draw a clear line between what is permitted and what is not. This stops the model from filling empty spaces with guesses. Large models are inclined to complete patterns, and if you do not show them where the firm ground ends, they will supply their own footing.
A natural extension of this is to make the model aware of what is missing. Once the assumptions are set, the next step is to mark the gaps. This creates a smooth handover from what the model may rely on to what it must not invent. By pointing out missing information, you show the model where the edges of the task sit. When the model knows what is absent, it is less likely to drift into speculation or produce material that does not belong in the answer. You are giving it a map of the gaps so it does not try to fill them on its own.
Together, these two steps act as guardrails. They keep the work inside the brief, reduce the chance of invention, and ensure that the model stays within the limits you have set.
You can also break the task into a simple chain such as understanding → planning → execution. This mirrors what the model already does internally, but it makes the process explicit. When the steps are explicit, the model is less likely to skip ahead or solve the wrong problem.
Breaking the interaction into smaller stages also helps with scope. By naming the steps, you give the model a narrow lane to work in. It cannot jump to conclusions, and it cannot pad the answer with material that does not serve the task. The work stays tidy, and the output stays close to what you asked for.
In short, decomposition is a practical form of control. It does not restrict the model’s ability to give a good answer, but it does restrict where the model goes to supply that answer. This keeps the work steady, predictable, and within scope, so that it remains relevant to what you are doing.
4. Add a self-critique loop #
Modern models benefit from a short cycle of controlled refinement. Once the first version of the answer is produced, a brief review stage forces the model to check its own work against the constraints you have set. This is not a call for hidden reasoning. It is a prompt to tighten the output.
A review step also encourages the model to correct small slips in structure, scope, or tone. It is easier for the model to adjust an existing draft than to produce a perfect answer in one pass. The revision stage gives it a second chance to align with the brief.
This process also reduces noise. When the model has been told that its work will be checked and refined, it tends to produce cleaner first drafts. The revision step becomes a light polish rather than a rescue job.
In practice, this creates a steady rhythm: draft, inspect, refine. It keeps the work within bounds and produces answers that are clearer, more accurate, and easier for you to use.
5. Stack roles for higher-quality output #
Layered roles give you steadier output because each stage is handled by a specialist rather than a single broad persona. Modern models respond well to this division of labour. It narrows the scope of each step and reduces the chance of drift away from what you want.
A domain expert handles the substance. An editor handles clarity and structure. A risk assessor checks for overreach, missing information, and unwarranted certainty. A summariser produces a clean final version. Each role has a narrow brief, which keeps the work tidy and keeps the answer aligned with the task.
Here is an example prompt using layered roles:
ROLES
Domain Expert
Provide the technical or factual core. Stay within verified information. State assumptions and mark gaps.
Editor
Reshape the expert output into clear, plain structure. Remove padding. Ensure each section answers the brief.
Risk Assessor
Check for overreach, ambiguity, or missing information. Flag anything that exceeds the evidence. Recommend corrections.
Summariser
Produce a concise final version that reflects the corrections and stays within scope.
WORKFLOW
- Domain Expert produces the initial draft.
- Editor restructures and clarifies it.
- Risk Assessor reviews for accuracy and limits.
- Summariser produces the final answer.
OUTPUT CONTRACT
- Context
- Reasoning
- Conclusion
Rules
No invention. Mark missing information. Keep the answer within scope. Maintain plain structure.
6. Treat the context window as working memory #
As of April 2026, modern models dedicate roughly 200,000 to 1,000,000 tokens to representing your instructions. This space acts as working memory. It can hold definitions, constraints, examples, running notes, previous outputs, and a living brief. With this in place, the model behaves more like a stateful collaborator than a stateless assistant.
This working memory is what the model can track across prompts. When you define what belongs in this state, you save time. You do not need to repeat your requirements. The model carries them forward and maintains the structure you set.
7. Use agentic prompting patterns #
Static prompts assume a fixed path from question to answer. Modern systems are closer to small agents: they can plan, choose actions, call tools, and adjust their output based on intermediate results. This is often called agentic behaviour. The system selects and sequences actions to achieve an objective, rather than following a single linear path. Giving the model a workflow such as Plan → Act → Observe → Revise makes this explicit. In the planning phase, the model outlines what it intends to do, which tools it may need, and what a good outcome looks like. In the action phase, it carries out the steps, including any tool calls. In the observation phase, it inspects the result against the plan and the constraints. In the revision phase, it adjusts the answer and produces a clean final version.
Using a workflow saves time and reduces the need for repeated corrections. The final answer remains tidy. The planning and checking happen in the background or in short, structured notes, while the output stays compact and readable. You gain the benefit of step-by-step reasoning without having to sift through a long chain of output. Tool use fits naturally into this pattern. In the Plan step, the model decides whether tools are needed and why. In the Act step, it calls them. In the Observe step, it checks whether the tool results answer the question. If tools are not needed, the model should say so plainly and proceed with reasoning instead of forcing a tool into the workflow.
In this context, agentic means that the system behaves as a goal directed process. The model can plan, choose among available capabilities, and adapt its path based on intermediate results, rather than producing a single static completion from a prompt.
8. Make the model identify ambiguity before answering #
One of the most effective techniques is to require the model to surface all plausible interpretations before it attempts an answer. This forces the model to slow down, map the possible meanings, and avoid locking itself into the first pattern it detects. Large models tend to commit early unless guided.
This step also exposes hidden ambiguity. When the model lists the possible readings, you can see whether the task is underspecified, whether key terms are unclear, or whether the scope could be read in more than one way. This gives you a chance to correct the course before any work is done.
If more than one interpretation exists, the model should ask for clarification. This prevents mis-scoping, reduces the chance of error, and removes the need for the model to guess. Guessing is where most drift begins. The technique also improves consistency. When the model is told to check for multiple readings, it becomes less likely to produce answers that are confident but misaligned. It treats ambiguity as a signal to rather than a gap to fill.
In practice, this turns ambiguity into a controlled step rather than a source of error. The model identifies the forks in the road, confirms which path is correct, and only then proceeds with the task.
Doing this will save you a great deal of time.
9. Adapt prompts to the model #
Different models excel in different areas, and a good prompt acknowledges this rather than assuming a single uniform capability. Some models are strongest at structure: they produce clean sections, tidy formatting, and predictable layouts. Others are stronger at reasoning: they handle multi step logic, edge cases, and constraint checking with more stability. Some specialise in compression: they can distil long material into tight summaries without losing meaning. Others lean toward style: they generate fluent prose but may drift if not anchored.
A well designed prompt sets expectations that match these tendencies. If the model is strong at structure, you can lean on explicit output contracts. If it is strong at reasoning, you can give it more analytical work and tighter constraints. If it excels at compression, you can trust it with dense source material. If it is style heavy, you can counterbalance that with stricter rules and clearer boundaries.
The point is not to flatter the model. It is to shape the workflow so that the model’s strengths are used deliberately and its weaknesses are contained. This reduces variability, improves reliability, and produces output that is more consistent across your prompts.
Even if you stick to one model or one vendor, recognising that you may one day use a different system helps sharpen your expectations and improves the way you design prompts for the model you use.
In the same way customer service varies across vendors, so does AI interaction.
10. Include safety and uncertainty rules #
Modern models behave more reliably when you tell them not only what to do, but what to avoid. Negative guidance is a form of operational discipline. It removes entire classes of failure rather than correcting them after the fact.
Clear avoidance rules stop the model from drifting into areas that carry higher risk: speculation, overreach, sensitive claims, or invented detail. Without these boundaries, the model will often fill gaps with confident but unreliable material. Stating what must not happen is as important as stating what must.
Escalation rules serve a different purpose. They tell the model when to stop and hand control back to the user. This is essential for tasks involving uncertainty, missing information, or sensitive domains. When the model knows when to escalate, it avoids guessing, avoids false precision, and avoids treating ambiguity as something to be patched over.
Uncertainty handling is another pillar. Models respond well when instructed to mark unknowns, list assumptions, and request clarification instead of improvising. This keeps the work inside the evidence and prevents the model from manufacturing answers to maintain fluency.
Sensitive topics require explicit treatment. If you tell the model how to handle them, it will follow the procedure rather than rely on its own processing. This reduces variability and keeps the output aligned with your standards rather than the model’s defaults.
Taken together, these measures form a small operational framework. They are not decoration. They are the guardrails that keep your AI output predictable, bounded, and safe to use in structured workflows.
A modern prompt template #
A compact structure that works across the latest models:
SYSTEM FRAME
You are an analytical engine. You work with steady reasoning, cautious claims, and plain structure. When the request is unclear, you and ask
for what is missing. You avoid invention and stay within the boundaries set
for you.
ROLES
Domain Expert: Provide the factual and technical core. State assumptions and mark gaps.Editor: Reshape the material into clear, plain sections. Remove padding and repetition.Risk Assessor: Check for overreach, missing information, and unwarranted certainty. Flag issues.Summariser: Produce a concise final version that reflects all corrections and stays within scope.
TASK
Describe the task in one or two sentences. State the objective, the audience, and any hard limits on scope.
OUTPUT CONTRACT
Produce the answer in the following sections:
- Context
- Reasoning
- Conclusion
UNCERTAINTY AND AMBIGUITY
- List plausible interpretations of the request before answering.
- If more than one interpretation exists, ask for clarification instead of guessing.
- State what information is missing and how it affects the answer.
- Mark assumptions clearly and keep them minimal.
SAFETY, LIMITS, AND ESCALATION
- Do not invent facts. If evidence is missing, say so.
- Avoid speculation, sensitive claims, and advice outside the brief.
- Escalate to the user when the task is out of scope or under specified. Explain why and what is needed.
- Treat sensitive topics with extra care. Prefer to mark limits rather than improvise.
WORKFLOW (AGENTIC) Plan: Identify the goal, constraints, and any tools or references that may be needed.Act: Produce the initial answer according to the output contract.Observe: Review the draft for clarity, accuracy, scope, and alignment with the rules.Revise: Produce a refined final version that corrects issues and tightens the structure.
STYLE RULES
- Keep the final answer concise, structured, and free of padding.
- Use only British English.
- Do not include hidden reasoning or chain of thought in the final answer.
BEHAVIOUR
These rules apply to every response in this session unless explicitly revoked. If the request conflicts with these rules, explain the conflict and ask how to proceed.
Having the AI Manage the Prompt Template #
You managing the above template is too much. Therefore, once you have it in a form you are happy with and which is effective for your needs, you tell the AI the template and before you start your session you prompt with this:
Summary #
Modern prompting is not about clever wording. It is about defining the system, setting the output contract, controlling the workflow, managing ambiguity, and using the context window as working memory. This will help produce reliable output from modern AI systems.
Ten simple AI workflows that save minutes each day and compound into hours each week, helping people work more efficiently.An explanation of how large language models actually function and why they should not be treated as miniature humans.Guidance on using AI safely and effectively, grounded in recent examples of misuse and emerging best practices.
If this piece was useful, you’ll appreciate the free Phroneses newsletter — clear thinking on engineering leadership, organisational clarity, and reliable systems. Practical, honest, and built for people who care about doing the work well.
I work with leaders and teams on clarity, capability, and momentum.
Work with me → 1. Start with the system, not the request2. Define the output contract3. Use decomposition as a control mechanism4. Add a self-critique loop5. Stack roles for higher-quality output6. Treat the context window as working memory7. Use agentic prompting patterns8. Make the model identify ambiguity before answering9. Adapt prompts to the model10. Include safety and uncertainty rulesA modern prompt templateHaving the AI Manage the Prompt TemplateSummaryRelated WorkTable of Contents