Feature Driven Development - Vibe Coding with VS Code for Copilot Studio
Build Copilot Studio agents feature-by-feature using the VS Code extension and AI-assisted development
- VS Code Extension for Copilot Studio
- Feature Driven Development: one feature at a time
- Spec-first, intent-driven agent building
- GitHub Copilot assists with prompt writing
- Full build cycle without leaving VS Code
Watch the session
Open on YouTubeAbout this session
Feature Driven Development applied to Copilot Studio means you never write a system prompt before you have a feature list. Name each thing the agent should do, one sentence each - that list is your acceptance criteria. Then you implement and test one feature at a time using the VS Code Extension for Copilot Studio, with GitHub Copilot helping draft prompt sections and action configurations. The result is 'vibe coding': you express intent, iterate by feel, and ship agents that do exactly what you specified - built entirely in VS Code without touching the maker portal.
Inside the demo
- Install the VS Code Extension for Copilot Studio and connect to a Power Platform environment without leaving the editor.
- Write a three to five line feature list before touching the system prompt - these become your test cases.
- Use GitHub Copilot inline suggestions to draft each feature's prompt section, keeping features isolated from each other.
- Test each feature in the VS Code test pane immediately after adding it - fix and iterate before moving to the next one.
- Stack features progressively until the full agent spec is covered and every feature passes in the test pane.
- Deploy directly from VS Code to Copilot Studio and publish to Teams without switching to the maker portal.
Prompts to try
Point an agent at your own Process Mining data and adapt these:
- What can you help me with today?
- Walk me through [the agent's main capability].
- What happens if I ask about something outside your scope?
Build it yourself
Install the VS Code Extension for Copilot Studio
Search for 'Copilot Studio' in the VS Code extensions marketplace. Sign in with your Microsoft 365 account and select your Power Platform environment.
VS Code extension for Copilot StudioWrite your feature list first
Before opening a prompt editor, list three to five things your agent must do - one sentence each. This is your spec and your test suite. No feature list means no prompt.
Draft each feature's prompt section with GitHub Copilot
For each feature, use GitHub Copilot in VS Code to draft the system prompt section for that specific behavior. Keep each feature's instructions isolated - don't mix responsibilities in one block.
Authoring agents in VS CodeTest feature by feature in the test pane
After adding each feature to your agent's system prompt, open the test pane in VS Code and test only that feature before moving on. If it fails, fix the prompt before stacking the next capability.
Deploy and publish from VS Code
When all features pass, use the extension to deploy your agent to Copilot Studio. Publish to Microsoft Teams or other channels directly from the extension.
Publish to Microsoft Teams
Slides
Resources
Recordings
- Microsoft Community Learning - featured recording→The MCL featured recording of the Vibe Coding session.
- Power Platform Community Call - February 2026→The original community call recording at the demo start timestamp.
Resources from the session
- Playbook Guide→The step-by-step Feature Driven Development playbook for Copilot Studio.
- Workflow diagram (slides)→The Vibe Coding workflow diagram from the session slides.
- Full demo flow diagram→The complete Feature Driven Development flow used in the demo.
VS Code Extension for Copilot Studio
- Authoring agents with the VS Code extension→Official Microsoft Learn documentation for the extension.
From the speaker
Elliot Margot
Microsoft MVP - M365 Copilot & Copilot Studio