feat: make Agent Teams the primary execution model for /construct

Restructure the construct skill so that Agent Teams (parallel teammate
spawning, monitor/react loop, per-unit hat tracking) is the primary
execution path when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set.
The previous sequential subagent approach is preserved as a fallback.

- construct: Add team create/reconnect, parallel unit spawn, monitor
  loop, team shutdown, and unitStates/teamName schema in iteration.json
- advance: Add Step 2c to spawn newly unblocked units as teammates
- fail: Add Step 4b with retry tracking (max 3) and teammate re-spawn
- reset: Add Step 1b for team cleanup (shutdown + TeamDelete)
- resume: Add Step 5b for team reconnection on resume
- enforce-iteration: Add teammate guard so unit sessions exit early
- subagent-context: Add Team Communication instructions for teammates
- inject-context: Add Agent Teams status display in session context

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jwaldrip

hooks/enforce-iteration.sh

@@ -37,6 +37,15 @@ if [ -z "$ITERATION_JSON" ] && [[ "$CURRENT_BRANCH" == ai-dlc/*/* ]]; then
   ITERATION_JSON=$(han keep load --branch "$INTENT_BRANCH" iteration.json --quiet 2>/dev/null || echo "")
 fi
 
+# Unit-branch sessions (teammates or subagents) should NOT be told to /construct
+# The orchestrator on the intent branch manages the construction loop
+if [ -n "$INTENT_BRANCH" ]; then
+  echo "## AI-DLC: Unit Session Ending"
+  echo ""
+  echo "Ensure you committed changes and saved progress."
+  exit 0
+fi
+
 if [ -z "$ITERATION_JSON" ]; then
   # No AI-DLC state - not using the methodology, skip
   exit 0

hooks/inject-context.sh

@@ -439,6 +439,19 @@ if [ -n "$INTENT_DIR" ] && [ -d "$INTENT_DIR" ] && ls "$INTENT_DIR"/unit-*.md 1>
     fi
 fi
 
+# Display Agent Teams status if enabled
+if [ -n "${CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:-}" ]; then
+  TEAM_NAME="ai-dlc-${INTENT_SLUG}"
+  TEAM_CONFIG="$HOME/.claude/teams/${TEAM_NAME}/config.json"
+  if [ -f "$TEAM_CONFIG" ]; then
+    echo "### Agent Teams"
+    echo ""
+    echo "**Team:** \`${TEAM_NAME}\`"
+    echo "**Mode:** Parallel execution enabled"
+    echo ""
+  fi
+fi
+
 # Load hat instructions from markdown files
 # Resolution order: 1) User override (.ai-dlc/hats/), 2) Plugin built-in (hats/)
 HAT_FILE=""

hooks/subagent-context.sh

@@ -287,3 +287,15 @@ echo ""
 echo "Output status messages directly - users see them in real-time."
 echo "Document blockers in \`han keep save blockers.md\` for persistence (unit-scoped)."
 echo ""
+
+# Team communication instructions (Agent Teams mode)
+if [ -n "${CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:-}" ]; then
+  echo "### Team Communication"
+  echo ""
+  echo "You are a **teammate** in an Agent Teams session."
+  echo "- Report completion/issues to team lead via SendMessage"
+  echo "- Do NOT call /construct, /advance, or /fail — the lead handles orchestration"
+  echo "- Use TaskUpdate to mark shared tasks as completed when done"
+  echo "- Coordinate with other teammates through the team lead"
+  echo ""
+fi

skills/advance/SKILL.md

@@ -101,6 +101,28 @@ ${dagSummary.blockedUnits.join('\n')}
 Review blockers and unblock units to continue.`;
 ```
 
+### Step 2c: Spawn Newly Unblocked Units (Agent Teams)
+
+When `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is enabled and completing a unit unblocks new units:
+
+```bash
+AGENT_TEAMS_ENABLED="${CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:-}"
+```
+
+If `AGENT_TEAMS_ENABLED` is set and `readyCount > 0` after completing a unit:
+
+1. Read `teamName` from `iteration.json`
+2. For each newly ready unit:
+   - Initialize `unitStates.{unit}.hat = "planner"` and `unitStates.{unit}.retries = 0`
+   - Create unit worktree
+   - Mark unit as `in_progress`
+   - Spawn planner teammate via Task with `team_name` and `name`
+3. Save updated state to `iteration.json`
+
+This replaces the sequential "loop back to builder" behavior when Agent Teams is active. Instead of the lead picking up the next unit sequentially, newly unblocked units are spawned as parallel teammates immediately.
+
+**Without Agent Teams:** The existing behavior (reset hat to builder, let `/construct` pick next unit) continues unchanged.
+
 ### Step 3: Update State
 
 ```bash