← Back to concept explainers

Concept Fable

Planner

Conclusion first:The planner is responsible for breaking user goals into executable steps, subgoals, constraints, and dependencies, and for adjusting the plan when new information appears. In an enterprise Agent, the planner cannot just write a pretty task list; it must also clarify which steps can run in parallel, which require approval, which depend on external systems, and how to retry or reroute after failure. Its value is reducing chaos in the execution phase, so that executors, tools, human approvals, and state management all advance around the same plan.

Planner · Agent architecture

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The night before the canal repair, that map without a shovel

Nanpo Village irrigated its fields from an old canal. In the past the canal was short, and the village chief only had to shout once: who digs the soil, who carries the stones, who opens the gate—everyone just knew. Back then a light rain could soak the fields, and no one felt the need for complicated arrangements.

Later the village expanded to three slopes. The upper slope lacked water, the lower slope feared flooding, a section of canal wall in the middle had come loose, and the granary required that transport not be interrupted for three days. The old method was still to shout for people on site after work started, patching first wherever the noise was loudest.

The first round of canal repair was lively. More than a dozen shovels went into the ground at the same time, and as a result, just as the upstream was dug deeper, the downstream was blocked by mud; the grain carts got halfway and found that temporary piles of earth blocked the road; the gate operator heard shouting from both sides and did not know whether to release water or shut it off.

The village chief came up with a simple patch: line up all tasks in a single column by urgency. But everyone said their own matter was urgent—the people at Songqu Wall said it would collapse if not repaired, the granary said delaying the grain would cause losses, and the downhill farmers said releasing more water would flood the seedlings. That ranking table quickly turned into a list of arguments.

An old surveyor did not immediately hand out shovels. He first walked along the canal for a whole day, mapping water levels, road junctions, fields, workers, tools and the boundaries that must not be touched. That evening, he broke the big goal into several stages: first secure the grain route, then reinforce the canal walls, then open the sluices in batches, and finally repair the downhill drainage outlets.

He also wrote conditions beside each section: if it rains at night, pause gate opening; if the stone has not arrived, first do temporary support; if the downstream water level exceeds the red line, immediately switch to the side channel. Each step had inputs, preconditions and a backup path after failure.

The next day, the villagers found that this map had not dug a single shovel of soil for them, yet it gave every shovel of soil a place. The workers knew why they were waiting and when to switch tasks; the gate opener no longer listened to whoever shouted loudest, but looked at the water level and the previous step's result.

Three days later, the old canal was repaired. Only then did the village chief admit that the real savior was not that the surveyor was stronger than everyone else, but that before acting he laid out the goals, sequence, constraints, and variable conditions. From then on, whenever the village faced a major project, they did not rush to start. They first drew a route that could be executed, modified, and held accountable, then handed the shovels to the right people. Later, when the old surveyor left, the village still did things according to the method. New projects first wrote goals, then listed resources, sequence, constraints, trigger conditions, and backup routes; after completion they reviewed which judgments were wrong. The villagers found that a plan is not about nailing down the future, but about letting everyone know which step to change when change appears. Without this modifiable route, the more diligent the people, the more chaotic the site.

Reveal

This story is about: the planner

The planner is responsible for breaking user goals into executable steps, subgoals, constraints, and dependencies, and for adjusting the plan when new information appears. In an enterprise Agent, the planner cannot just write a pretty task list; it must also clarify which steps can run in parallel, which require approval, which depend on external systems, and how to retry or reroute after failure. Its value is reducing chaos in the execution phase, so that executors, tools, human approvals, and state management all advance around the same plan.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Old Canal Project: an enterprise task spanning systems and roles
  • Shouting for people on the spot: ad-hoc decisions and local optimization without a planner
  • Urgency ranking table: the naive fix of queuing only by surface priority
  • Old surveyor: Planner, first understand goals, resources, constraints and risks
  • Segments on the map: task decomposition, step sequencing and dependencies
  • Rain, stone that has not arrived, the water-level red line: dynamic conditions, external dependencies and exception branches
  • Give the shovel to the right people: the planner outputs the plan, and the executor and tools handle implementation
  • A route that can be modified and held accountable: enterprise Agent plans need to be auditable, recoverable, and adjustable

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

executororchestrationworkflowstask decompositionplan-and-execute agents

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号