mirror of
https://github.com/github/awesome-copilot.git
synced 2026-04-30 12:15:56 +00:00
8cb29415be
* Add ai-team-orchestration plugin: multi-agent dev team with Producer, Dev Team, QA agents * fix: use kebab-case agent names to match filenames * fix: regenerate README after agent name change * fix: address Copilot review — add edit tools to Producer/QA, use GitHub closing keywords * fix: update agent tools to official VS Code tool set names Replace outdated/nonexistent tool names with current official tool sets: - Producer: search, read, edit, web (removed nonexistent githubRepo) - Dev Team: search, read, edit, execute, web (replaced runCommands, problems, usages, etc.) - QA: search, read, edit, execute, web (removed nonexistent findTestFiles, runTests) Ref: https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features#_chat-tools * fix: remove frontmatter from plugin README per reviewer feedback --------- Co-authored-by: Aaron Powell <me@aaron-powell.com>
5.9 KiB
5.9 KiB
name, description
| name | description |
|---|---|
| ai-team-orchestration | Bootstrap and run a multi-agent AI development team. Use when: starting a new software project with AI agents, setting up parallel dev/QA teams, creating sprint plans, writing brainstorm prompts with distinct agent voices, recovering a project workflow, or planning sprints. |
AI Team Orchestration
When to Use
- Starting a new project that needs planning, development, testing, and deployment
- Setting up parallel AI agent teams (dev, QA, DevOps)
- Writing brainstorm prompts that produce real debate (not generic output)
- Creating sprint plans with cross-chat context survival
- Recovering from context overflow mid-sprint
Team Roles
| Agent | Name | Role | Focus |
|---|---|---|---|
| Producer | Remy | Sprint planning, coordination, merging PRs | Scope control, handoffs, issue triage |
| Product Designer | Kira | UX, mechanics, user experience | Fun factor, user flows, feature design |
| Visual/Art Director | Milo | CSS, animations, visual identity | Design system, polish, accessibility |
| Frontend Engineer | Nova | UI framework, state management, components | React/Vue/Svelte, client-side logic |
| Backend Engineer | Sage | API, database, auth, security | Server-side logic, infrastructure |
| DevOps Engineer | Dash | CI/CD, cloud deployment, pipelines | GitHub Actions, Azure/AWS/GCP |
| QA Engineer | Ivy | E2E tests, automation, playtesting | Playwright/Cypress, bug filing, sign-off |
Customize names and roles for your project. Not every project needs all roles.
Chat Architecture
The human (CEO) is the message bus between parallel chats:
┌────────────────────────────────────────┐
│ @ai-team-producer — Plans, merges │
│ NEVER writes code │
└────────────────┬───────────────────────┘
│ Human carries messages
┌──────────┼──────────┐
▼ ▼ ▼
┌──────────┐ ┌────────┐ ┌────────┐
│@ai-team │ │@ai-team│ │DevOps │
│-dev │ │-qa │ │(on │
│ │ │ │ │demand) │
│ Nova │ │ Ivy │ │ │
│ Sage │ │ │ │ │
│ Milo │ │ │ │ │
│ │ │feature/│ │feature/│
│ feature/ │ │qa-N │ │devops-N│
│ sprint-N │ └────────┘ └────────┘
└──────────┘
Each team works in a separate VS Code window with its own clone:
git clone <repo> project-dev # Dev team
git clone <repo> project-qa # QA
git clone <repo> project-devops # DevOps (only when needed)
Project Bootstrap
1. Create PROJECT_BRIEF.md
The single source of truth across all chats. See the project brief template.
Required sections (do not abbreviate):
- Project Overview
- Concept / Product Description
- Tech Stack
- Architecture (ASCII diagram)
- Key Files Map
- Team Roles
- Sprint Status (updated every sprint)
- Current State (rewritten every sprint)
- Security Rules
- How to Run Locally
- How to Deploy
- Cross-Chat Handoff Protocol — how context survives between chats
- Bug & Fix Tracking — GitHub Issues as single source of truth
- Multi-Repo Setup — separate clones, branch strategy, merge rules
2. Run a Brainstorm
See the brainstorm format. Key: name each agent explicitly with distinct personality and perspective. Require at least 2 genuine disagreements to prevent groupthink.
3. Create Sprint Plans
See the sprint plan template. Every sprint gets:
docs/sprint-N/plan.md— prioritized tasks, success criteriadocs/sprint-N/progress.md— live tracker, enables recoverydocs/sprint-N/done.md— handoff doc written at sprint end
4. Execute Sprints
Read PROJECT_BRIEF.md, then read docs/sprint-N/plan.md. Execute Sprint N.
First: git pull origin main && git checkout -b feature/sprint-N
Close GitHub Issues in commits: "fix: description (Fixes #NN)"
Update docs/sprint-N/progress.md after each phase.
When done, push and create PR: git push origin feature/sprint-N
Follow Sections 12-14 of PROJECT_BRIEF.md.
5. QA Sign-off
After dev merges, QA does a full playthrough:
Read PROJECT_BRIEF.md. You are Ivy (QA).
Sprint N is merged to main. Do full playthrough.
File bugs as GitHub Issues. Write docs/qa/sprint-N-signoff.md.
Context Recovery
When a chat gets long (>100 messages), save state and start fresh:
Before closing:
- Update
docs/sprint-N/progress.mdwith current status - Update
PROJECT_BRIEF.mdsections 7+8 - Write
docs/sprint-N/done.md
Cold start prompt:
Read PROJECT_BRIEF.md and docs/sprint-N/progress.md.
Continue from where it left off.
Anti-Patterns
See anti-patterns reference for the full list. Top 5:
| Don't | Do Instead |
|---|---|
| Rebase feature branches | Merge (rebase loses commits) |
| Producer writes code | Producer only plans, merges, files issues |
| Batch "fix everything" commits | One commit per fix with issue reference |
| Vague brainstorm prompts | Name each agent with distinct perspective |
| Keep bugs only in chat | File GitHub Issues (chat context dies) |
Tips for Better Results
- "Take your time, do it right" in prompts produces better output than rushing
- Test before merge — you playtest, file issues, dev fixes, then merge
- Run team consiliums before major sprints — each agent reviews the plan from their perspective
- Save lessons to memory after every milestone