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.
- Installs
- 100
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/fradser/dotclaude --skill agent-team-driven-development- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads agent-team-driven-development automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Analyze plan -- identify task independence, file conflicts, and required roles (Implementer, Reviewer, Architect)
- Spawn team -- provide each teammate with task assignments, file paths, constraints, and verification criteria. Teammates do not inherit conversation history.
- Coordinate -- monitor via shared task list, facilitate cross-teammate communication, use delegate mode (
Shift+Tab) to keep the lead focused on coordination - 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.
FAQ
What does the agent-team-driven-development 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.
How do I install agent-team-driven-development?
Run npx skills add https://github.com/fradser/dotclaude --skill agent-team-driven-development in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/agent-team-driven-development/ (personal) or .claude/skills/agent-team-driven-development/ (project).
Which AI agents can use agent-team-driven-development?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is agent-team-driven-development safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains agent-team-driven-development?
It is published by fradser in fradser/dotclaude. It has 100 recorded installs.
More from fradser/dotclaude
patent-architect
fradser/dotclaude
Automatically searches prior art via SerpAPI and generates Chinese patent application forms. This skill should be used when the user wants to generate Chinese patent application forms, or mentions "patents", "inventions", or wants to protect technical innovations.
agent-browser
fradser/dotclaude
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
behavior-driven-development
fradser/dotclaude
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.
commit-and-push
fradser/dotclaude
Creates clean conventional git commits using standard git and pushes changes to the remote repository. Use when the user asks to "commit and push", "push changes", or complete a commit followed by git push.
executing-plans
fradser/dotclaude
Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.
brainstorming
fradser/dotclaude
Designs new software features and multi-component changes for the current repo into implementation-ready BDD specs via autonomous codebase research, then commits the design for review (runs to completion without mid-design questions). Scope covers new features, greenfield design, and multi-component changes. Not for hardware/physical-system design, out-of-repo questions, single-file refactors, or known-root-cause bugs (those go to direct edits or systematic-debugging).
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.