team-builder

Compose cross-domain agent teams and dispatch them in parallel.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill team-builder-ggedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-builder
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/team-builder
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill team-builder-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.

Core Features & Use Cases

  • Browse available agents across domains and layouts.
  • Compose ad-hoc cross-domain teams.
  • Spawn agents in parallel for task execution.

Quick Start

Select domains or agents to form a team and spawn them in parallel for task execution.

Frequently Asked Questions about team-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assemble multiple agents to execute tasks in parallel?

Parallel agent execution is facilitated by dynamically discovering agents from local directories and dispatching them concurrently via the Agent tool using per-agent prompts.

What is the best way to compose ad-hoc cross-domain agent teams?

Composing cross-domain agent teams is handled through an interactive menu that supports browsing available agents across flat layouts and domain-subdirectory collections to form a custom team.

Can I select specific agents from a domain-subdirectory collection?

Yes, agent selection from domain-subdirectory collections is supported through dynamic discovery of local directories, allowing you to browse and pick specific experts for team assembly.

How do merge rules work when selecting agents across multiple domains?

Merge rules for domains dictate how agent collections are consolidated during team assembly, ensuring proper integration when composing ad-hoc cross-domain teams from separate domain layouts.

Do I need a specific directory layout to browse and spawn agent teams?

No specific layout is strictly required; the system works with both flat agent collections and domain-subdirectory layouts, dynamically discovering available agents from local directories.