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.

referencessprint-plan-template.md

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

Work Plan Template

Use this for substantial work. Small, clear changes can proceed directly from the issue or request.

# [Work Item] - Plan

## Goal

[One observable outcome.]

## Context

- Relevant issue/request: [link or summary]
- Repository instructions: [links]
- Important constraints: [list]

## In Scope

- [deliverable]

## Out of Scope

- [explicit exclusion]

## Tasks

1. [task]
2. [task]
3. [task]

## Acceptance Criteria

- [ ] [observable behavior]
- [ ] Relevant repository checks pass (example: `npm run lint`, `npm test`)
- [ ] Tests covering the change are added or validated
- [ ] Documentation/context is updated when behavior or operation changed

## Verification

- Automated: [commands or checks]
  - Example: `npm ci && npm run test` or `pytest -q`
  - Example: `npm run lint && npm run build`
- Manual: [focused scenarios, if useful]
- Independent review: required / optional / not needed - [reason]
- QA: required / optional / not needed - [reason]

## PR Checklist (add to PR body)

- Branch name follows repo policy (e.g., `feat/`, `fix/`, or `chore/`)
- Description: short summary, why, and acceptance criteria
- Verification steps included (commands & manual checks)
- Tests added or existing tests updated
- Relevant docs/PROJECT_BRIEF updated if behavior changed
- Reviewers: @team or specific owners
- Required checks: list CI jobs that must pass
- Release notes / changelog entry: yes/no

## Risks and Decisions

- [risk or material decision]

## QA risk matrix (when to require QA)

- High impact × High uncertainty = QA required
- High impact × Low uncertainty = QA recommended
- Low impact × High uncertainty = QA recommended
- Low impact × Low uncertainty = QA optional

## Next Action

[owner and immediate next step]

Progress Note

For long-running work, keep a short progress note:

# [Work Item] - Progress

- Completed: [items]
- In progress: [item]
- Blocked: [issue or none]
- Decisions: [material decisions]
- Verification so far: [results]
- Next action: [specific action]

Dev Handoff

Read the repository instructions, PROJECT_BRIEF.md when present, and this plan.
Implement the in-scope work, run the listed verification, update durable context
when needed, and prepare a pull request. Do not merge.

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.