init-mode

Automating team setup requires proposing a cross-functional roster and waiting for user confirmation before creating files. This workflow initializes the .squad state, including casting state and templates, to enable subsequent Phase 2 execution safely.

Explicit user approval for workflow orchestration prevents accidental changes and scope creep. By enforcing confirmation via the ask_user tool prior to Phase 2 execution, it ensures traceability and guards against misconfiguration during initial team setup.

Casting state initialization sets up the .squad state with agents and templates to support Phase 2 creation. You need it when coordinating cross-functional team setup to ensure required roster roles and states are provisioned before workflow actions begin.

Yes, you can propose a cross-functional roster for Phase 1 and wait for explicit user confirmation before any files are created. This approach ensures the proposed squad state and templates are safely provisioned without accidental modifications.

The best way to coordinate Phase 1 team setup is to automate roster proposals and enforce explicit confirmation. Initializing the squad state only after approval prevents scope creep and ensures template provisioning happens securely.

Team initiation requires manual approval before provisioning templates for Phase 2. The system enforces explicit user confirmation via the ask_user tool to guard against accidental changes and ensure traceability before executing any subsequent actions.