team
Orchestrate multi-agent teams across AIWG providers natively on Claude Code or emulated via Mission Control elsewhere
What this skill does
# team
You orchestrate multi-agent teams across all AIWG providers. On Claude Code, teams run natively via the Task tool. On all other providers, you emulate team execution through `aiwg mc` (Mission Control). Team definitions live in `agentic/code/frameworks/sdlc-complete/teams/`.
## Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "spin up a team" → `team run` with named team
- "who's on the security review team" → `team info`
- "what teams do I have" → `team list`
- "run the greenfield team on this task" → `team run greenfield "<task>"`
## Trigger Patterns Reference
| Pattern | Example | Action |
|---------|---------|--------|
| Run a named team | "run the sdlc-review team on the SAD" | `aiwg team run sdlc-review "<task>"` |
| List available teams | "what teams are available" | `aiwg team list` |
| Inspect team composition | "who is on the security review team" | `aiwg team info security-review` |
| Task-inferred team | "review this architecture for security" | `aiwg team run security-review "<task>"` |
## Behavior
When triggered:
1. **Parse the subcommand**:
- `run <team-name> "<task>"` — execute team against a task
- `list` — list all available teams from the manifest
- `info <team-name>` — show team composition and use cases
2. **Detect provider**:
- Claude Code (`CLAUDE_CODE_VERSION` set) → native Task-tool dispatch
- All other providers → emulate via `aiwg mc dispatch`
3. **Run the appropriate command**:
```bash
# Run a team on a task
aiwg team run sdlc-review "Review the SAD at .aiwg/architecture/sad.md"
# Run with provider override
aiwg team run security-review "Audit auth module" --provider cursor
# List all teams
aiwg team list
# Inspect a team
aiwg team info greenfield
```
4. **Report execution progress**:
- Native (Claude Code): reports inline as agents complete
- Emulated (mc): reports mission IDs and tracks via `aiwg mc status`
## Team Definitions
Teams are defined as JSON files in `agentic/code/frameworks/sdlc-complete/teams/`. Built-in teams:
| Team | Use Cases |
|------|-----------|
| `sdlc-review` | Architecture, requirements, and test review |
| `security-review` | Threat modeling, security audit, privacy review |
| `api-development` | API design, documentation, test generation |
| `full-stack` | Feature implementation across layers |
| `greenfield` | New project inception and architecture |
| `maintenance` | Refactoring, debt reduction, upgrades |
| `migration` | Database or platform migration planning |
## Team Definition Format
```yaml
# .aiwg/teams/my-team.yaml (project-local override)
name: Custom Review Team
slug: custom-review
description: Tailored review for domain-specific concerns
agents:
- agent: security-architect
role: lead
responsibilities:
- Security threat model
- Auth design review
- agent: test-architect
role: contributor
responsibilities:
- Test coverage gaps
- Integration risks
- agent: technical-writer
role: reviewer
responsibilities:
- Clarity and consistency
dispatch: parallel
```
## Execution Modes
### Native (Claude Code)
Agents launch as parallel Task tool calls in a single message. Each agent runs independently with its assigned prompt, and results are collected and synthesized.
### Emulated (All Other Providers)
```bash
# Steward emulates by dispatching via Mission Control
SESSION=$(aiwg mc start --name "team-run-$(date +%s)")
aiwg mc dispatch $SESSION "security-architect: <task>" --completion "Review complete"
aiwg mc dispatch $SESSION "test-architect: <task>" --completion "Review complete"
aiwg mc watch $SESSION
```
## Examples
### Example 1: Run a review team
**User**: "Run the security review team on the auth module"
**Extraction**: `team run security-review` on the auth module
**Action**:
```bash
aiwg team run security-review "Review src/auth/ for security vulnerabilities, focusing on token handling and session management"
```
**Response** (Claude Code, native):
```
Launching security-review team (3 agents, parallel)...
security-architect: reviewing...
security-auditor: reviewing...
privacy-officer: reviewing...
Results collected. 2 critical findings, 4 recommendations.
Full report: .aiwg/working/team-runs/security-review-20260401-143022.md
```
### Example 2: List teams
**User**: "What teams do I have available?"
**Action**:
```bash
aiwg team list
```
**Response**:
```
Available teams (7):
api-development API design, documentation, test generation
full-stack Feature implementation across layers
greenfield New project inception and architecture
maintenance Refactoring, debt reduction, upgrades
migration Database or platform migration planning
sdlc-review Architecture, requirements, and test review
security-review Threat modeling, security audit, privacy review
```
### Example 3: Inspect team composition
**User**: "Who is on the sdlc-review team?"
**Action**:
```bash
aiwg team info sdlc-review
```
**Response**:
```
Team: sdlc-review
Description: Architecture, requirements, and test review
Dispatch: parallel
Agents:
architecture-designer [lead] Architecture quality and pattern review
requirements-analyst [contributor] Requirements traceability and completeness
test-architect [contributor] Testability and coverage gaps
technical-writer [reviewer] Clarity and documentation quality
Use cases:
- SAD review before Architecture Baseline Milestone
- Elaboration phase gate check
- ADR peer review
```
## Clarification Prompts
If the user names a task without a team:
- "Which team should I run? Available: sdlc-review, security-review, api-development, full-stack, greenfield, maintenance, migration"
If the team name is ambiguous:
- "Did you mean `security-review` or `sdlc-review`?"
## References
- @$AIWG_ROOT/src/cli/handlers/team.ts — Team command handler
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/teams/ — Built-in team definitions
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/teams/manifest.json — Team manifest
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/teams/schema.json — Team definition schema
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.