AI Fluency and the 4D Framework: Delegation, Description, Discernment, Diligence
Anthropic's 4D framework for AI fluency, with practical examples of task delegation, prompt writing, code review, and responsible use of AI-generated work.
Give two people the same AI tool and the same task, and the results can be worlds apart. I see it every week: same model, same codebase, same deadline, and yet one session ends with a clean plan and a reviewable diff while another ends with an hour of back and forth and a result nobody is happy with. For a long time I assumed the difference was prompting skill. It turns out prompting is only about a quarter of the story.
The other three quarters have names too. Anthropic, together with Prof. Rick Dakan (Ringling College of Art and Design) and Prof. Joseph Feller (University College Cork), published the AI Fluency Framework: four interconnected competencies that make our interactions with AI effective, efficient, ethical, and safe. They call it the 4D framework, for the 4 Ds: Delegation, Description, Discernment, and Diligence. I took their course, AI Fluency: Framework & Foundations, and earned the certification, and what follows is the framework as I have come to use it in daily work.
What is the 4D framework for AI fluency?
The 4D framework is Anthropic's model of AI fluency: the four competencies of Delegation, Description, Discernment, and Diligence that together make working with AI effective, efficient, ethical, and safe. The point of the framework is that using AI well is a learnable skill set, and that prompting is only one of the four skills.
One note for anyone who arrived here from a different "4D": the name is also used by frameworks in sustainability and curriculum design. This one is specifically about how people work with AI, and it comes from Anthropic and the two professors above.
What are the four competencies in the 4D framework?
The four competencies are Delegation, Description, Discernment, and Diligence, and each one covers a different part of the same working relationship.
| Competency | What it means |
|---|---|
| Delegation | Deciding whether to involve AI at all, what to hand over, and what to keep for yourself. |
| Description | Telling it clearly enough to act: the product you want, the process to follow, and how it should behave while working with you. |
| Discernment | Judging what comes back, both the output itself and the reasoning that produced it. |
| Diligence | Owning what you ship, from the data you paste in to who answers for the result. |
Each one is worth more than a row in a table, so what follows takes them one at a time, with what each looks like in a normal working day.
Delegation: decide whether, when, and how
Delegation is the competency of setting goals and deciding whether, when, and how to engage AI at all. That sounds obvious until you notice how rarely we actually do it. The tool is open, so we type into it. The framework asks for a small pause before that: what am I trying to achieve, which parts of this work need my judgment, and which parts can I hand over?
In my own work the clearest example is the split between planning and implementation. When I bring an agentic tool like Claude Code into a piece of work, I now start by asking for a plan: break the deliverable into small stories, define acceptance criteria, list the risks and assumptions, and stop. The implementation gets delegated story by story afterwards. I wrote about this workflow in detail in my post on TDD with Claude Code, and at its heart it is a delegation decision: the shaping of the work stays with me, the typing goes to the agent.
Delegation also means knowing what not to hand over. Decisions with long shadows, like architecture choices, naming things that a team will live with for years, or anything where accountability sits with me, get AI as an advisor, not as a decision maker. That is augmentation, one of the three interaction modes covered below, and choosing it deliberately is a delegation skill as well.
Description: say what you actually want
Description is the competency people usually mean when they say "prompting": effectively describing your goals so the AI produces useful behavior and output. But the framework is broader than clever phrasing. You are describing three things at once: the product you want, the process the AI should follow, and the way you want it to behave while working with you.
The difference is easy to see in practice. Here is a description I would have typed a couple of years ago:
Create a todo app with Angular.
And here is what a fluent description of the same goal looks like:
Planning mode only. Do not edit files yet.
I want to create a todo app with Angular.
First, break the deliverable into small composable stories. For each story, define the goal, acceptance criteria, expected files to create or modify, dependencies, required tests, risks, and assumptions.
Stop after the plan.
The second version describes the product (a todo app, shaped as stories), the process (plan first, no file edits), and the behavior (stop and wait for review). Every sentence closes a gap the AI would otherwise fill with an assumption. Actually, that is the simplest test I know for a good description: read it back and count the guesses it still leaves open. The AGENTS.md files in Do UI frameworks still matter when AI writes the code? are the same competency written down once, so every session starts with those guesses already closed.
Discernment: the review is the work
Discernment is accurately assessing the usefulness of what the AI gives you, and it is the competency that separates using AI from benefiting from it. Models produce fluent, confident output whether they are right or wrong, therefore the confidence of the answer tells you nothing about its quality. Someone has to actually judge it, and that someone is you.
This matches my engineering days exactly. The bottleneck has genuinely moved from writing code to reviewing and validating it. An agent hands back a summary of what it changed, and the real work starts there:
- Does this diff do what the story asked for?
- What assumptions did it quietly make?
- Do the tests prove the behavior, or do they just pass?
- Is this consistent with how the rest of the codebase works?
Discernment also applies to the process, not only the product. Sometimes the output looks fine but the way the AI got there is worrying, like reasoning that skipped a constraint you stated, or a step where it invented a fact to keep moving. Catching that changes what you do next, which is where discernment feeds straight back into description: you refine what you asked, the AI produces a better result, and you assess again. The course calls this the description and discernment loop, and it is a good name for what a productive AI session actually feels like. The same judgment applies outside code: when I generate an image locally, the skill crops the risky regions and inspects them before I accept anything, and that pass is described in free local AI image generation on a Mac.
Diligence: own what you ship
Diligence is taking responsibility for what we do with AI and how we do it. Of the 4 Ds this is the one I care about most. I have built software for one of Greece's largest insurers and an e-invoicing integration for the Greek tax authority, and that kind of work teaches you early that "the AI wrote it" is not a defense anyone will accept. If AI helped produce the code, the document, or the decision, the accountability still belongs to the human who shipped it.
In practice, diligence looks unglamorous. It is checking that the data you paste into a tool is data you are allowed to share. It is being transparent with colleagues about where AI was involved in a piece of work, so they can calibrate their own review. It is knowing what the systems you rely on do with your inputs. And it is refusing to let speed become the excuse for skipping the human check on anything that matters.
I find this framing kinder than the usual compliance language, because it makes responsibility a skill you practice. The framework's own definition of fluency puts ethical and safe right next to effective and efficient, and in my experience the people who treat those as one package are also the ones who get the most out of the technology, since trust is what allows anyone to say yes to more AI, not less.
Automation, augmentation, agency: the three ways of working with AI
The framework also names three modes of interacting with AI, and they are worth knowing by name because they explain a lot of everyday frustration. Automation is AI executing a specific task you instruct it to do. Augmentation is you and the AI thinking through something together as partners. Agency is configuring AI to perform future work on your behalf.
Most of the friction I see comes from mixing these up: asking for a one-shot answer when the task needed a conversation, or giving an agent free rein on work that needed supervision. The four competencies are what let you move between the modes on purpose, and delegation in particular is the act of picking the right mode before you type anything.
The 4 Ds in practice: one loop
The 4 Ds are not a checklist you complete once. Delegation decides what to hand over, description hands it over well, discernment judges what comes back, and diligence makes sure the whole exchange is something you can stand behind. In a real session you cycle through all four in minutes, and each one you are weak in caps the value of the others. Amazing descriptions cannot save a task that should never have been delegated, and sharp discernment cannot fix responsibility that nobody took.
Here is the whole framework compressed into the questions I actually ask in a session:
| Competency | The question it answers | What it looks like in a real session |
|---|---|---|
| Delegation | Should AI do this at all, and which part? | I ask for a plan and keep the architecture decisions; the typing goes to the agent. |
| Description | Did I say what I actually want? | Product, process, and behavior all stated: "planning mode only, stop after the plan." |
| Discernment | Is what came back actually good? | I read the diff for quiet assumptions and check the tests prove behavior. |
| Diligence | Can I stand behind shipping this? | The data I pasted was mine to share, and the work says where AI was involved. |
Also worth saying plainly: this is learnable. None of it requires a technical background, which is exactly the point, since the people who need these skills now include everyone whose work touches a model, not only engineers.
Is Anthropic's AI Fluency course worth it?
Yes, and it costs nothing. Anthropic offers free courses on working with AI, and the one this post is built on, AI Fluency: Framework & Foundations, ends with a final assessment and a certificate of completion. It is the course I took and the certification I hold, and it is a few well-spent hours: the framework vocabulary alone changes how you notice your own habits with these tools. The trailer gives you a quick feel for it:
Frequently asked questions
What is not one of the 4 Ds in the AI Fluency framework?
The four competencies are Delegation, Description, Discernment, and Diligence, and nothing else. Any other D-word you might meet in a quiz, like documentation, data, or deployment, is not part of the framework.
What is the primary focus of the Diligence competency?
Responsibility. Diligence is about taking ownership of what you do with AI and how you do it: checking that the data you share is data you are allowed to share, being transparent with colleagues about where AI was involved, and staying accountable for the result whoever or whatever produced it.
Who created the 4D framework?
Anthropic published the AI Fluency Framework together with Prof. Rick Dakan of Ringling College of Art and Design and Prof. Joseph Feller of University College Cork, and teaches it through the free course AI Fluency: Framework & Foundations.
What is AI fluency?
AI fluency is the ability to work with AI effectively, efficiently, ethically, and safely. In the 4D framework it is built from the four competencies of Delegation, Description, Discernment, and Diligence, practiced together rather than in isolation.
The takeaway
Which brings me back to the two sessions from the start, the clean plan and the hour of back and forth. The distance between them was four skills with names, and you can start practicing every one of them in your very next session.
