--- name: spawn-teammates description: > Reproducible teammate creation during Sprint Planning. Reads Sprint and Backlog state, spawns Developer teammates via Agent Teams with consistent naming and assignment. disable-model-invocation: false --- ## Inputs - `sprint.json` → pbi_ids, developer_count - `backlog.json` → Sprint PBIs ## Outputs - `sprint.json` → developers[] populated, status: "active" - Agent Teams teammates spawned ## Preconditions - state.json phase: "sprint_planning" or "integration_sprint" - sprint.json status: "planning", pbi_ids set - backlog.json PBIs status: refined matching pbi_ids ## Steps 0. **Freeze Sprint base.** Run `bash .scrum/scripts/freeze-sprint-base.sh`. This captures `sprint.json.base_sha = $(git rev-parse HEAD)` exactly once per Sprint. PBI worktrees fork from this commit. 1. Read sprint.json→developer_count, pbi_ids 2. Read backlog.json→PBI details 3. developer_count = min(Sprint refined PBIs, 6). **1 Developer = 1 PBI** 4. Extract Sprint number N from sprint.json id (e.g., "sprint-001"→1) 5. Each Developer: a. ID: `dev-001-s{N}`, `dev-002-s{N}` (zero-pad + -s{N} mandatory, no short forms) b. Implement assignment from backlog.json implementer_id c. Review assignment: round-robin (no self-review, single-PBI→"scrum-master") d. Entry: `{"id": "dev-001-s{N}", "assigned_work": {"implement": [...], "review": [...]}, "status": "active", "sub_agents": []}` 5.5. **Create PBI worktrees.** For each PBI assigned in this Sprint run: ``` bash .scrum/scripts/create-pbi-worktree.sh ``` This creates `.scrum/worktrees/` checked out at `pbi/` forked from `sprint.base_sha`, sets up the `.scrum` symlink, and writes `branch`, `worktree`, `base_sha` into `.scrum/pbi//state.json`. 6. **Reconcile backlog.json**: Update all PBI implementer_id/reviewer_id to match final dev-NNN-sN IDs 7. Update sprint.json→developers[] + developer_count (TUI dashboard reads both) 8. Spawn Agent Teams teammates (agents/developer.md). Name = exact ID from 5a. Compute `PROJECT_ROOT=$(git rev-parse --show-toplevel)` at spawn time and substitute it into the task prompt below in place of ``. Each Developer's `` is the one assigned to them in 5a/6. Task: ``` Your working directory: /.scrum/worktrees/ First action: cd "/.scrum/worktrees/" All file operations and commits must stay inside this directory. Use `.scrum/scripts/commit-pbi.sh` for commits — never raw `git commit`. Execute these skills in order for your assigned PBIs: 1. Invoke the `design` skill 2. Invoke the `implementation` skill 3. Invoke the `cross-review` skill Do NOT skip or reorder these steps. When the pbi-pipeline reaches phase=complete, run `.scrum/scripts/mark-pbi-ready-to-merge.sh ` and notify SM: `[] PBI_READY_TO_MERGE branch=pbi/ sha=`. Then stop and wait. ``` 9. Verify all teammates active + assignments received 10. sprint.json → status: "active" Ref: FR-007 ## Re-Spawn Recovery (FR-022) When Teammate Liveness Protocol detects terminated Developer: 1. Read `sprint.json`→get developer entry + assigned_work 2. Read `backlog.json`→get PBI status to determine remaining work 3. Update `sprint.json` developer status: "failed" 4. Spawn new teammate: same ID (e.g., `dev-001-s{N}`), `agents/developer.md` 5. Task prompt = remaining work only: - PBI in design→"Run design skill for PBI-XXX, then implementation skill" - PBI in implementation→"Resume implementation for PBI-XXX. Design docs at: ..." - PBI in review (fix needed)→"Fix review findings for PBI-XXX: [findings]. Source at: ..." 6. Update `sprint.json` developer status: "active" ## Exit Criteria - sprint.json developers[] = developer_count entries - All Developers: assigned_work.implement[] non-empty, review[] non-empty (or scrum-master) - No self-review - All teammates spawned + active - sprint.json status: "active"