init-mode

Squad setup is automated by proposing a Phase 1 roster when no squad exists, then awaiting explicit user confirmation before creating the structure. You review the proposed roster and approve it to proceed with seeding agents and directories.

Team orchestration supports multi-branch workflows by persisting casting state in stable, merge-friendly forms. It uses append-only logs via a union strategy to prevent conflicts across different branches.

Yes, git config user.name is required to personalize your squad roster. The setup enforces this safeguard by pulling your name from git configuration to ensure accurate agent personalization during the Phase 1 casting process.

Team context is stored in team.md under a fixed '## Members' header during initial squad orchestration. This ensures consistent structure and merge-friendly append-only logging for all team members.

If you don't confirm the proposed Phase 1 roster, the system will not create the .squad directory structure or seed agents. Phase 2 setup only begins after explicit user approval of the proposed team roster.