spawn-team

Automating squad creation involves resolving a crew profile, provisioning per-builder worktrees, and registering the team with the harness for dispatch. This removes manual orchestration by handling roster expansion, worktree seeding, and idle readiness checks automatically.

Automated team spawning applies gatekeeping for epic, backlog, and brief handling as described in the crew policy. It supports both execution and discovery crew profiles, ensuring proper policy enforcement before proceeding with device provisioning and member spawning.

To provision worktrees and seed env files, the automation expands the profile roster, allocates per-builder worktrees, handles epic branching if requested, and seeds the worktrees with necessary environment files before spawning agents.

Yes, resolving a phonetic team name registers the squad via TeamCreate while managing idempotency against existing teams. It checks for phantom slots and existing registrations to prevent duplicate squad creation during the dispatch setup.

Waiting for agent idle readiness involves spawning per-member agents, monitoring for idle readiness notifications, and producing a squadkit-specific manifest. Once all members are ready, the final handoff to the orchestrator completes the multi-step workflow.