speccrew 0.6.39 → 0.6.41

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

@@ -190,8 +190,9 @@ 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="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
               <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+              <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
             </block>
           </branch>
           <branch test="${bizs_kb.exists} == false" name="Bizs Not Initialized">
@@ -199,8 +200,9 @@ 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="run-skill" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
               <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+              <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
             </block>
           </branch>
           <branch default="true" name="Knowledge Base Ready">
@@ -221,6 +223,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">dispatch skills (bizs-dispatch-xml, techs-dispatch-xml) MUST be called directly by Leader via Skill tool as orchestration playbooks. Downstream worker skills (identify-entries, init-features, ui-analyze, etc.) MUST be dispatched via Task tool → speccrew-task-worker.</field>
     </block>
 
     <block type="gateway" id="P1-G1" mode="exclusive" desc="Intent Recognition Routing">
@@ -240,8 +243,9 @@ 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="run-skill" status="pending" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
           <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+          <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
         </block>
       </branch>
       <branch test="${intent} == 'knowledge_techs'" name="Techs Knowledge Base">
@@ -249,8 +253,9 @@ 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="run-skill" status="pending" desc="Leader directly invokes techs-dispatch as orchestration playbook">
           <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+          <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
         </block>
       </branch>
 

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

@@ -8,6 +8,31 @@ 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 is an **orchestration playbook** — it MUST be loaded directly by Team Leader via Skill tool (NOT via Worker Agent).
+
+```
+Correct: Leader uses Skill tool to load this playbook directly
+Incorrect: Dispatch this skill to speccrew-task-worker
+```
+
+**Why?** This skill defines the orchestration workflow and prepares task plans for downstream workers. The Team Leader reads this playbook and dispatches individual worker tasks via Task tool → speccrew-task-worker for each stage.
+
+**Correct Invocation Pattern**:
+```xml
+<block type="task" action="run-skill" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
+  <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
+  <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
+</block>
+```
+
+**Worker Dispatch Rule**:
+- Dispatch skills (bizs-dispatch-xml, techs-dispatch-xml): Leader calls directly via Skill tool
+- Downstream worker skills (identify-entries, init-features, ui-analyze, module-summarize, etc.): Leader dispatches via Task tool → speccrew-task-worker
+
+**FORBIDDEN**: Worker Agents MUST NOT execute this dispatch skill. If a Worker Agent loads this skill, it must report error and abort.
+
 ## Quick Reference — Execution Flow
 
 ```
@@ -94,6 +119,15 @@ Stage 4: System Summary
     <field name="completed_dir" required="true" type="string" desc="Marker file output directory for Worker results (absolute path required)"/>
   </block>
 
+  <!-- ============================================================
+       Global Invocation Rules
+       ============================================================ -->
+  <block type="rule" id="GLOBAL-R-INVOCATION" level="forbidden" desc="Invocation constraints — NEVER violate">
+    <field name="text">This skill is an ORCHESTRATION PLAYBOOK — it MUST be loaded directly by Team Leader via Skill tool</field>
+    <field name="text">Worker Agents MUST NOT execute this dispatch skill — if loaded by a Worker, report error and abort</field>
+    <field name="text">Downstream worker skills (identify-entries, init-features, ui-analyze, module-summarize, etc.) MUST be dispatched via Task tool → speccrew-task-worker</field>
+  </block>
+
   <!-- ============================================================
        Global Continuous Execution Rules
        ============================================================ -->

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

@@ -8,6 +8,31 @@ 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 is an **orchestration playbook** — it MUST be loaded directly by Team Leader via Skill tool (NOT via Worker Agent).
+
+```
+Correct: Leader uses Skill tool to load this playbook directly
+Incorrect: Dispatch this skill to speccrew-task-worker
+```
+
+**Why?** This skill defines the orchestration workflow and prepares task plans for downstream workers. The Team Leader reads this playbook and dispatches individual worker tasks via Task tool → speccrew-task-worker for each stage.
+
+**Correct Invocation Pattern**:
+```xml
+<block type="task" action="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
+  <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
+  <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
+</block>
+```
+
+**Worker Dispatch Rule**:
+- Dispatch skills (bizs-dispatch-xml, techs-dispatch-xml): Leader calls directly via Skill tool
+- Downstream worker skills (techs-init, techs-generate-conventions, techs-generate-ui-style, etc.): Leader dispatches via Task tool → speccrew-task-worker
+
+**FORBIDDEN**: Worker Agents MUST NOT execute this dispatch skill. If a Worker Agent loads this skill, it must report error and abort.
+
 ## Quick Reference — Execution Flow
 
 ```
@@ -107,6 +132,15 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
     <field name="ide_skills_dir" required="true" type="string" desc="Absolute path to IDE skills directory (e.g., .qoder/skills, .cursor/skills)"/>
   </block>
 
+  <!-- ============================================================
+       Global Invocation Rules
+       ============================================================ -->
+  <block type="rule" id="GLOBAL-R-INVOCATION" level="forbidden" desc="Invocation constraints — NEVER violate">
+    <field name="text">This skill is an ORCHESTRATION PLAYBOOK — it MUST be loaded directly by Team Leader via Skill tool</field>
+    <field name="text">Worker Agents MUST NOT execute this dispatch skill — if loaded by a Worker, report error and abort</field>
+    <field name="text">Downstream worker skills (techs-init, techs-generate-conventions, techs-generate-ui-style, etc.) MUST be dispatched via Task tool → speccrew-task-worker</field>
+  </block>
+
   <!-- ============================================================
        Global Continuous Execution Rules
        ============================================================ -->

package/package.json

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