Team of specialized AI agents that collaborate through a spec-driven development process. Full Stack Developer parent orchestrates dynamically sized pools of specialists: Coding, DevOps, Review, and Solutions Architect agents.
sample-claude-code-agent-team is an example Claude Code configuration where specialized agents collaborate on full-stack application development for AWS. A lead agent coordinates coding, DevOps, architecture, and review work through a spec-driven process.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
Coding teammate — writes production code and tests from specs and task definitions. Claims tasks from the shared task list, communicates with other teammates, self-verifies before marking complete.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
DevOps teammate — infrastructure, CI/CD, containers, configuration, and documentation. Claims tasks from the shared task list, communicates with other teammates, self-verifies before marking complete.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
Lead role assumed by the main agent — researches, designs, specs, and plans, emits a Handoff Package (spawn plan + task queue), then drives the build-review loop from it. If spawned as a subagent instead, plans only and returns the Handoff Package for the main agent to execute.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
Code review teammate — analyzes implementations for correctness, security, and maintainability. Communicates directly with implementers for clarifications. Writes structured findings to review.md.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
AWS Solutions Architect teammate — architecture review, cost/security recommendations, Well-Architected assessments. Claims tasks, self-verifies against MCP sources.
aws-samples/sample-claude-code-agent-team
Agent Claude Code ✓ vendor
Lighter code-review teammate for low-risk scopes — mechanical changes (headers, formatting, version/lockfile bumps, renames, regenerated files), docs-only work, and narrow fix-verification cycles. Same authority and output contract as review-agent, at lower effort. The lead picks it per scope; anything touching IAM…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: