init-mode

Automate initial squad setup by generating and validating a persistent .squad structure, including casting decisions and agent histories. The process proposes a team roster, awaits user confirmation, and seeds the registry to enable traceable collaboration across sessions.

Squad initialization coordinates team setup and project governance by generating a persistent .squad structure. You need it during Phase 1 proposal and Phase 2 creation to establish casting policies, registries, and agent histories for new projects.

Create the .squad state through structured Phase 2 creation automation. This seeds the casting policy, registry, and agent histories, ensuring continuity and traceable collaboration across multiple sessions without losing squad context.

Yes, you must confirm the team roster proposal. When no .squad/team.md file exists, the system proposes an initial roster in Phase 1 and explicitly awaits your confirmation via user interaction before proceeding with project creation.

Ensure traceable collaboration by seeding the .squad registry and agent histories during initialization. This persistent state structure enables continuity across sessions, safely handling project context and recording casting decisions.

The automated team initialization requires explicit user confirmation before applying roster proposals. It is designed specifically for Phase 1 proposal and Phase 2 creation, meaning it handles initial setup rather than ongoing squad management or modifications.