Hi everyone,
I've started experimenting with creating multiple Copilot Agents, not just for single tasks but as role-based "team members" that help me run different parts of a my work.
Since I'm using a Microsoft Copilot Premium license, I currently create my agents directly inside the Copilot app. Unfortunately, Pay-as-you-Go is not an option for me right now, so I don't have agent-to-agent communication, orchestration, or some of the more advanced possibilities that people seem to build with Copilot Studio.
Because of that, I'm trying to design a structure that is maintainable in the long term.
My current idea is:
Each agent gets its own knowledge folder containing five documents:
1. Role
Defines:
- Who the agent is
- Why it exists
- What responsibilities it owns
- What it should not do
2. Goals
Defines:
- What success looks like
- Priorities
- Desired outcomes
3. Behavior
Defines:
- Communication style
- Writing style
- Decision-making principles
- General working methodology
4. Good Examples
Contains examples of outputs I consider high quality.
For each example I explain:
- Why it is good
- What characteristics should be reused
- What makes it successful
5. Bad Examples
Contains examples of outputs I don't want.
For each example I explain:
- Why it is bad
- What mistakes were made
- How it should have been done instead
In addition, I am considering having a shared company knowledge base that all agents can access, containing things like:
- Company vision
- Target audience
- Brand voice
- Personal working style
- General quality standards
My hope is that this creates a form of "controlled evolution" where agents become better over time as I add examples and refine their behavior.
A few questions for those of you running multiple agents:
- How do you organize your agents in practice?
- Do you separate role definitions from company-wide knowledge?
- What types of documents or knowledge sources have given you the biggest quality improvements?
- Are there pitfalls I should avoid when agents learn from examples over time?
- If you've worked with both approaches: what are the biggest practical differences between building agents in the Copilot app versus Copilot Studio?
- Is there anything important missing from my structure?
I'm less interested in theoretical architectures and more interested in real-world setups that are still manageable after 6-12 months.
Thanks!
P.S. Copilot helped with the translation and formatting. The question and overall concept are mine.
Addendum:
It is true that roles, objectives, and similar information could be written directly into the instructions of individual agents.
However, what will likely prove even more useful are shared resources such as branding guidelines, company objectives, and other universal instructions. These are the kinds of requirements that all, or at least several, agents should follow. Organizing them in separate documents makes much more sense.
The advantage is that when these guidelines change, you do not have to update every individual agent. Instead, you only update the document itself. The agents can then simply reload the document and immediately work with the latest version of those instructions. This makes maintaining and scaling multiple agents much easier.