05. Clear Articulation, Curiosity, and the Art of Prompting

Published 2026-09-14

Core Theme: AI does not reward cleverness; it rewards clarity. If you cannot question what you need with the unquenchable curiosity of a small child — and then translate it into unambiguous words — even the most powerful supercomputer in the world cannot give you the result you want.

This chapter is the public-officer edition of CM-04: Articulation, Curiosity, and the Art of Prompting (Prompt Architecture). The general explanation is there; this page keeps what changes when the work is a public office.

Why is a curious three-year-old the best model for prompting?

The most common question asked in any session with officers is some version of this: what coding do I need to learn to become a good prompt engineer?

Figure 5.1: The Articulation Test — how vague curiosity evolves into precision prompt architecture (illustrated through the Sigiriya hydraulic engineering inquiry).

Look closely at that Sigiriya sequence, because it is not random chatter. It is a systematic exploration of one scenario: the phone falls, the phone breaks, the phone hits the rock, the wind intervenes, the child intervenes, the child falls too. Each question opens a branch the previous answer created. No adult officer habitually explores a problem that thoroughly, and it is precisely the pattern the next chapter will dignify with the name tree-of-thought prompting.

That training was always a loss. It is now a measurable professional disadvantage, because the interface to the most powerful tool on an officer's desk is a question.

To win in the presence of artificial intelligence, the buried curiosity has to be dug back up. Prompting is nothing more exotic than this: looking at a problem with curiosity, hunting for its root, and asking a continuous, logical chain of questions. A person who questions that way is already an excellent prompter and usually does not know it.

There is one difference between the child and the professional, and it is the whole subject of this chapter. The child asks and asks without needing precision, because a parent fills in the gaps, guesses the intent, and answers the question that was meant rather than the one that was asked. A model does not do that. It answers what you actually wrote. So the curiosity has to be paired with something the three-year-old does not have — exact expression — and that pairing is what the rest of this chapter builds.

What is articulation, and why does it decide your results?

The Canadian psychology professor Dr. Jordan B. Peterson has put the case for this skill as well as anyone, and for the public officer of the AI age his formulation reads almost as a specification:

Figure 5.5: The Architecture of Articulation — moving from chaotic intuition through linguistic discipline to machine-executable directives.

"A person becomes more articulate by choosing their words with great care, by practicing saying what they believe to be true, by reading and writing deeply about their own thoughts, and by treating the word with immense respect. The clearer your ideas, the more powerful your thinking; and the more powerful your thinking, the more you become a victor before the world."

The most powerful person of the AI age, then, is not the one who memorised computer code. It is the person with the articulate power to tell the machine exactly what they need — in precise words, with zero ambiguity.

Which five human skills actually power a prompt?

Getting a flawless official document out of a model depends on five capacities, and every one of them resides not in the machine but in the officer. Figure 5.6 sets them out.

Figure 5.6: The 5 Essential Human Skills of Prompt Engineering — critical reading, explicit writing, structured logic, critical thinking, and precise articulation.

Structured logic: sequencing the work

Do not demand a complex administrative task in one lump. Decompose it into a logical sequence of sub-routines: review, then eligibility verification, then calculation, then recommendation.

The reason this works connects back to the mechanics in Chapter 03. A model generates each part of its answer conditioned on what it has already produced, so a task broken into ordered stages gives it correct intermediate ground to build on. It also gives you checkpoints — you can catch an error at the eligibility stage rather than discovering it inside a finished recommendation.

Precise articulation: arranging the prompt

Finally, arrange the role, the context, the constraints and the format so cleanly that the machine has no room to misunderstand. This is the skill the remaining sections of this chapter are devoted to, because unlike the other four it has an actual structure that can be taught.

What makes an instruction precise?

Ambiguity is not a stylistic weakness in public administration. In the public service a single ambiguous word in a letter can cost a citizen their land title or their pension, or open the road to a High Court case. The four principles in Figure 5.7 are how ambiguity gets removed from a prompt before it does that damage.

Figure 5.7: The Four Pillars of Precise Articulation in Prompt Engineering — Zero-Ambiguity, Negative Constraints, the Intent-Action-Result (IAR) audit model, and Semantic Precision.

Pillar three: the Intent–Action–Result audit

Intent asks what the institutional purpose actually is — for example, "persuade the Ministry of Finance to approve the budget allocation." This is the part most prompts omit entirely, and its absence is why so much output is technically responsive and strategically useless. A document written to inform reads differently from one written to persuade, and the model cannot infer which you needed.

Action asks what specific mechanical task is being delegated: "compare the expenditure reports of the 3 attached Divisional Secretariat offices." Narrow and checkable.

Result asks what form the finished document must take: "a one-page executive summary with a clear approve / do not approve recommendation." Naming the deliverable prevents the most common disappointment of all, which is receiving a perfectly good piece of work in the wrong shape for the meeting it was needed for.

Pillar four: semantic precision

The last pillar is the one that feels like a trick and is in fact a consequence of the architecture described in Chapter 03. Using your field's exact technical or legal terminology, rather than everyday language, anchors the model's attention in the relevant expert region of its training data.

The effect is easy to observe. "Write good software code" returns something serviceable and generic; "write a stateless functional component in TypeScript, using memoization for efficiency" returns work of a different order. "Make a good promotional plan for farmers" returns platitudes; "using the Jobs-to-be-Done framework, identify the core struggle of the rural farmer applying for the fertilizer subsidy, and design a communication strategy that speaks to it" returns something you could take into a meeting.

How is a complete prompt structured?

A prompt built to handle the public service's complex material — a case file, a gazette, a financial report — is not a sentence or two. It is a carefully designed work of architecture, with five distinct layers, each doing a job the others cannot.

Figure 5.8: Prompt Architecture (Full Architecture) — Role, Context, Task, Constraints, and Output Format.

Layer one: role

The expert identity the model is to adopt. "Act as an Additional Secretary with 20 years in the Sri Lanka Administrative Service, expert in the Establishments Code and government financial regulations."

One sentence, and it sets the vocabulary, the priorities and the standard of evidence for everything that follows. The specificity is doing the work — twenty years and a named code, rather than "an expert."

Layer two: context

The background the model cannot know: the situation, the relevant circular numbers, the parties involved. "A dispute has arisen between the local council and the traders' association over the removal of unauthorized shops in the Divisional Secretariat area. Under Circular No. 12 of 2024…"

Layer three: task

The specific operation to perform, stated as an instruction. "Draft a 5-step mediation action plan to bring the two parties to a settlement."

Layer four: constraints

What must not be done, the legal limits, the length. "Propose nothing that exceeds the powers granted by the Local Government Act. Do not include assumed laws. Limit the response to 300 words."

The middle instruction is the one to notice. "Do not include assumed laws" is the negative constraint from Pillar two doing exactly the work it exists for — closing off the model's most dangerous habit before it starts, rather than catching it in review.

Layer five: output format

The shape the answer must arrive in. "Present with headings, numbered steps, and a closing Markdown table of [Risk | Responsible Officer | Remedy]."

Specifying format is not fussiness about presentation. That closing table forces a named responsible officer and a remedy against every risk — which means the structure you asked for has quietly required the model to produce content it would otherwise have left vague.

Why articulation is the skill worth practising

The encouraging part is that articulation is a practised skill rather than a talent, and it improves with use in a way most skills do not: every clear prompt you write is a small exercise in stating exactly what you want, and it compounds. For a public officer, practising precise expression in file work and in commanding these tools does double duty. It gets better work out of the machine today, and it makes you an administrator without equal in your service.

In the next chapter, building on these principles, we study, hands-on, the advanced prompting methods used in the public service and the Divisional Secretariat "Promptathon" model.