@atlashub/smartstack-cli 3.30.0 → 3.31.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "3.30.0",
+  "version": "3.31.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/skills/business-analyse/SKILL.md

@@ -287,8 +287,8 @@ Load ONLY relevant categories based on feature type:
 
 **Team mode workflow (Propose & Review):**
 1. Steps 00-02 execute inline in the main conversation (interactive with user)
-2. After step-02 decomposition: `TeamCreate({ team_name: "ba-{appName}" })`
-3. For each module: spawn autonomous agent, agent proposes complete specification, team lead presents to user for validation
+2. After step-02 decomposition: clean up old team data (§1a), then `TeamCreate({ team_name: "ba-{appName}" })` — **CRITICAL: capture the RETURNED team name** (may differ from requested)
+3. For each module: spawn autonomous agent using the **returned** team name, agent proposes complete specification, team lead presents to user for validation
 4. After all modules specified: spawn consolidation agent (steps 04a + 04b), present report for user approval (04c)
 5. After consolidation approved: spawn handoff agent (steps 05a + 05b + 05c)
 6. `TeamDelete()` cleanup

package/templates/skills/business-analyse/references/team-orchestration.md

@@ -10,14 +10,34 @@
 
 After step-02 decomposition is complete and client has approved the module structure:
 
+### 1a. Clean Up Old Team Data (MANDATORY)
+
+Before creating the team, clean up any leftover data from previous sessions to prevent stale task collisions:
+
+```bash
+# Remove leftover task files from previous runs
+rm -f ~/.claude/tasks/ba-{appName}/*.json 2>/dev/null
+# Remove leftover team directory (TeamDelete may leave remnants)
+rm -rf ~/.claude/teams/ba-{appName} 2>/dev/null
 ```
-TeamCreate({ team_name: "ba-{appName}" })
+
+> **Why:** If a previous session used the same team name and crashed or was interrupted,
+> leftover task files will be picked up by new agents, causing them to receive stale
+> task_assignment notifications for wrong modules.
+
+### 1b. Create Team and Capture Actual Name
+
+```javascript
+const result = TeamCreate({ team_name: "ba-{appName}" });
+// CRITICAL: TeamCreate may return a DIFFERENT name than requested!
+// Always use the RETURNED team_name, not the requested one.
+const actualTeamName = result.team_name;
 ```
 
 Store team context for the session:
 ```javascript
 const teamContext = {
-  teamName: "ba-{appName}",
+  teamName: actualTeamName, // ← RETURNED name, NOT "ba-{appName}"
   moduleOrder: metadata.workflow.moduleOrder,
   dependencyLayers: dependencyGraph.layers || null,
   currentModuleIdx: 0,
@@ -26,6 +46,9 @@ const teamContext = {
 };
 ```
 
+> **WARNING:** NEVER hardcode `"ba-{appName}"` in subsequent calls.
+> Always use `teamContext.teamName` (the actual name returned by TeamCreate).
+
 ---
 
 ## 2. Module Agent Spawn — Sequential by Topological Order
@@ -54,7 +77,7 @@ Before spawning, gather the context the agent needs:
 ```javascript
 Task({
   subagent_type: "general-purpose",
-  team_name: "ba-{appName}",
+  team_name: teamContext.teamName, // ← ACTUAL name from TeamCreate result
   name: "mod-{moduleCode}",
   model: "opus",
   mode: "bypassPermissions",
@@ -257,7 +280,7 @@ Display: "═══ All modules specified — Starting consolidation ═══"
 ```javascript
 Task({
   subagent_type: "general-purpose",
-  team_name: "ba-{appName}",
+  team_name: teamContext.teamName, // ← ACTUAL name from TeamCreate result
   name: "consolidation",
   model: "opus",
   mode: "bypassPermissions",
@@ -316,7 +339,7 @@ After approval → shutdown consolidation agent → proceed to §6.
 ```javascript
 Task({
   subagent_type: "general-purpose",
-  team_name: "ba-{appName}",
+  team_name: teamContext.teamName, // ← ACTUAL name from TeamCreate result
   name: "handoff",
   model: "sonnet",
   mode: "bypassPermissions",
@@ -436,8 +459,9 @@ If the entire session crashes:
 1. User restarts `/business-analyse`
 2. Step-00 detects existing feature.json with `status: "decomposed"` or partial modules
 3. Reads `metadata.workflow.completedModules` to know which modules are done
-4. Creates new team, spawns agent for next incomplete module
-5. Continues normally
+4. **Cleans up old team/task data** (§1a cleanup step) before creating new team
+5. Creates new team (§1b — captures actual team name), spawns agent for next incomplete module
+6. Continues normally
 
 ---