ai-team-orchestration
Skill1 starsChanged 16 days agoMITView on GitHub
Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- github/awesome-copilotword for word, first seen Oct 25, 2026
- patterson-agents/skillstheir own version, first seen Aug 12, 2026
Other versions2 projects use a version of this.
Word for word · 1
- github/awesome-copilot★ 41k100% same
Edited · 0
None found.
Wrote their own version · 1
- patterson-agents/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository95 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- agent-architectureSkill
- agentic-evalSkill
- agent-owasp-complianceSkill
- agent-skill-stackSkill
- ai-readySkill
- answer-me-with-htmlSkill
- anti-ui-slopSkill
- archifySkill
- autoresearchSkill
- batch-script-progressSkill
- cli-creatorSkill
- codebase-designSkill
- code-exemplars-blueprint-generatorSkill
- copilot-instructions-blueprint-generatorSkill
- create-agentsmdSkill
- create-architectural-decision-recordSkill
- create-github-action-workflow-specificationSkill
- create-github-issues-feature-from-implementation-planSkill
- create-readmeSkill
- create-specificationSkill
- create-technical-spikeSkill
- create-tldr-pageSkill
- docs-sync-auditSkill
- folder-structure-blueprint-generatorSkill
- gh-fix-ciSkill
- github-actions-hardeningSkill
- github-repo-careSkill
- impeccableSkill
- launchd-automationSkill
- mcp-security-auditSkill
- notion-cliSkill
- opencode-model-routerSkill
- playwright-cliSkill
- python-pypi-package-builderSkill
- refactorSkill
- simple-englishSkill
- swiftui-expert-skillSkill
- technical-documentationSkill
- workshop-driverSkill
- xerj-hubSkill
- xerjSkill
- anti-ui-slopSkill
- autoresearchSkill
- batch-script-progressSkill
- calling-frontend-from-tauri-rustSkill
- calling-rust-from-tauri-frontendSkill
- cli-creatorSkill
- codebase-designSkill
- code-exemplars-blueprint-generatorSkill
- configuring-tauri-appsSkill
- configuring-tauri-capabilitiesSkill
- configuring-tauri-cspSkill
- configuring-tauri-permissionsSkill
- configuring-tauri-scopesSkill
- copilot-instructions-blueprint-generatorSkill
- create-agentsmdSkill
- create-architectural-decision-recordSkill
- create-github-action-workflow-specificationSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 19 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use three stable agents:
- Distinctive: line 22
Keep the workflow proportional:
- Distinctive: line 25
Use a short plan for multi-step or cross-cutting work.
- Distinctive: line 26
Add independent review or QA when risk, uncertainty, or repository policy justifies it.
- Distinctive: line 31
Read existing repository instructions and documentation.
- Very specific: line 33
Create or update PROJECT_BRIEF.md only when durable cross-session context is useful.
- Distinctive: line 35
Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.
- Distinctive: line 43
Keep durable project state concise and current.
- Distinctive: line 47
Follow repository conventions and implement the smallest complete solution.
- Distinctive: line 48
Run relevant checks and inspect the final diff.
- Distinctive: line 53
Use only when dedicated behavioral verification adds value.
- Distinctive: line 54
Test the requested change and important regressions.
- Distinctive: line 59
Use the brainstorm format for product or architecture decisions that benefit from competing perspectives.
- Distinctive: line 63
Before ending a long or interrupted session:
- Distinctive: line 65
Update the active plan or progress note if one exists.
- Distinctive: line 67
Use a cold-start prompt such as:
- Distinctive: line 84
If the environment exposes too many tools, deselect irrelevant tools or MCP servers, or use VS Code virtual-tool management.
- Distinctive: line 88
Prefer working software and clear handoffs over process artifacts.
- Distinctive: line 89
Follow repository policy instead of embedding universal Git commands.
- Distinctive: line 91
Keep bugs and important decisions in durable project systems, not only chat.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Team Orchestration
Use three stable agents:
| Agent | Purpose |
@ai-team-producer | Clarify scope, plan proportionately, coordinate, and merge |
@ai-team-dev | Implement, test, self-review, and prepare the pull request |
@ai-team-qa | Independently test behavior when dedicated QA is useful |
Nova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers.
Default Workflow
Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state
Keep the workflow proportional:
- Skip formal planning for small, obvious changes.
- Use a short plan for multi-step or cross-cutting work.
- Add independent review or QA when risk, uncertainty, or repository policy justifies it.
- Let branch protection, required checks, permissions, and merge queues enforce repository merge policy.
Start or Adopt a Project
- Read existing repository instructions and documentation.
- Discover the actual stack, architecture, commands, deployment model, and risks.
- Create or update
PROJECT_BRIEF.mdonly when durable cross-session context is useful. Start from the project brief template and omit irrelevant sections. - For substantial work, create a concise plan from the sprint plan template.
- Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.
Execute
Producer
- Define the outcome, constraints, acceptance criteria, and explicit exclusions.
- Choose review and QA based on risk rather than ceremony.
- Keep durable project state concise and current.
Dev
- Follow repository conventions and implement the smallest complete solution.
- Run relevant checks and inspect the final diff.
- Open or update the pull request with summary, verification, and limitations.
QA
- Use only when dedicated behavioral verification adds value.
- Test the requested change and important regressions.
- Report reproducible findings and verify fixes.
Brainstorms
Use the brainstorm format for product or architecture decisions that benefit from competing perspectives. For ordinary implementation choices, let Dev decide using repository conventions.
Context Recovery
Before ending a long or interrupted session:
- Update the active plan or progress note if one exists.
- Record material decisions, blockers, and the next action in repository context.
- Use a cold-start prompt such as:
Read the repository instructions, then read whichever sources exist for this
work: the active issue or request, PROJECT_BRIEF.md, and the active plan or
progress note.
Continue from the recorded next action.Tool and Model Inheritance
The bundled agents intentionally omit tools and model frontmatter:
- available built-in, MCP, and extension tools remain usable;
- developers keep control of model selection;
- role boundaries are defined by instructions and normal trust, permission, authentication, and approval controls.
If the environment exposes too many tools, deselect irrelevant tools or MCP servers, or use VS Code virtual-tool management. Do not add a machine-specific plugin allowlist.
Principles
- Prefer working software and clear handoffs over process artifacts.
- Follow repository policy instead of embedding universal Git commands.
- Preserve unknown work and ask before destructive or privileged actions.
- Keep bugs and important decisions in durable project systems, not only chat.
- See anti-patterns for concise lessons.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

