skilld
All skills
github avatar

/ai-team-orchestration

@7968055 official
by githubgithub/awesome-copilot40k stars
5,040

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/ai-team-orchestration

This session only. Nothing lands on disk.

referencesproject-brief-template.md

≈489 tokens on demand. Your agent reads this file only when SKILL.md points to it.

PROJECT_BRIEF.md Template

Use this only when the project benefits from durable context across sessions. Keep it concise and omit irrelevant sections.

# PROJECT_BRIEF.md - [Project Name]

> Last updated: [date]

## 1. Goal and Users

[What the project is, who it serves, and the outcome it should create.]

## 2. Current Scope

**In scope**
- [outcome]

**Out of scope**
- [explicit exclusion]

## 3. Stack and Architecture

- Runtime/language: [value]
- Frameworks/libraries: [value]
- Data/services: [value]
- Deployment: [value or not applicable]
- Tests/checks: [verified commands]

[Short architecture description or diagram when useful.]

## 4. Key Files

| Area | Path | Purpose |
|---|---|---|
| [area] | `[path]` | [purpose] |

## 5. How to Work

- Setup: [verified command or link]
- Run: [verified command or link]
- Test: [verified commands]
- Deploy: [verified process or not applicable]
- Repository rules: [links to contribution/security instructions]

## 6. Safety and Constraints

- [secrets/privacy/data rules]
- [compatibility or reliability invariant]
- [operational constraint]

## 7. Current State

**Working**
- [item]

**Known issues**
- [issue/link]

**Next**
- [next outcome]

## 8. Team and Handoff

- Producer: scope, coordination, and merge
- Dev: implementation and verification
- QA: optional independent behavioral verification

## Onboarding checklist (add to brief)

- Setup verified: `npm ci` / `pip -r requirements.txt`
- Tests run: `npm test` / `pytest -q`
- Lint pass: `npm run lint`
- Where to find CI logs and deploy dashboards

## Where to record decisions

- Add short entries to DECISIONS.md or create an issue with the decision tag. Each entry should include: title, date, owner, 1-line summary, rationale, and link to PR/issue.

Record material decisions, blockers, and the next action here or in the active plan. Use GitHub Issues or the repository's tracker for bugs and follow-up work.

Source: SKILL.md on GitHub

Third-party checks

1 warning16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill facilitates multi-agent development orchestration. It identifies a potential risk of indirect prompt injection as it instructs agents to read and follow external repository documentation and issues without explicit safety boundaries or sanitization.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at 7968055. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

Topics

  • Testing
  • multi-agent
  • orchestration
  • sprint-planning
  • team-coordination
  • github
  • project-management
  • ai-workflow

README badge

README badge for github/awesome-copilot/ai-team-orchestration

What it does

Orchestrates parallel AI agent teams (dev, QA, DevOps, design) across separate VS Code clones to execute multi-sprint software projects from brainstorm through deployment. Uses a human coordinator role, shared PROJECT_BRIEF.md for context continuity, and GitHub Issues for cross-chat handoffs to prevent context collapse.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with Claude or other AI models?
The skill is model-agnostic and designed for any AI coding agent. It uses role-based prompts and chat architecture that work across Claude, other LLMs, or mixed-model teams.
Can I use fewer than seven agent roles?
Yes. The skill explicitly states 'Not every project needs all roles.' Customize names and roles based on your project's actual needs.
How does context survive between separate AI chats?
Through three documents kept in version control: PROJECT_BRIEF.md (single source of truth), docs/sprint-N/progress.md (live tracker), and docs/sprint-N/done.md (handoff doc). Each chat reads these before continuing.
Do I need separate git clones for each team?
Yes. The skill prescribes separate VS Code windows with separate clones (project-dev, project-qa, project-devops) so teams work in parallel without merge conflicts during execution.
What happens when a chat exceeds context limits?
Save progress to docs/sprint-N/progress.md and PROJECT_BRIEF.md, then start a fresh chat. The cold-start prompt reads these files to resume work without losing state.

Generated from the current SKILL.md. These answers refresh after source changes.