| name | implementation-team |
| description | Multi-agent implementation team for parallel code execution.
Transforms specs, task descriptions, and feature requests into working code
using coordinated Agent Teams with an Opus lead and Sonnet teammates.
Supports parallel implementation, architect review, test writing, and
external research via Perplexity MCP.
Keywords: implementation, agent-teams, parallel, orchestration,
code-review, testing, spec, feature, multi-agent.
|
Implementation Team
A multi-agent implementation framework using Claude Code Agent Teams. All commands use the team: namespace.
Available Commands
| Command | Description |
|---|
/team:init | Initialize project configuration (tech stack, conventions, quality gates) |
/team:implement <spec-or-description> | Implement a spec or feature using parallel agent teams |
/team:research <question> | Research a question using codebase exploration and Perplexity |
When to Use
Use this plugin when:
- You have a spec or detailed feature description ready for implementation
- You want parallel implementation across multiple files/modules
- You need coordinated code review and test writing
- You want quality gates (lint, static analysis, tests) enforced automatically
Workflow
/team:init → /team:implement <spec>
- Run
/team:init once per project to configure tech stack, conventions, and quality gates
- Run
/team:implement with a spec file path or inline description to execute the full implementation pipeline
Team Composition
The team scales based on spec complexity:
| Size | Implementers | Architect | Researcher | Test Writer |
|---|
| Small (1-3 files) | 1 | No | No | 1 |
| Medium (4-10 files) | 2 | Yes | No | 1 |
| Large (10+ files) | 3 | Yes | Yes | 1 |
