speccrew 0.6.38 → 0.6.40

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

@@ -190,8 +190,16 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
             <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">
+            <block type="task" id="P05-B5" action="dispatch-to-worker" desc="Dispatch techs-dispatch via Task tool → speccrew-task-worker">
+              <field name="worker">speccrew-task-worker</field>
               <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+              <field name="instructions">
+CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
+
+Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-techs-dispatch-xml.
+The Worker Agent will load and execute the dispatch workflow autonomously.
+DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
+              </field>
             </block>
           </branch>
           <branch test="${bizs_kb.exists} == false" name="Bizs Not Initialized">
@@ -199,8 +207,16 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
             <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">
+            <block type="task" id="P05-B6" action="dispatch-to-worker" desc="Dispatch bizs-dispatch via Task tool → speccrew-task-worker">
+              <field name="worker">speccrew-task-worker</field>
               <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+              <field name="instructions">
+CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
+
+Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-bizs-dispatch-xml.
+The Worker Agent will load and execute the dispatch workflow autonomously.
+DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
+              </field>
             </block>
           </branch>
           <branch default="true" name="Knowledge Base Ready">
@@ -221,6 +237,7 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
       <field name="text">DO NOT trigger business process Skills (PRD, Solution, Design, Dev) — these are loaded by corresponding role Agents</field>
       <field name="text">DO NOT handle business development requests (feature requirements, code modifications, bug fixes) — prompt user to talk directly to Qoder</field>
       <field name="text">DO NOT delete or modify WORKFLOW-PROGRESS.json (read-only)</field>
+      <field name="text">DO NOT call the Skill tool directly for speccrew-knowledge-* skills (speccrew-knowledge-bizs-dispatch-xml, speccrew-knowledge-techs-dispatch-xml) — MUST use Task tool to create speccrew-task-worker Agent for indirect execution</field>
     </block>
 
     <block type="gateway" id="P1-G1" mode="exclusive" desc="Intent Recognition Routing">
@@ -240,8 +257,16 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
           <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">
+        <block type="task" id="P1-B3" action="dispatch-to-worker" status="pending" desc="Dispatch bizs-dispatch via Task tool → speccrew-task-worker">
+          <field name="worker">speccrew-task-worker</field>
           <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+          <field name="instructions">
+CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
+
+Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-bizs-dispatch-xml.
+The Worker Agent will load and execute the dispatch workflow autonomously.
+DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
+          </field>
         </block>
       </branch>
       <branch test="${intent} == 'knowledge_techs'" name="Techs Knowledge Base">
@@ -249,8 +274,16 @@ rule       : Constraint declaration (level: forbidden | mandatory | note)
           <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">
+        <block type="task" id="P1-B4" action="dispatch-to-worker" status="pending" desc="Dispatch techs-dispatch via Task tool → speccrew-task-worker">
+          <field name="worker">speccrew-task-worker</field>
           <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+          <field name="instructions">
+CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
+
+Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-techs-dispatch-xml.
+The Worker Agent will load and execute the dispatch workflow autonomously.
+DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
+          </field>
         </block>
       </branch>
 
@@ -400,6 +433,13 @@ When user reports problems ("something went wrong", "error occurred", "not worki
 - 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`
 
+**CONTINUOUS EXECUTION ENFORCEMENT:**
+- NEVER offer A/B/C choices during pipeline execution
+- NEVER pause to ask "Should I continue?" when workload is large
+- NEVER suggest "partial execution" or "on-demand initialization" as options
+- When context window is running low, complete current stage fully, write checkpoint, then continue in next context — DO NOT ask user
+- The ONLY acceptable reason to stop is: unrecoverable error (file system failure, missing dependencies)
+
 **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

@@ -8,6 +8,26 @@ tools: Read, Write, Task, Bash
 
 Orchestrate **bizs knowledge base generation** with a 5-stage pipeline using **XML Block system**: Feature Inventory → Feature Analysis + Graph Write → Module Summarize → UI Style Pattern Extract → System Summary.
 
+## Invocation Method
+
+**CRITICAL**: This skill MUST be invoked via Task tool → speccrew-task-worker, NOT via direct Skill tool call.
+
+```
+Correct: Use Task tool to create speccrew-task-worker with this skill
+Incorrect: Use Skill tool to call this skill directly
+```
+
+**Why?** This skill requires run_in_terminal capability for script execution, which Worker Agents possess but direct Skill invocations may not support correctly. The Task tool creates a dedicated Worker Agent (speccrew-task-worker) that loads and executes this workflow autonomously.
+
+**Correct Invocation Pattern**:
+```xml
+<block type="task" action="dispatch-to-worker" desc="Dispatch bizs-dispatch via Task tool">
+  <field name="worker">speccrew-task-worker</field>
+  <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+  <field name="instructions">Execute the bizs knowledge base generation pipeline.</field>
+</block>
+```
+
 ## Quick Reference — Execution Flow
 
 ```
@@ -105,6 +125,10 @@ Stage 4: System Summary
     <field name="text">DO NOT ask for confirmation before generating output files</field>
     <field name="text">DO NOT warn about "large number of files" or "this may take a while" — proceed with generation</field>
     <field name="text">ONLY pause at explicit &lt;event action="confirm"&gt; blocks defined in the workflow</field>
+    <field name="text">DO NOT offer "continue/pause/partial" options — EVER</field>
+    <field name="text">DO NOT estimate workload and suggest breaking it into phases — execute ALL phases in sequence</field>
+    <field name="text">When many features need analysis, dispatch ALL of them — do NOT skip or defer any</field>
+    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume — do NOT ask user for guidance</field>
   </block>
 
   <!-- ============================================================

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

@@ -8,6 +8,26 @@ tools: Read, Write, Task, Bash
 
 Orchestrate **techs knowledge base generation** with a 3-stage pipeline using **XML Block system**: Platform Detection → Tech Doc Generation → Root Index.
 
+## Invocation Method
+
+**CRITICAL**: This skill MUST be invoked via Task tool → speccrew-task-worker, NOT via direct Skill tool call.
+
+```
+Correct: Use Task tool to create speccrew-task-worker with this skill
+Incorrect: Use Skill tool to call this skill directly
+```
+
+**Why?** This skill requires run_in_terminal capability for script execution, which Worker Agents possess but direct Skill invocations may not support correctly. The Task tool creates a dedicated Worker Agent (speccrew-task-worker) that loads and executes this workflow autonomously.
+
+**Correct Invocation Pattern**:
+```xml
+<block type="task" action="dispatch-to-worker" desc="Dispatch techs-dispatch via Task tool">
+  <field name="worker">speccrew-task-worker</field>
+  <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+  <field name="instructions">Execute the techs knowledge base generation pipeline.</field>
+</block>
+```
+
 ## Quick Reference — Execution Flow
 
 ```
@@ -118,6 +138,10 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
     <field name="text">DO NOT ask for confirmation before generating output files</field>
     <field name="text">DO NOT warn about "large number of files" or "this may take a while" — proceed with generation</field>
     <field name="text">ONLY pause at explicit &lt;event action="confirm"&gt; blocks defined in the workflow</field>
+    <field name="text">DO NOT offer "continue/pause/partial" options — EVER</field>
+    <field name="text">DO NOT estimate workload and suggest breaking it into phases — execute ALL phases in sequence</field>
+    <field name="text">When many platforms need analysis, dispatch ALL of them — do NOT skip or defer any</field>
+    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume — do NOT ask user for guidance</field>
   </block>
 
   <!-- ============================================================

package/package.json

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