agent-teams

Orchestrate multi-agent collaboration with lifecycle phases, quality gates, and structured state.

6|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/snewhouse/aa-ma-forge --skill agent-teams-snewhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-teams
Source: https://github.com/snewhouse/aa-ma-forge/tree/main/claude-code/skills/agent-teams
Command: npx skills add https://github.com/snewhouse/aa-ma-forge --skill agent-teams-snewhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you run complex, multi-agent Claude Code collaborations without losing coordination, quality gates, or state—especially when tasks require research, implementation, review, debate, and clean shutdown.

Core Features & Use Cases

  • Multi-role orchestration: Creates and coordinates teams with purpose-built roles (researchers, architect, implementers, reviewers, tester, synthesizer).
  • 7-phase lifecycle execution: Classify → compose → get approval → spawn → coordinate & monitor → shutdown → cleanup & report.
  • AA-MA structured memory integration: When an AA-MA task is active, it maps milestones to team tasks and keeps AA-MA files synchronized at the right times.
  • Research debate for higher confidence: Implements a competing-hypotheses challenge round to reduce confirmation bias.
  • Quality and error guardrails: Enforces design/code/test consistency gates and provides protocols for file conflicts, stuck teammates, partial completion, and retries.
  • Graceful shutdown and final reporting: Drains active work, verifies results, deletes team artifacts, and summarizes outcomes to the user.

Quick Start

Use agent-teams when your task needs two or more coordinated agents that must communicate (for example, a research phase with competing hypotheses followed by coordinated implementation).

Frequently Asked Questions about agent-teams

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-agent work without losing state or skipping quality gates?

Multi-agent orchestration coordinates persistent agents across complex phases using a 7-step lifecycle: classify, compose, get approval, spawn, coordinate, shutdown, and cleanup. It enforces quality gates, tracks execution state, and handles task dependencies so work is validated and reported.

What is the best way to run a research debate with competing hypotheses using multiple agents?

Research debate reduces confirmation bias by running a competing-hypotheses challenge round during multi-agent orchestration. Agents challenge each other's conclusions before synthesis, yielding higher confidence results with structured execution state tracked across the team lifecycle.

How do I manage task lifecycle and inter-agent messaging for complex code review scenarios?

Task lifecycle management applies role-based spawning for specialized agents like reviewers and testers, enforced design-code-test consistency gates, and structured inter-agent messaging. It handles file conflicts, stuck teammates, and partial completion with retry protocols during coordinated code review.

Can I synchronize milestones to tasks when an AA-MA task is active during multi-agent collaboration?

AA-MA milestone-to-task synchronization maps milestones to team tasks and keeps AA-MA files synchronized across tasks.md, reference.md, context-log.md, and provenance.log during multi-agent orchestration, ensuring structured memory integration when an AA-MA task is active.

How do I gracefully shutdown multi-agent teams and verify final results?

Graceful shutdown drains active work from spawned agents, verifies results against quality gates, deletes team artifacts, and summarizes outcomes to the user. This cleanup phase ensures coordinated multi-agent work completes cleanly without orphaned processes or lost execution state.

When should I use multi-agent orchestration instead of a single agent for my software engineering task?

Use multi-agent orchestration when your task needs two or more coordinated agents that must communicate, such as a research phase with competing hypotheses followed by coordinated implementation. It applies to research, implementation, hybrid, and review scenarios requiring inter-agent messaging and task dependencies.