agent-teams

Solid

Паттерны для оптимального состава команд агентов: sizing heuristics, preset configurations, agent type selection. Используй когда решаешь сколько агентов запустить, какой тип агента выбрать для роли, как организовать Review/Debug/Feature/Security команду. Триггеры: /agent-teams, "team composition", "how many agents", "spawn agents", "multi-agent team", "сколько агентов", "команда агентов", "parallel agents setup".

AI & Automation 7 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

<!-- BSV — Brief Skill View | поиск: BSV Скил : agent-teams TL;DR : Sizing heuristics + preset teams + agent type selection для multi-agent workflows Вызов : /agent-teams, team composition, how many agents, spawn agents, multi-agent НЕ для : Одиночный агент (прямо используй Agent tool); review кода (→ /reviewer) --> # Agent Teams Orchestration ## Sizing Heuristics **Правило:** Начни с наименьшей команды которая покрывает все нужные измерения. Каждый дополнительный агент = overhead координации. | Сложность | Размер | Когда использовать | |-----------|--------|--------------------| | Simple | 1-2 | Single-dimension review, изолированный баг, небольшая фича | | Moderate | 2-3 | Multi-file изменения, 2-3 аспекта, средние фичи | | Complex | 3-4 | Cross-cutting concerns, большие фичи, глубокий debug | | Very Complex | 4-5 | Full-stack фичи, comprehensive review, системные проблемы | ## Agent Type Selection | Тип | Инструменты | Использовать для | |-----|-------------|------------------| | `general-purpose` | Все | Implementation, debugging | | `Explore` | Read-only | Research — НЕ для impl | | `Plan` | Read-only | Архитектурное планирование | | `reviewer` | Read + Bash | Code review | | `builder` | Read + Write + Edit + Bash | Написание кода | | `tester` | Read + Write + Bash | Написание тестов | **Критическое:** Read-only агенты (Explore, Plan) НЕ могут изменять файлы. ## Preset Team Compositions | Команда | Агенты | Измерения | Когда | |---------|--------|-----------...

Details

Author
sergeeey
Repository
sergeeey/Claude-cod-top-2026
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

agent-team-orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.

81 Updated today
aAAaqwq
AI & Automation Listed

creating-agent-teams

Use when facing a complex task that could benefit from multiple agents, parallel work, or specialized roles - triggers on "create a team", "parallelize", "multi-agent", or cross-layer implementation needs

1 Updated yesterday
ELVINgotIT
AI & Automation Solid

agent-teams

Set up and orchestrate Claude Code agent teams - multiple Claude Code instances working together with shared tasks, inter-agent messaging, and centralized management. Use when the user wants to (1) create or start an agent team for parallel work, (2) configure agent team settings like display mode or teammate mode or permissions, (3) coordinate teammates for code review or debugging or feature development or research, (4) understand when to use agent teams vs subagents, (5) troubleshoot agent team issues. Triggers include mentions of "agent team", "team of agents", "parallel agents", "teammates", "split pane", "tmux teammates", "delegate mode", "spawn teammates", or wanting multiple Claude instances collaborating.

6 Updated 5 days ago
DmitriyYukhanov