imabusyman/team-builder
prompts/squad/skills/team-builder/SKILL.md
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add imabusyman/CodebrewRouter team-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:21 PM124.9s1 file scanned
SKILL.md
- name:
- team-builder
- description:
- Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
Team Builder — compose parallel agent teams
Decomposes complex tasks into parallel streams and assigns each stream to the right specialist.
When to use
- A task naturally splits into independent subtasks (e.g., API changes + tests + deployment wiring).
- You have multiple specialist roles available (Coder, Tester, Infra, Architect).
- Subtasks have non-overlapping file ownership and can run in parallel.
Workflow
1. Decompose the task
List all subtasks and identify dependencies:
Task: Add a new provider
├─ Subtask 1: Core provider implementation (Coder)
├─ Subtask 2: Unit + integration tests (Tester)
├─ Subtask 3: Aspire AppHost wiring (Infra)
└─ Subtask 4: ADR + design notes (Architect)
Dependencies: Coder → Tester → Infra (sequential)
Architect ∥ Coder (parallel)
2. Map to roles & estimate
Assign each subtask to the best-fit specialist:
| Subtask | Role | Files | Est. effort |
|---|---|---|---|
| Core provider | Coder | Infrastructure/Providers/** | M |
| Tests | Tester | Tests/** | M |
| AppHost | Infra | AppHost/**, ServiceDefaults/** | S |
| ADR | Architect | Docs/design/adr/** | S |
3. Check for conflicts
- No shared files across parallel subtasks (each agent owns a disjoint set).
- Dependencies are explicit (e.g., "Tester waits for Coder").
4. Create delegation handoffs
Per-agent handoff with:
- Files you may edit (exclusive lock).
- Artifacts to re-read (spec, plan, prior ADRs).
- Pending decisions (from prior phases).
Team composition rules
- Max 4 agents in parallel (Conductor can manage).
- One role per phase (Architect before Coder before Tester before Reviewer).
- File locks are disjoint (no two agents editing the same file).
- Clear dependencies (if B depends on A, state it in B's handoff).
See also
dispatching-parallel-agents— automate agent assignment.claude-devfleet— use Git worktrees for isolated workspaces.quality-gate— ensure parallel builds pass-warnaserror+ 95% coverage before merge.
Related Skills
imabusyman/write-a-prd
development
VerifiedTrustedCommunity
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
SKILL.mdUpdated Apr 25, 2026
imabusyman/subagent-driven-development
development
VerifiedTrustedCommunity
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
SKILL.mdUpdated Apr 25, 2026
imabusyman/reasoning
testing
VerifiedTrustedCommunity
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
SKILL.mdUpdated Apr 25, 2026
imabusyman/quality-gate
development
VerifiedTrustedCommunity
Enforce the -warnaserror build + 95% coverage test gate on every squad [DONE]. Use this before any specialist (Coder, Tester, Reviewer, Infra) marks a phase complete.
SKILL.mdUpdated Apr 25, 2026