Every morning an AI agent builds my daily brief. It pulls the accounts, the follow ups due, and the open tasks in my CRM, and puts them in front of me before the day starts.
For a while I was doing a lot of my work twice. I would ask the agent to mark a task complete, move on, and find the same task still open later. So I closed it by hand. Then I caught another one. The duplicate steps kept stacking up.
The cause was one line in my own instructions. When I first set up the brief, I wrote that the agent was never allowed to edit the CRM. I meant it as a safety rail, and then I forgot it was there. The agent did not forget. Every time I asked it to close a task, the rule I had written won over the request I was making.
It also told me the tasks were closed. The brief reported the work as done, and nothing in the CRM had changed. Nothing in my instructions required it to check that a change had actually landed, so it never checked.
My orders were the problem. Its report made the problem invisible.
That is the part of working with AI nobody warns you about. The tool is rarely the hard part. The hard part is stating what you actually want: the purpose, the end state, and the limits. And then making sure those pieces do not quietly cancel each other out.
The military has a name for that skill. It is called intent, and the military spends years teaching it.
A Marine operations order does not just list tasks. It carries the commander's intent: why the mission matters and what the end state looks like. It also separates two kinds of limits. Constraints are things you must do. Restraints are things you cannot do. Part of writing a good order is checking that no restraint makes a task impossible, because a unit that receives contradictory orders either stalls or picks one and hopes.
I had written an order with a restraint that blocked the task I kept assigning. Any lieutenant who has had an order sent back for that reason would recognize the mistake immediately.
But there is an important difference between my agent and a Marine. A good corporal handed my instructions would have stopped and asked, "You told me never to touch the CRM. Do you want these closed anyway?" That question comes from shared context. The corporal knows how the unit runs, how the boss thinks, and when a rule was meant as a guardrail and not a wall.
An AI has none of that. It does not know which of your instructions you care about and which you wrote in a hurry three weeks ago. It resolves every gap and every conflict with its best reading of what you wrote, and it does so with total confidence.
That makes intent harder to write for a machine, not easier. Everything a unit's culture used to carry now has to be on the page.
For operations leaders, this is where the bottleneck has moved. As routine work shifts to automation, the job is less about doing the work and more about defining it well enough for something else to do it. That means a clear purpose, a defined end state, and limits that do not conflict. The people who struggle with AI are rarely struggling with the software. They are finding out they never had to put their intent into words before, because a capable human on the other end filled in the gaps.
The military trains that skill on purpose. A young officer learns to write intent clearly enough that a team can act on it without calling back, and to understand the mission two levels up well enough to make the call their boss would make.
Military service does not guarantee the skill, though. Some people came up under commands that micromanaged every move and never practiced writing intent. Others learned it deeply. On paper, both resumes look the same. That is a fit question, and one conversation can answer it.
Ask a candidate for the intent behind the last major task they led. Not what they did. Why it mattered, what done looked like, and what they would have let their team change without asking. Someone who learned mission command answers in about thirty seconds. Someone who did not will describe the steps.
My agent did not need better software. It needed a better order.