speccrew 0.6.52 → 0.6.54

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

@@ -77,7 +77,15 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
 >
-> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. Every `<block type="task">` is a literal tool-call instruction — use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. Do NOT interpret the workflow as a goal description or improvise your own approach.
+> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. For EVERY block, you MUST announce it before execution:
+>
+> ```
+> 📋 Block [ID] (action=[action]) — [desc]
+> 🔧 Tool: [which IDE tool to call]
+> ✅ Result: [output or status]
+> ```
+>
+> Use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. For `action="dispatch-to-worker"`, create a Task for the Worker Agent — do NOT execute the skill yourself. Do NOT interpret the workflow as a goal description or improvise your own approach.
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>

package/.speccrew/skills/speccrew-knowledge-bizs-api-analyze-xml/SKILL.md

@@ -385,6 +385,34 @@ Before executing the workflow, verify the following inputs:
     <field name="message" value="Step 5a Status: COMPLETED - Template copied to ${documentPath}, ready for section filling"/>
   </block>
   
+  <!-- ==================== STEP 5-DYNAMIC: DYNAMIC SECTION GENERATION ==================== -->
+  <!-- Dynamic Section Generation Rule -->
+  <block type="rule" id="R-DYNAMIC-SECTIONS" level="mandatory" desc="Dynamic section generation rule">
+    <field name="text">BEFORE filling template sections, you MUST first count identified items (endpoints, components, etc.) and dynamically create the corresponding number of sections in the document.</field>
+    <field name="text">Step 1: Copy template skeleton to target path</field>
+    <field name="text">Step 2: For each identified endpoint/component, insert a new numbered sub-section (e.g., 2.1, 2.2, 2.3...) into the document</field>
+    <field name="text">Step 3: Fill each sub-section with the specific endpoint/component details</field>
+    <field name="text">NEVER rely on fixed template sections alone — the number of sections MUST match the number of identified items</field>
+  </block>
+  
+  <!-- Dynamically Generate Endpoint Sections -->
+  <block type="loop" id="L-ENDPOINT-SECTIONS" over="${endpoints}" as="endpoint" desc="Dynamically generate a section for each API endpoint">
+    <block type="task" id="B-EP-SECTION" action="generate" desc="Insert endpoint sub-section into document">
+      <field name="target" value="${documentPath}"/>
+      <field name="content">For endpoint ${endpoint.method} ${endpoint.path}: insert a ## 2.X sub-section containing Endpoint Information table, Request Parameters, Response Data, Business Flow, and Error Codes</field>
+      <field name="output" var="section_${endpoint.index}"/>
+    </block>
+  </block>
+  
+  <!-- Verify Section Count Matches Endpoint Count -->
+  <block type="checkpoint" id="CP-SECTIONS-COUNT" desc="Verify section count matches endpoint count">
+    <field name="verify" value="Number of generated 2.X sections == ${endpoints.length}"/>
+  </block>
+  
+  <block type="event" id="E-DYNAMIC" action="log" level="info" desc="Log dynamic sections status">
+    <field name="message" value="Step 5-Dynamic Status: COMPLETED - Generated ${endpoints.length} endpoint sections dynamically"/>
+  </block>
+  
   <!-- ==================== STEP 5B: FILL EACH SECTION USING SEARCH_REPLACE ==================== -->
   <!-- Calculate Dynamic Path Prefix -->
   <block type="task" id="B17" action="calculate-path-prefix" desc="Calculate path prefix">

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

@@ -8,15 +8,28 @@ tools: Read, Write, Task, Bash
 >
 > **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md` — this defines all block types and action-to-tool mappings
 >
-> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**:
-> - `action="run-script"` → Execute via **Terminal tool** (PowerShell/Bash)
-> - `action="run-skill"` → Invoke via **Skill tool** (do NOT manually read SKILL.md files or browse directories)
-> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker`
+> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
+>
+> ```
+> 📋 Block [ID] (action=[action]) — [desc]
+> 🔧 Tool: [which IDE tool to call]
+> ✅ Result: [output or status]
+> ```
+>
+> Action-to-tool mapping:
+> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
+> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
+> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker` (Worker loads and executes the skill, NOT you)
 > - `action="confirm"` (event) → Present to user and wait for response
 >
 > **Step 3**: Execute ALL stages sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
 >
-> **FORBIDDEN**: Do NOT run terminal commands as substitute for Skill tool calls. Do NOT do Worker's job yourself. Do NOT skip blocks or improvise.
+> **FORBIDDEN**:
+> - Do NOT skip the block announcement format above — every block must be announced before execution
+> - Do NOT run terminal commands as substitute for Skill tool calls
+> - Do NOT do Worker's job yourself — when `action="dispatch-to-worker"`, create a Task and let Worker handle it
+> - Do NOT skip blocks or improvise your own commands
+> - Do NOT read a skill's SKILL.md file yourself — use the Skill tool which resolves paths automatically
 
 # Bizs Knowledge Dispatch (XML Block Version)
 

package/.speccrew/skills/speccrew-knowledge-bizs-ui-analyze-xml/SKILL.md

@@ -306,7 +306,31 @@ Analyze one specific UI feature from source code, extract business functionality
       <field name="message">Step 5a Status: COMPLETED - Template copied to ${documentPath}</field>
     </block>
   </sequence>
-
+  
+  <!-- ==================== STEP 5-MID: DYNAMIC SECTION GENERATION ==================== -->
+  <!-- Rule: Dynamic section generation before filling fixed sections -->
+  <block type="rule" id="R-DYNAMIC-SECTIONS" level="mandatory" desc="Dynamic section generation rule">
+    <field name="text">BEFORE filling template sections, you MUST first count identified UI components and dynamically create the corresponding number of sections in the document.</field>
+    <field name="text">Step 1: Copy template skeleton to target path</field>
+    <field name="text">Step 2: For each identified UI component/area, insert a new numbered sub-section (e.g., 2.1, 2.2, 2.3...) into the document</field>
+    <field name="text">Step 3: Fill each sub-section with the specific component details (wireframe, interactions, events)</field>
+    <field name="text">NEVER rely on fixed template sections alone — the number of sections MUST match the number of identified UI components</field>
+  </block>
+  
+  <!-- Loop: Dynamically generate a section for each UI component -->
+  <block type="loop" id="L-COMPONENT-SECTIONS" over="${analysisResult.components}" as="component" desc="Dynamically generate a section for each UI component">
+    <block type="task" id="B-COMP-SECTION" action="generate" desc="Insert component sub-section into document">
+      <field name="target" value="${documentPath}"/>
+      <field name="content">For component ${component.name} (type: ${component.type}): insert a ## 2.X sub-section containing Component Wireframe, Props/Events table, Interaction Flow, and State Management</field>
+      <field name="output" var="section_${component.index}"/>
+    </block>
+  </block>
+  
+  <!-- Checkpoint: Verify section count matches component count -->
+  <block type="checkpoint" id="CP-SECTIONS-COUNT" desc="Verify section count matches component count">
+    <field name="verify">Number of generated 2.X sections == ${analysisResult.components.length}</field>
+  </block>
+  
   <!-- ==================== STEP 5B: FILL EACH SECTION USING SEARCH_REPLACE ==================== -->
   <sequence id="S5b" name="Step 5b: Fill Sections" status="pending" desc="Fill document sections">
     <!-- Section 1: Content Overview -->

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

@@ -8,15 +8,28 @@ tools: Read, Write, Task, Bash
 >
 > **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md` — this defines all block types and action-to-tool mappings
 >
-> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**:
-> - `action="run-script"` → Execute via **Terminal tool** (PowerShell/Bash)
-> - `action="run-skill"` → Invoke via **Skill tool** (do NOT manually read SKILL.md files or browse directories)
-> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker`
+> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
+>
+> ```
+> 📋 Block [ID] (action=[action]) — [desc]
+> 🔧 Tool: [which IDE tool to call]
+> ✅ Result: [output or status]
+> ```
+>
+> Action-to-tool mapping:
+> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
+> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
+> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker` (Worker loads and executes the skill, NOT you)
 > - `action="confirm"` (event) → Present to user and wait for response
 >
 > **Step 3**: Execute ALL stages sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
 >
-> **FORBIDDEN**: Do NOT run terminal commands as substitute for Skill tool calls. Do NOT do Worker's job yourself. Do NOT skip blocks or improvise.
+> **FORBIDDEN**:
+> - Do NOT skip the block announcement format above — every block must be announced before execution
+> - Do NOT run terminal commands as substitute for Skill tool calls
+> - Do NOT do Worker's job yourself — when `action="dispatch-to-worker"`, create a Task and let Worker handle it
+> - Do NOT skip blocks or improvise your own commands
+> - Do NOT read a skill's SKILL.md file yourself — use the Skill tool which resolves paths automatically
 
 # Techs Knowledge Dispatch (XML Block Version)
 

package/package.json

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