[bradygaster]

Summary

Fixes #66 — Squad init consistently skips user confirmation before creating the team.

Root Cause

Five reinforcing factors cause the LLM to skip the confirmation step:

1. List completion impulse — numbered lists trigger sequential completion behavior
2. Ambiguous conditional — On confirmation, create files reads as a soft gate
3. Eager Execution Philosophy — the prompt explicitly encourages launching aggressively
4. Parenthetical escape hatches — phrases like (or skip) allow implicit-yes interpretation
5. No structural turn boundary — nothing in the prompt structure forces a pause

Fix

Two-phase Init Mode split

• Phase 1: Propose the Team — ends with ask_user tool call and explicit STOP instruction
• Phase 2: Create the Team — only triggered when the user confirms

ask_user with selectable choices

• Step 5 now uses the ask_user tool with a choices array: ["Yes, hire this team", "Add someone", "Change a role"]
• This renders as a selectable menu in the CLI, matching what other Squad users see

Eager Execution exception

• Added explicit carve-out: "Eager Execution does NOT apply during Init Mode Phase 1"

Changes

• .github/agents/squad.agent.md — split Init Mode, added STOP gate, added Eager Execution exception
• test/init-flow.test.js — 8 new regression tests verifying prompt structure

Testing

All 53 tests pass (8 new + 45 existing):

• STOP gate present between phases
• ask_user referenced in Phase 1
• Step ordering (propose before create)
• Phase 2 gated on user confirmation
• No file creation in Phase 1
• Eager Execution exception present