A-Team — Role-Based Project Team Coordination
Overview
Inspired by a.team: don't send solo agents — form a project team
with specific roles. A PM coordinates, engineers execute, specialists advise,
reviewers gate quality. The team has continuity across the project lifecycle.
Roles
| Role |
Agent |
Purpose |
pm |
Project Manager |
Reads brief, breaks into tasks, assigns to specialists, synthesizes final output |
engineer |
Implementation |
Writes code, runs commands, produces artifacts |
reviewer |
Quality Gate |
Checks engineer + specialist output, flags issues before PM synthesis |
specialist |
Domain Expert |
Configurable domain: "security", "ansible", "elixir", "performance", etc. |
Coordination Flow
Phase 1: PM Breakdown
┌─────────┐
│ PM │ reads brief → task list + role assignments
└────┬────┘
│
Phase 2: Parallel Execution
┌────┴────┬────────────┐
│ Engineer │ Specialist │ work assigned tasks in parallel
└────┬────┴─────┬──────┘
│ │
Phase 3: Review Gate
┌────┴──────────┴──┐
│ Reviewer │ checks all output, flags issues
└────────┬─────────┘
│
Phase 4: PM Synthesis
┌────────┴─────────┐
│ PM (final) │ integrates, writes summary/ship report
└──────────────────┘
Each phase runs explicitly via --phase 1|2|3|4 so you see output between phases.
Quick Start
# Phase 1: PM breaks down the project
nu ~/.claude/skills/a-team/a-team.nu --phase 1 \
--brief "Deploy gastown rate limiter to Pi fleet"
# Phase 2: Engineer + Specialist execute in parallel panes
nu ~/.claude/skills/a-team/a-team.nu --phase 2 \
--brief "Deploy gastown rate limiter to Pi fleet" \
--specialist "ansible"
# Phase 3: Reviewer checks output
nu ~/.claude/skills/a-team/a-team.nu --phase 3 \
--brief "Deploy gastown rate limiter to Pi fleet"
# Dry run any phase
nu ~/.claude/skills/a-team/a-team.nu --dry-run --phase 1 \
--brief "Deploy gastown rate limiter to Pi fleet"
When to Use: a-team vs tiger-team vs zellij-team
|
a-team |
tiger-team |
zellij-team |
| Shape |
Project team with roles |
Same problem, specialist lenses |
Parallel tasks, generic workers |
| Coordination |
Sequential phases + review gates |
Parallel analysis, synthesize |
Fire-and-forget parallel |
| Best for |
Multi-deliverable projects |
Deep investigation of one issue |
Independent, parallelizable tasks |
| PM? |
Yes — plans, assigns, synthesizes |
No — each lens is peer |
No — tasks are self-contained |
| Review gate? |
Yes — reviewer checks before ship |
No — synthesis is the gate |
No |
| Example |
"Deploy service to fleet: build, distribute, configure, verify" |
"Why is auth latency spiking?" |
"Fix these 5 independent bugs" |
Agent Flags
All agents run with --dangerously-skip-permissions --permission-mode bypassPermissions
by default. Override with --mode default for interactive permission prompts.
Output Convention
Each phase writes output to /tmp/a-team-<brief-hash>/:
phase1-pm-plan.md — PM's task breakdownphase2-engineer.md — Engineer's outputphase2-specialist.md — Specialist's outputphase3-review.md — Reviewer's findingsphase4-summary.md — PM's final synthesis
1---2name: a-team3description: Use when a project needs role-based team coordination — PM breakdown, parallel specialist execution, review gates. Best for multi-deliverable projects vs tiger-team (single problem) or zellij-team (independent tasks).4---56# A-Team — Role-Based Project Team Coordination78## Overview910Inspired by [a.team](https://a.team): don't send solo agents — form a **project team**11with specific roles. A PM coordinates, engineers execute, specialists advise,12reviewers gate quality. The team has continuity across the project lifecycle.1314## Roles1516| Role | Agent | Purpose |17|------|-------|---------|18| `pm` | Project Manager | Reads brief, breaks into tasks, assigns to specialists, synthesizes final output |19| `engineer` | Implementation | Writes code, runs commands, produces artifacts |20| `reviewer` | Quality Gate | Checks engineer + specialist output, flags issues before PM synthesis |21| `specialist` | Domain Expert | Configurable domain: "security", "ansible", "elixir", "performance", etc. |2223## Coordination Flow2425```26Phase 1: PM Breakdown27 ┌─────────┐28 │ PM │ reads brief → task list + role assignments29 └────┬────┘30 │31Phase 2: Parallel Execution32 ┌────┴────┬────────────┐33 │ Engineer │ Specialist │ work assigned tasks in parallel34 └────┬────┴─────┬──────┘35 │ │36Phase 3: Review Gate37 ┌────┴──────────┴──┐38 │ Reviewer │ checks all output, flags issues39 └────────┬─────────┘40 │41Phase 4: PM Synthesis42 ┌────────┴─────────┐43 │ PM (final) │ integrates, writes summary/ship report44 └──────────────────┘45```4647Each phase runs explicitly via `--phase 1|2|3|4` so you see output between phases.4849## Quick Start5051```bash52# Phase 1: PM breaks down the project53nu ~/.claude/skills/a-team/a-team.nu --phase 1 \54 --brief "Deploy gastown rate limiter to Pi fleet"5556# Phase 2: Engineer + Specialist execute in parallel panes57nu ~/.claude/skills/a-team/a-team.nu --phase 2 \58 --brief "Deploy gastown rate limiter to Pi fleet" \59 --specialist "ansible"6061# Phase 3: Reviewer checks output62nu ~/.claude/skills/a-team/a-team.nu --phase 3 \63 --brief "Deploy gastown rate limiter to Pi fleet"6465# Dry run any phase66nu ~/.claude/skills/a-team/a-team.nu --dry-run --phase 1 \67 --brief "Deploy gastown rate limiter to Pi fleet"68```6970## When to Use: a-team vs tiger-team vs zellij-team7172| | a-team | tiger-team | zellij-team |73|---|--------|------------|-------------|74| **Shape** | Project team with roles | Same problem, specialist lenses | Parallel tasks, generic workers |75| **Coordination** | Sequential phases + review gates | Parallel analysis, synthesize | Fire-and-forget parallel |76| **Best for** | Multi-deliverable projects | Deep investigation of one issue | Independent, parallelizable tasks |77| **PM?** | Yes — plans, assigns, synthesizes | No — each lens is peer | No — tasks are self-contained |78| **Review gate?** | Yes — reviewer checks before ship | No — synthesis is the gate | No |79| **Example** | "Deploy service to fleet: build, distribute, configure, verify" | "Why is auth latency spiking?" | "Fix these 5 independent bugs" |8081## Agent Flags8283All agents run with `--dangerously-skip-permissions --permission-mode bypassPermissions`84by default. Override with `--mode default` for interactive permission prompts.8586## Output Convention8788Each phase writes output to `/tmp/a-team-<brief-hash>/`:89- `phase1-pm-plan.md` — PM's task breakdown90- `phase2-engineer.md` — Engineer's output91- `phase2-specialist.md` — Specialist's output92- `phase3-review.md` — Reviewer's findings93- `phase4-summary.md` — PM's final synthesis
ryanmaclean