Reviewed sourceAI Developmentv2.0.0

ai-team-orchestration Agent Plugin

Run a lightweight role-separated development team with a producer, implementation team, optional QA, developer-selected models and tools, proportionate planning, and durable project context.

0 repository stars MIT Updated Aug 6, 2026
Reviewed seed

AI Team Orchestration

with reviewed context.

The catalog adds a fixed-commit inventory, operating summary, prerequisites, and task-fit guidance for AI Team Orchestration.

Inspect, compare, verify

Installation

Install AI Team Orchestration

Install from github/awesome-copilot in a compatible Agent Plugins client. The agents intentionally inherit enabled tools and the developer-selected model; repository permissions and approval controls still apply.

Terminal · Git sparse checkout
git clone --filter=blob:none --sparse https://github.com/github/awesome-copilot.git
cd awesome-copilot
git sparse-checkout set plugins/ai-team-orchestration
The agents intentionally inherit enabled tools and the developer-selected model; repository permissions and approval controls still apply.
Review the fixed-source README and manifest before enabling the workflow.

Explainable standards check

Conforms to Agent Plugins 1.0.0

Official latest version: 1.0.0 (Working Draft). The value is read from the official specification and cached for one day.

Read the official specification

This is a static package-format check, not a security audit, quality score, malware scan, or guarantee of client compatibility.

Canonical manifest schema

plugin.json targets the official 1.0.0 schema.

Agent Plugins specification §5.2

Required name and naming rules

The plugin name “ai-team-orchestration” satisfies the 1–64 character naming rules.

Agent Plugins specification §§5.3 and 5.5

Closed top-level schema

No unknown top-level manifest fields were found.

Agent Plugins specification §5.2

Manifest field types

All present metadata and extension fields use permitted JSON types.

Agent Plugins specification §§5.2–5.6

Root plugin.json file

A regular plugin.json file exists at the plugin root.

Agent Plugins specification §§4.1 and 5.1

Agent Skills discovery and format

0 immediate-child Agent Skills discovered; every SKILL.md passed required frontmatter and naming checks.

Agent Plugins specification §7.1 and Agent Skills specification

MCP configuration

No root mcp.json is present; MCP is optional and its absence is conforming.

Agent Plugins specification §§6.2 and 7.2

Capabilities

What can you do with ai-team-orchestration?

Run a lightweight role-separated development team with a producer, implementation team, optional QA, developer-selected models and tools, proportionate planning, and durable project context.

The reviewed package declares 1 skill and 3 agent resources for its documented workflow.

  • Separate producer, developer, and QA responsibilities
  • Keep planning proportional to task size and risk
  • Use developer-selected models and enabled tools
  • Implement, test, and self-review without merging
  • Run optional independent behavioral QA
  • Keep important project state in durable files or issues

Coordinate role-separated work

Separate producer, developer, and QA responsibilities; Keep planning proportional to task size and risk; Use developer-selected models and enabled tools.

Implement and independently verify changes

Implement, test, and self-review without merging; Run optional independent behavioral QA; Keep important project state in durable files or issues.

Practical workflow

A reviewed AI Team Orchestration workflow

Pass 01 / Start

Coordinate role-separated work

Let the producer scope and coordinate substantial work without implementing application code.

Pass 02 / Verify

Implement and independently verify changes

Have the development role implement and test, then optionally ask QA for independent acceptance verification before merge.

Package contents

What is included in ai-team-orchestration?

ai-team-orchestration declares 1 Skill, 0 MCP configurations, and 3 additional resources. The included-file links below point to the reviewed source repository.

Agent Skills

1

ai-team-orchestration

MCP servers

0

No runtime service

Package format

Agent Plugins

Official latest 1.0.0

Synced source content

Repository README

View original README

This README snapshot is stored by Agent Plugins Hub and refreshed by the daily GitHub synchronization pipeline. Remote images and embedded content are not loaded.

Source
https://github.com/github/awesome-copilot#readme

This repository does not currently provide a README snapshot. The plugin instructions below remain available.

Source documentation

AI Team Orchestration source documentation

Rendered from the linked GitHub source. Raw HTML is disabled, scripts cannot execute, remote images are omitted, and external links open separately.

What this catalog entry adds

This entry summarizes the fixed reviewed manifest and README without extending the upstream package's claims.

Package scope

Run a lightweight role-separated development team with a producer, implementation team, optional QA, developer-selected models and tools, proportionate planning, and durable project context.

Declared package inventory

Skills: ai-team-orchestration

Agent resources: ai-team-dev, ai-team-producer, ai-team-qa

Agents are listed as resources because the extension declares them separately from skills. Only the real upstream plugin.json and README.md are listed as package files.

Documented capabilities

  • Separate producer, developer, and QA responsibilities
  • Keep planning proportional to task size and risk
  • Use developer-selected models and enabled tools
  • Implement, test, and self-review without merging
  • Run optional independent behavioral QA
  • Keep important project state in durable files or issues

Workflow

  1. Let the producer scope and coordinate substantial work without implementing application code.
  2. Have the development role implement and test, then optionally ask QA for independent acceptance verification before merge.

Requirements and limitations

The agents intentionally inherit enabled tools and the developer-selected model; repository permissions and approval controls still apply.

Review generated output and consequential actions with the relevant maintainer or subject-matter expert.

License

The upstream manifest and README identify the plugin as MIT licensed.