flow

## Agent Teams support If `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is set, use **Agent Teams** when a lifecycle stage fans out into parallel, coordinated work (e.g. build + test + review running together, or a multi-repo ship). This enables: - Stage agents share context mid-flight (the test agent surfaces a regression → the build agent pivots before review starts) - You can steer priorities in real time ("land the API change first, then docs") - Agents report progress as each stage completes, so you sequence the merge **Team setup** (only when the flag is enabled, and only for genuinely parallel stages): ``` TeamCreate("flow-lifecycle") Agent(team_name="flow-lifecycle", name="stage-build", ...) Agent(team_name="flow-lifecycle", name="stage-test", ...) ``` Steer with `SendMessage` / `broadcast`; share work via `TaskCreate`/`TaskUpdate`. If the flag is NOT set, fall back to standard fire-and-forget subagents (the default), or just route the stage to its single canonical command inline. ## Runtime Context Before routing, compute where the user is on the lifecycle: ```bash # FLOW_TARGET: the project you are actually working on. Default to the shell's # cwd, but pass an explicit path when the harness's tool cwd is not the project # (see the mode-resolution note below). FLOW_TARGET="${FLOW_TARGET:-$PWD}" FLOW_STATE="" for _d in "${CLAUDE_PLUGIN_ROOT:-}" \ "$HOME/Developer/repos/claude-ops/claude-ops" \ "$HOME/external-skills/claude-ops" \ "$...