speccrew 0.6.32 → 0.6.34

package/.speccrew/agents/speccrew-task-worker.md

@@ -164,6 +164,14 @@ When the task fails or is blocked, output:
 
 ## Constraints
 
+**TECHNOLOGY STACK CONSTRAINTS:**
+- Scripting languages ONLY: PowerShell (Windows) and Bash (Linux/Mac)
+- Node.js permitted ONLY for existing project scripts (e.g., `node scripts/xxx.js`)
+- FORBIDDEN: Python, Ruby, Perl, compiled languages, or any runtime requiring separate installation
+- DO NOT create temporary .py, .rb, .pl files under any circumstances
+- For JSON validation, use `node -e "JSON.parse(require('fs').readFileSync('file.json','utf8'))"` instead of Python
+- For file processing, use PowerShell cmdlets (Get-Content, ConvertFrom-Json, Set-Content) or Bash built-ins
+
 **MUST DO:**
 - If `skill_name` is provided, MUST use Skill Discovery to resolve the full path and strictly follow the Skill definition
 - If `skill_name` is provided but Skill file does not exist, immediately report error

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

@@ -187,12 +187,18 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
         <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>
             <block type="task" id="P05-B5" action="run-skill" desc="Invoke techs-dispatch">
               <field name="skill">speccrew-knowledge-techs-dispatch</field>
             </block>
           </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>
             <block type="task" id="P05-B6" action="run-skill" desc="Invoke bizs-dispatch-xml">
               <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
             </block>
@@ -230,11 +236,19 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
         </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>
         <block type="task" id="P1-B3" action="run-skill" status="pending" desc="Invoke bizs-dispatch XML version">
           <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
         </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>
         <block type="task" id="P1-B4" action="run-skill" status="pending" desc="Invoke techs-dispatch Skill">
           <field name="skill">speccrew-knowledge-techs-dispatch</field>
         </block>
@@ -379,6 +393,13 @@ When user reports problems ("something went wrong", "error occurred", "not worki
 - Display pipeline status visually when WORKFLOW-PROGRESS.json exists
 - Support both auto-orchestration mode (when user requests "auto") and manual mode
 
+**Technology Stack Constraints:**
+- Scripting: PowerShell and Bash only (zero Python dependency, zero external tools)
+- Node.js: Permitted ONLY for existing project scripts (e.g., speccrew CLI, update-progress.js)
+- FORBIDDEN: Python, Ruby, Perl, compiled languages, or any runtime not pre-installed
+- When dispatching workers: ensure task descriptions explicitly state "use PowerShell/Bash only"
+- For JSON operations: use `node -e` with inline JS, or PowerShell `ConvertFrom-Json` / `ConvertTo-Json`
+
 **Must NOT Do:**
 - Do not directly execute specific steps in Skill (must read Skill file first)
 - Do not skip Skill and directly generate deliverables

package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md

@@ -107,6 +107,18 @@ Stage 4: System Summary
     <field name="text">ONLY pause at explicit &lt;event action="confirm"&gt; blocks defined in the workflow</field>
   </block>
 
+  <!-- ============================================================
+       Global Technology Stack Constraints
+       ============================================================ -->
+  <block type="rule" id="GLOBAL-R-TECHSTACK" level="forbidden" desc="Technology stack constraints — NEVER violate">
+    <field name="text">FORBIDDEN: Python, Ruby, Perl, compiled binaries, or any runtime requiring separate installation</field>
+    <field name="text">PERMITTED scripting: PowerShell (Windows) and Bash (Linux/Mac) ONLY</field>
+    <field name="text">PERMITTED Node.js: ONLY for existing project scripts (e.g., node scripts/update-progress.js)</field>
+    <field name="text">For JSON validation use: node -e "JSON.parse(require('fs').readFileSync('file.json','utf8'))"</field>
+    <field name="text">For JSON creation use: node -e with inline script, or PowerShell ConvertTo-Json</field>
+    <field name="text">DO NOT create temporary .py, .rb, .pl, .bat files — use inline commands via run_in_terminal</field>
+  </block>
+
   <!-- ============================================================
        Stage 0: Platform Detection
        ============================================================ -->
@@ -461,7 +473,7 @@ Preparing Graph data generation for completed Features
           </block>
 
           <!-- Step 2.5: Dispatch Graph Worker -->
-          <block type="loop" id="S2-L25" over="${batch_response.batch}" as="feature" desc="Dispatch Graph Worker for each Feature">
+          <block type="loop" id="S2-L25" over="${batch_response.batch}" as="feature" parallel="true" max-concurrency="${max_concurrent_workers}" desc="Dispatch Graph Worker for each Feature IN PARALLEL">
             <block type="gateway" id="S2-G2" mode="exclusive" desc="Route Graph Worker based on analysis type">
               <branch test="${feature.platformType} == 'backend'" name="API Graph">
                 <block type="task" id="S2-B25a" action="dispatch-to-worker" status="pending" desc="Dispatch API Graph Worker">
@@ -625,11 +637,12 @@ Stage 3 Milestone: Module summaries complete. ${module_count} modules summarized
     
     <block type="rule" id="S35-R1" level="mandatory" desc="Stage 3.5 mandatory rules">
       <field name="text">Worker dispatch is handled by the calling Agent (Team Leader). This Skill only prepares the task plan and parameters.</field>
+      <field name="text">ALL UI style extraction workers MUST be dispatched IN PARALLEL — sequential execution is FORBIDDEN</field>
       <field name="text">This stage writes to techs knowledge base, not bizs knowledge base</field>
     </block>
 
     <!-- Dispatch UI Style Extract Worker for each frontend platform -->
-    <block type="loop" id="S35-L1" over="${platforms}" as="platform" desc="Prepare UI style extraction tasks for frontend platforms">
+    <block type="loop" id="S35-L1" over="${platforms}" as="platform" parallel="true" max-concurrency="${max_concurrent_workers}" desc="Dispatch UI style extraction Workers for frontend platforms IN PARALLEL">
       <block type="gateway" id="S35-G1" mode="exclusive" desc="Execute for UI platforms only">
         <branch test="${platform.platformType} in ['web', 'mobile', 'desktop']" name="UI platform">
           <block type="task" id="S35-B1" action="dispatch-to-worker" status="pending" desc="Dispatch UI style extraction Worker">

package/.speccrew/skills/speccrew-knowledge-techs-dispatch/SKILL.md

@@ -124,6 +124,12 @@ See [Platform Status Tracking Fields](#platform-status-tracking-fields) for stat
 
 ## Stage 2: Generate Platform Documents (Parallel)
 
+> **🚨 CRITICAL: PARALLEL EXECUTION IS MANDATORY**
+> - Prepare task plans for ALL platforms FIRST, then dispatch ALL workers SIMULTANEOUSLY
+> - DO NOT finish one platform before starting the next — this wastes time and violates the pipeline design
+> - The calling Agent MUST use concurrent task dispatch (e.g., dispatch 3 workers in one turn for 3 platforms)
+> - Sequential platform-by-platform execution is FORBIDDEN
+
 **Goal**: Generate technology documentation for each platform in parallel.
 
 **Action**:

package/package.json

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