speccrew 0.7.14 → 0.7.15

package/.speccrew/agents/speccrew-team-leader.md

@@ -193,10 +193,40 @@ When you load a dispatch skill (e.g., `speccrew-knowledge-bizs-dispatch` or `spe
    - `run-script` → Terminal tool
    - `run-skill` → Skill tool (do NOT browse directories for SKILL.md)
    - `dispatch-to-worker` → Task tool (create Task for speccrew-task-worker)
-4. **For `<loop parallel="true">` with `dispatch-to-worker`**: create ALL worker Tasks in ONE batch
-5. **For `<event action="confirm">`**: present to user and wait
-6. **For `<checkpoint>`**: verify condition before proceeding to next stage
-7. **Execute ALL stages in sequence** — Stage 0 → 1a → 1b → 1c → 2 → 3 → 4 (or as defined)
+4. **For `<event action="confirm">`**: present to user and wait
+5. **For `<checkpoint>`**: verify condition before proceeding to next stage
+6. **Execute ALL stages in sequence** — Stage 0 → 1a → 1b → 1c → 2 → 3 → 4 (or as defined)
+
+### ⚠️ Parallel Worker Dispatch Protocol (MANDATORY)
+
+When executing a `<loop parallel="true">` block that contains `action=dispatch-to-worker`:
+
+1. **COLLECT FIRST**: Iterate through ALL items in the loop's `over` array BEFORE creating any Task
+2. **BATCH CREATE**: Create ALL Worker Tasks in a **SINGLE message** using **MULTIPLE Task tool calls in parallel**
+3. **NO SEQUENTIAL WAIT**: Do NOT wait for any Worker Task to complete before creating the next one
+4. **ONE WORKER PER ITEM**: Each loop iteration = exactly ONE separate Worker Task with its own context
+
+**FORBIDDEN behaviors:**
+- Creating one Task, waiting for completion, then creating the next → **FORBIDDEN**
+- Passing multiple items to a single Worker → **FORBIDDEN**
+- Processing loop items one-by-one with blocking waits between dispatches → **FORBIDDEN**
+
+**CORRECT execution pattern:**
+```
+Loop items: [A, B, C, D, E]
+↓
+Turn 1: TaskCreate(A) + TaskCreate(B) + TaskCreate(C) + TaskCreate(D) + TaskCreate(E)  ← ALL in ONE turn
+↓
+Turn 2-N: Monitor and collect results as Workers complete
+```
+
+**INCORRECT execution pattern (FORBIDDEN):**
+```
+Turn 1: Create Task(A) → wait for completion
+Turn 2: Create Task(B) → wait for completion
+Turn 3: Create Task(C) → wait for completion
+...
+```
 
 **CRITICAL FORBIDDEN BEHAVIORS**:
 - Do NOT run terminal commands as a substitute for calling a Skill via Skill tool

package/.speccrew/skills/speccrew-team-leader-routing/workflow.agentflow.xml

@@ -97,8 +97,16 @@
         <block type="gateway" id="P05-G3" mode="exclusive" desc="Check techs knowledge base">
           <branch test="${techs_kb.exists} == false" name="Techs Not Initialized">
             <block type="event" id="P05-E3" action="log" desc="Guide to initialize techs knowledge base"/>
-            <block type="rule" id="P05-R-TECHS" level="mandatory" desc="Parallel worker dispatch for techs">
-              <field name="text">When techs-dispatch Stage 2 prepares task plans for multiple platforms, dispatch ALL platform workers IN PARALLEL — DO NOT execute sequentially</field>
+            <block type="rule" id="P05-R-TECHS" level="mandatory" desc="PARALLEL BATCH DISPATCH - MANDATORY">
+              <field name="text">=== PARALLEL BATCH DISPATCH PROTOCOL ===</field>
+              <field name="text">1. COLLECT ALL items from loop's 'over' array BEFORE creating any Task</field>
+              <field name="text">2. Create ALL Worker Tasks in ONE message using MULTIPLE Task tool calls in parallel</field>
+              <field name="text">3. DO NOT wait for any Task to complete before creating the next one</field>
+              <field name="text">4. Each loop item = exactly ONE separate Worker Task</field>
+              <field name="text">=== FORBIDDEN ===</field>
+              <field name="text">- Create Task(A), wait, then Create Task(B) → FORBIDDEN</field>
+              <field name="text">- Passing multiple items to one Worker → FORBIDDEN</field>
+              <field name="text">- Sequential processing with blocking waits → FORBIDDEN</field>
             </block>
             <block type="task" id="P05-B5" action="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
               <field name="skill">speccrew-knowledge-techs-dispatch</field>
@@ -107,8 +115,16 @@
           </branch>
           <branch test="${bizs_kb.exists} == false" name="Bizs Not Initialized">
             <block type="event" id="P05-E4" action="log" desc="Guide to initialize bizs knowledge base"/>
-            <block type="rule" id="P05-R-BIZS" level="mandatory" desc="Parallel worker dispatch for bizs">
-              <field name="text">When bizs-dispatch prepares worker task plans, dispatch ALL workers IN PARALLEL per stage — DO NOT execute sequentially</field>
+            <block type="rule" id="P05-R-BIZS" level="mandatory" desc="PARALLEL BATCH DISPATCH - MANDATORY">
+              <field name="text">=== PARALLEL BATCH DISPATCH PROTOCOL ===</field>
+              <field name="text">1. COLLECT ALL items from loop's 'over' array BEFORE creating any Task</field>
+              <field name="text">2. Create ALL Worker Tasks in ONE message using MULTIPLE Task tool calls in parallel</field>
+              <field name="text">3. DO NOT wait for any Task to complete before creating the next one</field>
+              <field name="text">4. Each loop item = exactly ONE separate Worker Task</field>
+              <field name="text">=== FORBIDDEN ===</field>
+              <field name="text">- Create Task(A), wait, then Create Task(B) → FORBIDDEN</field>
+              <field name="text">- Passing multiple items to one Worker → FORBIDDEN</field>
+              <field name="text">- Sequential processing with blocking waits → FORBIDDEN</field>
             </block>
             <block type="task" id="P05-B6" action="run-skill" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
               <field name="skill">speccrew-knowledge-bizs-dispatch</field>
@@ -149,9 +165,16 @@
         </block>
       </branch>
       <branch test="${intent} == 'knowledge_bizs'" name="Bizs Knowledge Base">
-        <block type="rule" id="P1-R-BIZS" level="mandatory" desc="Bizs dispatch parallel execution rules">
-          <field name="text">When bizs-dispatch prepares worker task plans for multiple features or platforms, dispatch ALL workers IN PARALLEL — DO NOT execute features or platforms sequentially one by one</field>
-          <field name="text">Each Worker (analysis, graph, summarize) runs independently — dispatch all of them at once per stage, then monitor completion markers</field>
+        <block type="rule" id="P1-R-BIZS" level="mandatory" desc="PARALLEL BATCH DISPATCH - MANDATORY">
+          <field name="text">=== PARALLEL BATCH DISPATCH PROTOCOL ===</field>
+          <field name="text">1. COLLECT ALL items from loop's 'over' array BEFORE creating any Task</field>
+          <field name="text">2. Create ALL Worker Tasks in ONE message using MULTIPLE Task tool calls in parallel</field>
+          <field name="text">3. DO NOT wait for any Task to complete before creating the next one</field>
+          <field name="text">4. Each loop item = exactly ONE separate Worker Task</field>
+          <field name="text">=== FORBIDDEN ===</field>
+          <field name="text">- Create Task(A), wait, then Create Task(B) → FORBIDDEN</field>
+          <field name="text">- Passing multiple items to one Worker → FORBIDDEN</field>
+          <field name="text">- Sequential processing with blocking waits → FORBIDDEN</field>
         </block>
         <block type="task" id="P1-B3" action="run-skill" status="pending" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
           <field name="skill">speccrew-knowledge-bizs-dispatch</field>
@@ -159,9 +182,16 @@
         </block>
       </branch>
       <branch test="${intent} == 'knowledge_techs'" name="Techs Knowledge Base">
-        <block type="rule" id="P1-R-TECHS" level="mandatory" desc="Techs dispatch parallel execution rules">
-          <field name="text">When techs-dispatch Stage 2 prepares task plans for multiple platforms, dispatch ALL platform workers IN PARALLEL using concurrent task dispatch — DO NOT execute platforms sequentially one by one</field>
-          <field name="text">Each platform worker (techs-generate-conventions, techs-generate-ui-style) runs independently — dispatch all of them at once, then monitor completion markers</field>
+        <block type="rule" id="P1-R-TECHS" level="mandatory" desc="PARALLEL BATCH DISPATCH - MANDATORY">
+          <field name="text">=== PARALLEL BATCH DISPATCH PROTOCOL ===</field>
+          <field name="text">1. COLLECT ALL items from loop's 'over' array BEFORE creating any Task</field>
+          <field name="text">2. Create ALL Worker Tasks in ONE message using MULTIPLE Task tool calls in parallel</field>
+          <field name="text">3. DO NOT wait for any Task to complete before creating the next one</field>
+          <field name="text">4. Each loop item = exactly ONE separate Worker Task</field>
+          <field name="text">=== FORBIDDEN ===</field>
+          <field name="text">- Create Task(A), wait, then Create Task(B) → FORBIDDEN</field>
+          <field name="text">- Passing multiple items to one Worker → FORBIDDEN</field>
+          <field name="text">- Sequential processing with blocking waits → FORBIDDEN</field>
         </block>
         <block type="task" id="P1-B4" action="run-skill" status="pending" desc="Leader directly invokes techs-dispatch as orchestration playbook">
           <field name="skill">speccrew-knowledge-techs-dispatch</field>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.7.14",
+  "version": "0.7.15",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {