speccrew 0.7.57 → 0.7.58

package/.speccrew/agents/speccrew-system-designer.md

@@ -786,6 +786,20 @@ node {update_progress_script} update-task --file {iterations_dir}/{current}/03.s
 
 All workers execute simultaneously to maximize efficiency.
 
+> 🛑 **CRITICAL: Phase 5 dispatch-to-worker Protocol**
+> 1. **ONE Worker per Feature×Platform combination** — DO NOT group
+> 2. Use **Agent tool** to create `speccrew-task-worker` for each task
+> 3. Pass `skill_path`: `${ide_skills_dir}/${skill_name}/SKILL.md` (platform-specific skill)
+> 4. Pass context: task_id, feature_id, feature_name, platform_id, feature_spec_path, api_contract_path, techs_knowledge_paths, framework_decisions, output_base_path
+> 5. Dispatch ALL Workers in the same batch **SIMULTANEOUSLY** in a single turn
+> 6. **Wait** for ALL Workers in the batch to complete before dispatching next batch
+> 7. Update DISPATCH-PROGRESS.json after each Worker completes
+> **FORBIDDEN**:
+> - ❌ DO NOT group multiple features into one Worker
+> - ❌ DO NOT use Skill tool to invoke platform skills (when Features ≥ 2 OR Platforms ≥ 2)
+> - ❌ DO NOT dispatch Workers sequentially — ALL in same batch must be simultaneous
+> - ❌ DO NOT generate *-design.md files yourself as fallback
+
 ### 5.5 Update DISPATCH-PROGRESS.json
 
 After each worker completes, parse its **Task Completion Report** and update:

package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.md

@@ -119,6 +119,30 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
 
 **CRITICAL**: The `Agent tool` creates a NEW agent session — this is completely different from the `Skill tool` which executes inline.
 
+### Phase 5 Execution Method — Feature×Platform Worker Dispatch
+
+**DISPATCH GRANULARITY**: ONE Worker per Feature×Platform combination — NO EXCEPTIONS.
+
+**HOW TO DISPATCH**: When executing Phase 5 dispatch blocks (action="dispatch-to-worker"):
+1. Build Feature×Platform matrix from DESIGN-OVERVIEW.md Platform Design Index
+2. Create `.tasks-temp.json` with one entry per Feature×Platform combination
+3. Initialize DISPATCH-PROGRESS.json via `update-progress.js init`
+4. Compute batch plan (batch size = 6)
+5. For each batch:
+   a. Use **Agent tool** to create `speccrew-task-worker` agents for ALL tasks in the batch **SIMULTANEOUSLY**
+   b. Each Worker receives: `skill_path` (platform-specific skill), `task_id`, `feature_id`, `feature_name`, `platform_id`, `feature_spec_path`, `api_contract_path`, `techs_knowledge_paths`, `framework_decisions`, `output_base_path`
+   c. **Wait** for ALL Workers in the batch to complete
+   d. Update DISPATCH-PROGRESS.json for each completed Worker
+   e. Log batch progress
+6. After all batches complete, read final progress summary
+
+**CRITICAL**: Each Worker handles exactly ONE feature on ONE platform. DO NOT group multiple features or platforms into a single Worker.
+
+**Example** (5 features × 3 platforms = 15 workers, 3 batches of 6/6/3):
+- Batch 1: Workers 1-6 (parallel)
+- Batch 2: Workers 7-12 (parallel, after batch 1 completes)
+- Batch 3: Workers 13-15 (parallel, after batch 2 completes)
+
 ### HARD STOP Checkpoints
 
 This workflow has **mandatory HARD STOP** checkpoints at:
@@ -147,3 +171,5 @@ DO NOT proceed past these checkpoints without explicit user confirmation.
 - **DO NOT skip reading workflow.agentflow.xml** — XML is the execution authority
 - **DO NOT generate DESIGN-OVERVIEW.md yourself** — Dispatch speccrew-task-worker with speccrew-sd-design-overview-generate skill
 - **DO NOT use Skill tool for Phase 4 design overview generation** — Skill tool executes inline, Agent tool creates a worker
+- **DO NOT group multiple features into a single Worker** — Each Worker handles exactly ONE feature on ONE platform
+- **DO NOT dispatch Workers sequentially** — ALL Workers in the same batch MUST be dispatched simultaneously

package/.speccrew/skills/speccrew-system-designer-orchestration/workflow.agentflow.xml

@@ -341,25 +341,91 @@
         </block>
       </branch>
       <branch default="true" name="Multi Feature/Platform - Worker Dispatch Required">
-        <!-- Parallel Worker Dispatch -->
-        <block type="rule" id="P5-R2" level="mandatory" desc="Parallel dispatch rule">
-          <field name="text">Dispatch ALL platform workers IN PARALLEL — DO NOT execute sequentially</field>
-          <field name="text">Each Worker runs independently — dispatch all at once, then monitor completion</field>
+        <!-- Parallel Worker Dispatch with Batch Loop -->
+        <block type="rule" id="P5-R2" level="mandatory" desc="Feature×Platform dispatch rules">
+          <field name="text">ONE Worker per Feature×Platform combination — NO EXCEPTIONS</field>
+          <field name="text">DO NOT group multiple features or platforms into a single Worker</field>
+          <field name="text">ALL Workers in the same batch MUST be dispatched IN PARALLEL — sequential dispatch is FORBIDDEN</field>
+          <field name="text">ALL Worker dispatch calls MUST be issued SIMULTANEOUSLY in a SINGLE orchestration turn</field>
+          <field name="text">DO NOT wait for any Worker to complete before dispatching the next Worker in the same batch</field>
+          <field name="text">Batch size is 6 — DO NOT exceed</field>
+          <field name="text">Each Worker MUST receive a single feature_spec_path and single platform_id — NOT arrays</field>
         </block>
-        <block type="task" id="P5-B4" action="dispatch-to-worker" status="pending"
-               desc="Dispatch workers for Feature×Platform matrix">
-          <field name="worker">speccrew-task-worker</field>
-          <field name="max_concurrent">6</field>
-          <field name="tasks">${dispatch_tasks_matrix}</field>
-          <field name="note">Each worker receives: skill_path, task_id, feature_id, feature_name, platform_id, feature_spec_path, api_contract_path, techs_knowledge_paths, framework_decisions, output_base_path</field>
+
+        <!-- Compute batch plan from dispatch_tasks_matrix -->
+        <block type="task" id="P5-B4-BATCH" action="compute-batches" status="pending"
+               desc="Calculate batch plan from Feature×Platform matrix">
+          <field name="items" value="${dispatch_tasks_matrix}"/>
+          <field name="batch_size" value="6"/>
+          <field name="output" var="batch_plan"/>
+        </block>
+
+        <!-- Batch Loop: Process all Feature×Platform tasks in batches of 6 -->
+        <block type="loop" id="P5-L-MAIN" over="${batch_plan.batches}" as="batch"
+               desc="Process batches sequentially — wait for each batch to complete before next">
+
+          <!-- Parallel dispatch for each task in current batch -->
+          <block type="loop" id="P5-L-INNER" over="${batch.tasks}" as="task" parallel="true" max-concurrency="6"
+                 desc="Dispatch Worker for each Feature×Platform combination IN PARALLEL">
+
+            <!-- Update task status to in_progress -->
+            <block type="task" id="P5-B4-PRE" action="run-script" status="pending"
+                   desc="Update task status to in_progress before dispatch">
+              <field name="command">node "${update_progress_script}" update-task --file "${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json" --task-id "${task.id}" --status in_progress</field>
+            </block>
+
+            <!-- Dispatch single Worker for ONE Feature × ONE Platform -->
+            <block type="task" id="P5-B4-DISPATCH" action="dispatch-to-worker" status="pending"
+                   desc="Dispatch Worker: ${task.feature_id} on ${task.platform_id}">
+              <field name="agent">speccrew-task-worker</field>
+              <field name="skill">${task.skill}</field>
+              <field name="skill_path">${ide_skills_dir}/${task.skill}/SKILL.md</field>
+              <field name="context">
+                task_id: ${task.id},
+                feature_id: ${task.feature_id},
+                feature_name: ${task.feature_name},
+                platform_id: ${task.platform_id},
+                feature_spec_path: ${task.feature_spec_path},
+                api_contract_path: ${task.api_contract_path},
+                techs_knowledge_paths: ${task.techs_knowledge_paths},
+                framework_decisions: ${framework_result.decisions},
+                output_base_path: ${iterations_dir}/${current_iteration}/03.system-design
+              </field>
+              <field name="output" var="worker_result_${task.id}"/>
+            </block>
+
+            <!-- Update progress after worker completes -->
+            <block type="task" id="P5-B4-POST" action="run-script" status="pending"
+                   desc="Update task progress after worker completes">
+              <field name="command">node "${update_progress_script}" update-task --file "${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json" --task-id "${task.id}" --status ${worker_result_${task.id}.status}</field>
+            </block>
+
+          </block>
+
+          <!-- Log batch completion -->
+          <block type="task" id="P5-B4-BATCH-READ" action="run-script" status="pending"
+                 desc="Read current progress after batch">
+            <field name="command">node "${update_progress_script}" read --file "${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json" --summary</field>
+            <field name="output" var="batch_progress"/>
+          </block>
+
+          <block type="event" id="P5-E-BATCH-END" action="log" level="info"
+                 desc="Log batch completion">
+            <field name="message">✅ Batch ${batch.index} Complete
+├── Progress: ${batch_progress.counts.completed}/${dispatch_tasks_matrix.length} completed
+├── Failed: ${batch_progress.counts.failed}
+└── Remaining: ${batch_progress.counts.pending}</field>
+          </block>
+
         </block>
       </branch>
     </block>
 
-    <!-- Step 5.5: Update DISPATCH-PROGRESS.json after completion -->
+    <!-- Step 5.5: Read final dispatch progress -->
     <block type="task" id="P5-B5" action="run-script" status="pending"
-           desc="Update task status based on completion">
-      <field name="command">node ${update_progress_script} update-task --file ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json --task-id ${task_id} --status ${completion_status} --output "${output_path}"</field>
+           desc="Read final dispatch progress summary">
+      <field name="command">node "${update_progress_script}" read --file "${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json" --summary</field>
+      <field name="output" var="final_dispatch_progress"/>
     </block>
 
     <!-- Step 5.6: Error Handling -->

package/package.json

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