From sdd
Implements multiple tasks in parallel using agent teams. Each teammate owns a set of independent tasks and follows TDD (Red-Green-Refactor). Uses shared task list for coordination. Use when user says "team implement", "parallel implement", "implement in parallel", "implement with team", or when there are 3+ independent tasks that touch different files. Do NOT use for sequential tasks with dependencies — use /implement instead. Do NOT use when agent teams are not enabled.
npx claudepluginhub robertraf/rob-agent-workflow --plugin sddThis skill uses the workspace's default tool permissions.
You are orchestrating **parallel task implementation** using agent teams. Each teammate owns independent tasks and follows strict TDD.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
You are orchestrating parallel task implementation using agent teams. Each teammate owns independent tasks and follows strict TDD.
You need the task list from /tasks. If it is not in context:
$ARGUMENTS
If $ARGUMENTS is empty and no task list is in context, ask the user to provide the tasks.
Before creating the team, analyze the task list:
Critical rule: Two teammates must NEVER edit the same file. If tasks share files, they must be sequential — assign them to the same teammate or set up task dependencies.
Based on the analysis:
/implement insteadIf fewer than 3 tasks can run in parallel, recommend /implement instead and ask the user to confirm.
Create an agent team with N teammates to implement tasks in parallel.
Each teammate must:
1. Follow strict TDD: Red → Green → Refactor for each behavior
2. Run tests after each cycle
3. Only work on their assigned files — never touch files owned by another teammate
4. Report completion of each task
Each teammate receives:
If task B depends on task A:
While teammates work:
If two teammates accidentally affect the same test suite:
Pause all teammates. Review the conflict. Reassign tasks to eliminate
the overlap, then resume.
After all teammates report completion:
# Run the full test suite
# Run the build
git diff --stat
Team Implementation Complete
✓ Tasks: N/N complete
✓ Teammates: N (all shut down)
✓ Tests: N passing, 0 failures
✓ Build: clean
✓ No file conflicts detected
Ready for: /review or /team-review
If any tests fail, diagnose whether it's a merge conflict between teammates' work or a genuine bug. Fix before reporting success.
Ask all teammates to shut down, then clean up the team.
| Situation | Use |
|---|---|
| 1-2 tasks or highly sequential work | /implement |
| 3+ independent tasks touching different files | /team-implement |
| Tasks with heavy interdependencies | /implement |
| Large feature with clear module boundaries | /team-implement |
| Quick bug fix | /implement |
| Multi-service or multi-layer changes | /team-implement |
These are common failure modes during parallel implementation. Watch for them:
utils.ts; Teammate B also adds a helper to utils.ts. Result: merge conflict, wasted work. Audit file assignments before spawning — if two teammates share ANY file, restructure.handleX, Teammate B names them processX. Without alignment, the codebase becomes inconsistent. Include explicit naming conventions in each teammate's prompt./review or /ship, not a PR.