team-builder

Topics in the source

• Team Builder
• When to Use
• Prerequisites
• Configuration
• How It Works
• Step 1: Discover Available Agents
• Step 2: Present Domain Menu
• Step 3: Handle Selection

Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections. You have multiple agent personas (markdown files) and want to pick which ones to use for a task You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture) You want to browse what agents are available before deciding Agent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first # Heading is used as the agent name and the first paragraph as the description. Both flat and subdirectory layouts are supported: Subdirectory layout — domain is inferred from the folder name: Flat layout — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to "General". Note: the algorithm splits at the first -, so multi-word domains (e.g., product-management) should use the subdirectory layout instead: Agents are discovered via two methods, merged and deduplicated by agent name: 1. claude agents command (primary) — run claude agents to get all agents known to the CLI, including user agents, plugin agents (e.g. ecc:arch

This is an excerpt. Refer to the complete source and its current requirements.