Having your AI agent come up with a plan before start coding, has helped me a lot in my agentic development workflow. It allows me to verify the steps the agent will take and allowed me to avoid that the agent goes down the wrong path.
To help you with this, Visual Studio got a ‘plan mode’ that once enabled allowed the agent to create a plan. I really liked the feature, the only problem is that is what not always obvious when the agent decides to create a plan and when it just starts executing.
To tackle this issue, the plan mode in Visual Studio has evolved to a separate plan agent, similar to what we have in VSCode.
Plan first, code second
If you have never heard about plan mode or the plan agent, it is a dedicated mode in Copilot Chat that focuses entirely on understanding what you want to build before touching a single file. Instead of jumping straight to implementation, it asks clarifying questions, reads your codebase using read-only tools, and drafts a detailed implementation plan for you to review.
Think of it like pair programming with a very thorough senior dev who insists on talking through the approach before opening their editor.
How it works
Here's the basic flow:
- Pick "Plan" from the agent picker in Copilot Chat and describe what you want to build. You can be vague ("refactor the payment module") or specific — the more context you give, the sharper the plan.
- Copilot explores and asks questions. It scans your codebase read-only and flags anything ambiguous. If the task is straightforward, it'll skip straight to drafting.
- You get a plan to review. Not code — a plan. You can ask Copilot to rethink an approach, add edge cases, split a step into smaller pieces, or reconsider which files to touch. Iterate until it matches your vision.
- Edit the plan directly. Every plan is saved as a markdown file at
.copilot/plans/plan-{title}.mdin your repo. Open it in the editor, tweak it yourself, share it with your team for a review — it's just a file.
- Hit "Implement plan" when you're ready. Only then does Copilot switch into Agent mode and start making actual changes, working through the plan step by step while you watch in real time.
No surprises. No undoing a dozen edits. You stay in control.
Why I think it is a must in every developer workflow
The old problem with agentic AI tools isn't that they're bad at coding — it's that they're too eager. They optimise for doing rather than understanding. The Plan agent puts a deliberate checkpoint between your prompt and the first file change, which is where a lot of the real thinking should happen anyway.
It's also worth noting the .copilot/plans/ markdown files aren't just a nice-to-have. They make AI-assisted work reviewable and shareable in a way that a chat history isn't. You can commit a plan, get feedback from teammates, and have a clear record of the intended approach before any implementation exists.
Give it a try
The Plan agent is available now in Visual Studio. Next time you're about to kick off something non-trivial — a new feature, a refactor, a big integration — try reaching for Plan instead of Ask or Agent mode. The extra few minutes spent aligning on the approach will almost certainly save you more time on the back end.
More information
Plan Before You Build: Introducing the Plan agent in Visual Studio - Visual Studio Blog