agent-team-driven-development
Provides guidance on coordinating multiple specialized teammates working in parallel. This skill should be used when the user needs to execute complex implementation plans, resolve cross-cutting concerns, or coordinate independent work streams requiring communication.
Best use case
agent-team-driven-development is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Provides guidance on coordinating multiple specialized teammates working in parallel. This skill should be used when the user needs to execute complex implementation plans, resolve cross-cutting concerns, or coordinate independent work streams requiring communication.
Teams using agent-team-driven-development should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-team-driven-development/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-team-driven-development Compares
| Feature / Agent | agent-team-driven-development | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Provides guidance on coordinating multiple specialized teammates working in parallel. This skill should be used when the user needs to execute complex implementation plans, resolve cross-cutting concerns, or coordinate independent work streams requiring communication.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Agent Team Driven Development for Plan Execution Coordinate multiple specialized teammates working in parallel to execute complex implementation plans. ## Agent Teams vs Sub-agents Choose based on whether workers need to communicate with each other. | Dimension | Sub-agents | Agent Teams | |---|---|---| | **Communication** | Results return to caller only | Teammates message each other directly | | **Coordination** | Main agent manages all work | Shared task list with self-coordination | | **Best for** | Focused tasks where only the result matters | Complex work requiring discussion and collaboration | | **Token cost** | Lower | Higher: each teammate is a separate instance | Use **Sub-agents** for independent tasks needing no inter-worker communication (research, validation, file search). Use **Agent Teams** when teammates must share findings, challenge each other, or self-coordinate across 3+ parallel work streams. For sequential or highly interdependent tasks, use a single session. ## Execution Workflow 1. **Analyze plan** -- identify task independence, file conflicts, and required roles (Implementer, Reviewer, Architect) 2. **Spawn team** -- provide each teammate with task assignments, file paths, constraints, and verification criteria. Teammates do **not** inherit conversation history. 3. **Coordinate** -- monitor via shared task list, facilitate cross-teammate communication, use delegate mode (`Shift+Tab`) to keep the lead focused on coordination 4. **Verify and clean up** -- validate integration, run tests, shut down teammates, clean up team resources via the lead See `./references/initiate-team-workflow.md` and `./references/manage-team-workflow.md` for detailed workflows. ## Roles - **Implementer**: executes coding tasks on assigned files, follows TDD/BDD. See `./references/implementer-role.md`. - **Reviewer**: validates quality, security, and plan compliance. See `./references/reviewer-role.md`. - **Architect**: resolves cross-cutting concerns, maintains system-wide consistency. See `./references/architect-role.md`. ## Key Practices - Assign distinct file ownership per teammate to prevent edit conflicts - Include 5-6 tasks per teammate for steady throughput - Document task dependencies explicitly so blocked tasks wait automatically - Provide full context in spawn prompts (file paths, goals, constraints) - Require verification evidence (test results, etc.) upon task completion - Monitor frequently; unattended teams risk wasted effort For architecture, capabilities, and limitations, see `./references/official-documentation.md`.
Related Skills
build-like-iphone-team
Applies Apple's Project Purple design philosophy for radical innovation. This skill should be used when the user wants to challenge industry conventions, approach open-ended problems requiring disruptive thinking, or when standard brainstorming needs a breakthrough approach.
behavior-driven-development
Applies behavior-driven development principles including Gherkin scenarios and test-driven development. This skill should be used when the user asks to implement features, fix bugs, or when writing executable specifications and tests before writing production code.
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project. Always triggers when the user mentions updating or regenerating README files, especially for bilingual (EN/ZH) projects.
swiftui-review
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
writing-plans
Creates executable implementation plans that break down designs into detailed tasks. This skill should be used when the user has completed a brainstorming design and asks to "write an implementation plan" or "create step-by-step tasks" for execution.
systematic-debugging
Provides a systematic debugging methodology with a 4-phase root cause analysis process. This skill should be used when the user reports a bug, error, test failure, or unexpected behavior, ensuring thorough investigation precedes any code changes.
need-vet
This skill should be used when the user invokes /need-vet to enable work verification for the current task. Claude must verify completion and append the verified tag before the session can end.
executing-plans
Executes written implementation plans efficiently using agent teams or subagents. This skill should be used when the user has a completed plan.md, asks to "execute the plan", or is ready to run batches of independent tasks in parallel following BDD principles.
brainstorming
Structures collaborative dialogue to turn rough ideas into implementation-ready designs. This skill should be used when the user has a new idea, feature request, ambiguous requirement, or asks to "brainstorm a solution" before implementation begins.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
refactor
Executes automated refactoring for specific files, directories, or semantic queries. This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes "/refactor".
refactor-project
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".