Agent skill · operations · github
ai-team-orchestration
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.
Why this skill is useful
Provides a structured multi-agent workflow for project management that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 1. Read existing repository instructions and documentation. 2. Discover the actual stack, architecture, commands, deployment model, and risks. 3. Create or update PROJECTBRIEF.md only when durable cross-session context is useful. Start from the project brief template and omit irrelevant sections. 4. For substantial work, create a concise plan from the sprint plan template. 5. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/ai-team-orchestration