Add Gem Team Multi-Agent Orchestration agents and documentation

[mubaidr]

Gem Team: Multi-Agent Orchestration Framework

About

Multi-agent AI orchestration framework for complex project execution — 8 specialized agents, DAG-based planning, parallel execution, TDD verification

Link: https://github.com/mubaidr/gem-team

• Introduced new agents: gem-chrome-tester, gem-devops, gem-documentation-writer, gem-implementer, gem-orchestrator, gem-planner, gem-researcher, and gem-reviewer.
• Updated README.collections.md to include the new Gem Team Multi-Agent Orchestration collection.
• Created gem-team.collection.yml and gem-team.md for structured documentation of the multi-agent orchestration framework.
• Each agent includes detailed descriptions, workflows, operating rules, and final anchors for clarity on their functionalities and usage.

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• My contribution adds a new instruction, prompt, agent, or skill file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, or skill with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

Multi-agent AI orchestration framework for complex project execution — 8 specialized agents, DAG-based planning, parallel execution, TDD verification

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New collection file.
• New skill file.
• Update to existing instruction, prompt, agent, collection or skill.
• Other (please specify):

---

Additional Notes

Made this a collection, since this is orchestration based agent collection.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[aaronpowell]

I noticed there are tools referenced in the agents, would it be worthwhile explicitly adding those tools into the frontmatter of the agent definition?

Also, it might be worthwhile generating a plugin from this collection, which can be done with npm run plugin:migrate gem-team and commit the plugin symlinks. Then it can be installed easily using copilot-cli's plugin support.

[mubaidr]

I noticed there are tools referenced in the agents, would it be worthwhile explicitly adding those tools into the frontmatter of the agent definition?

These instructions only use agenric suggestive or added preference to agents with fallbacks if not available. Except, chrome testing agent, which depends upon chrome testing tools, but then again TBH I don't really know to add this tool to tools section. I mean we can use tools section to limit the tools available to agents but how to achieve addition here?

[mubaidr]

Also, it might be worthwhile generating a plugin from this collection, which can be done with npm run plugin:migrate gem-team and commit the plugin symlinks. Then it can be installed easily using copilot-cli's plugin support.

100%, I will push this update now. Thanks

[aaronpowell]

I noticed there are tools referenced in the agents, would it be worthwhile explicitly adding those tools into the frontmatter of the agent definition?

These instructions only use agenric suggestive or added preference to agents with fallbacks if not available. Except, chrome testing agent, which depends upon chrome testing tools, but then again TBH I don't really know to add this tool to tools section. I mean we can use tools section to limit the tools available to agents but how to achieve addition here?

Let's leave it as defined at the moment, as I think I need to review the overall design in this repo of plugins so that we can better outline how things like MCP servers (which I'm assuming is the intended interaction with the Chrome devtools) are added (plugins can include MCP servers but it's really clunky currently to do).

[mubaidr]

I noticed there are tools referenced in the agents, would it be worthwhile explicitly adding those tools into the frontmatter of the agent definition?

These instructions only use agenric suggestive or added preference to agents with fallbacks if not available. Except, chrome testing agent, which depends upon chrome testing tools, but then again TBH I don't really know to add this tool to tools section. I mean we can use tools section to limit the tools available to agents but how to achieve addition here?

Let's leave it as defined at the moment, as I think I need to review the overall design in this repo of plugins so that we can better outline how things like MCP servers (which I'm assuming is the intended interaction with the Chrome devtools) are added (plugins can include MCP servers but it's really clunky currently to do).

Ok I will keep an eye on how things progress about plugins/ mcp.