init-mode

Init Mode proposes a roster and secures explicit user confirmation before any team structure is created. It applies to onboarding workflows where no squad exists, guiding a Phase-1 proposal into Phase-2 execution while withholding filesystem changes until approval.

You use the ask_user tool to present roster choices and capture explicit confirmation. Upon approval, the workflow initializes the .squad state, seeds agents for Phase 2 execution, and captures casting decisions and audit trails.

The safest way to manage team initiation is to propose a roster and withhold all filesystem changes until explicit user confirmation is captured. This prevents premature file creation by storing casting decisions and audit trails in a standardized .squad state only after approval.

Yes, this workflow applies to scenarios where no squad exists or where the roster must be refined through user input. It uses the ask_user tool to present choices, capturing casting decisions and audit trails in a .squad state before proceeding to Phase 2 execution.

A Phase-1 proposal transitions into Phase-2 execution after explicit user confirmation is secured. The workflow then initializes the .squad state and seeds agents for Phase 2, capturing casting decisions, seeds, and audit trails in a standardized format.