Apr 6 • General discussion
The Anatomy of a Plan
In prompt engineering, there are specific components that separate a great prompt from a mediocre one. Planning works the same way. Most people write to-do lists and call them plans. A real plan is a model of reality that produces a specific outcome under specific conditions. Here are the 10 components that make it work.
1
Objective
The single outcome the plan exists to produce. Not a list of things to do — one measurable end state. If you cannot write it in one sentence, the plan is not scoped yet. Everything else in the plan exists to serve this one thing.
2
Constraints
What the plan must not violate. Time, budget, tools, dependencies, non-negotiables. Constraints defined upfront prevent the mid-execution pivots that collapse a plan entirely. A plan without constraints is a wish with steps attached.
3
Context
What is true right now that the plan has to account for. The current state of the system, the environment, relationships, known blockers. A plan built without context is not a plan — it is a guess formatted to look like one.
4
Assumptions
What you are treating as true but have not yet verified. Explicit assumptions are recoverable when they turn out to be wrong. Implicit assumptions are landmines — they detonate mid-execution when you least expect them. Write them down. Every one of them.
5
Sequenced steps
Ordered actions with clear dependencies — not a flat list, but a chain where each step has a defined input and a defined output. The sequence is what makes a plan executable instead of just readable. If the order does not matter, you do not have steps, you have a checklist.
6
Decision points
Forks in the path where the next action depends on an outcome. Good plans identify these in advance so you are not improvising under pressure when reality diverges. If your plan has no decision points, you are assuming the path is linear. It never is.
7
Success criteria
How you know each step is complete, and how you know the whole plan is done. Without this, "done" is subjective and execution drifts. Criteria must be observable — something you can point to and verify, not something you feel your way toward.
8
Failure modes
The most likely ways the plan breaks. Not every edge case — the top two or three failure paths with a stated response for each. Planning for failure is not pessimism. It is the difference between a plan that adapts and one that collapses the moment something goes wrong.
9
Owner or executor
Who or what executes each step. In solo work this is obvious. In team or agentic contexts it is critical — a step with no assigned executor does not get done, it gets assumed. Every action needs a name attached to it, whether that name is a person, an agent, or a system.
10
Review surface
When and how the plan gets interrogated before full execution begins. A plan you cannot review before it runs is a liability. Build in a checkpoint — a moment where someone or something reads the plan critically and has the authority to stop it. This is not overhead. This is the mechanism that makes every other component worth writing.
The three components most plans are missing
Assumptions — people skip them because writing them down feels like admitting uncertainty. Decision points — people pretend the path is linear because branches feel complicated. Failure modes — people confuse optimism with planning. These three omissions account for most plan failures. Not bad execution. Bad architecture.
A plan is not a to-do list. It is a model of reality that produces a specific outcome under specific conditions. Build it like one.
Which of these 10 components is your plan usually missing?
5
14 comments
The Anatomy of a Plan
powered by
skool.com/ai-for-life-3967
Practical AI training for work and life. Hands-on lessons with Claude,
ChatGPT, and automation tools. Built for people ready to use AI.
Suggested communities
Powered by