How to stop your AI from doing things in the wrong order
In my last post, we traded mere prompting for architecture. We moved away from the “chat-and-hope” method and focused on the real work: organizing logic into semantic folders and writing instruction-based Markdown files. Having a solid structure is a huge win, but your agents still need an order of operations. This is where we tackle Sequence.
If you ask an AI to “update the maintenance logs for next week,” it might try to schedule a mechanic before checking if the bus is actually in the depot. Because AI agents don’t naturally follow an alphabetical or chronological order when browsing your skills, you need a dedicated Planner to define the workflow.
In this post, we’re building the Planner Skill — the Markdown file that contains the logic for the AI to understand exactly in which order to execute the skills found in your other files.
What is a Planner?
A Planner is a specialized agent whose only job is to look at your request, survey your available skills, and write a step-by-step “to-do list” before taking any action.
Without a planner, your agent has no way to prioritize which instructions to follow first. With a planner, you give the system a central logic hub…
