speccrew 0.6.57 → 0.6.59

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

@@ -353,6 +353,21 @@ Before executing the workflow, verify the following inputs:
   </block>
   
   <!-- ==================== STEP 5A: COPY TEMPLATE TO DOCUMENT PATH ==================== -->
+  <!-- Document Output Path Rule -->
+  <block type="rule" id="R-DOCPATH" level="mandatory" desc="Document output path MUST use documentPath parameter">
+    <field name="text">
+      The output document file MUST be created at the EXACT path specified by ${documentPath} input parameter.
+      DO NOT use the template file name (e.g., FEATURE-DETAIL-TEMPLATE-*.md) as the output file name.
+      The documentPath already contains the correct target path including file name (e.g., speccrew-workspace/knowledges/bizs/backend-system/admin/cache/cache_controller.md).
+      Before creating the file, ensure the parent directory exists (create if necessary).
+    </field>
+  </block>
+
+  <!-- Ensure Document Output Directory Exists -->
+  <block type="task" id="B14a" action="run-script" desc="Ensure document output directory exists">
+    <field name="command">node -e "require('fs').mkdirSync(require('path').dirname('${documentPath}'), {recursive: true})"</field>
+  </block>
+
   <!-- Replace Top-Level Placeholders -->
   <block type="task" id="B14" action="replace-placeholders" desc="Replace template placeholders">
     <field name="template" value="${templateContent}"/>

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

@@ -285,6 +285,21 @@ Analyze one specific UI feature from source code, extract business functionality
 
   <!-- ==================== STEP 5A: COPY TEMPLATE TO DOCUMENT PATH ==================== -->
   <sequence id="S5a" name="Step 5a: Copy Template" status="pending" desc="Copy template to document path">
+    <!-- Document Output Path Rule -->
+    <block type="rule" id="R-DOCPATH" level="mandatory" desc="Document output path MUST use documentPath parameter">
+      <field name="text">
+        The output document file MUST be created at the EXACT path specified by ${documentPath} input parameter.
+        DO NOT use the template file name (e.g., FEATURE-DETAIL-TEMPLATE-*.md) as the output file name.
+        The documentPath already contains the correct target path including file name (e.g., speccrew-workspace/knowledges/bizs/web-vue/src/views/system/user/index.md).
+        Before creating the file, ensure the parent directory exists (create if necessary).
+      </field>
+    </block>
+
+    <!-- Ensure Document Output Directory Exists -->
+    <block type="task" id="B5a0" action="run-script" desc="Ensure document output directory exists">
+      <field name="command">node -e "require('fs').mkdirSync(require('path').dirname('${documentPath}'), {recursive: true})"</field>
+    </block>
+
     <!-- Prepare Placeholder Replacements -->
     <block type="task" id="B5a1" action="analyze" desc="Prepare replacements">
       <field name="language" value="${language}"/>

package/package.json

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

package/workspace-template/docs/rules/xml-workflow-spec.md

@@ -481,3 +481,20 @@ Team Leader executes:
 6. **`loop parallel="true"`** = dispatch all iterations concurrently
 7. **`rule level="forbidden"`** = immediate stop if violated
 8. **Input/Output blocks** define the contract — respect required parameters
+
+### Block Execution Announcement Protocol
+
+Before executing each `<block>`, the agent MUST announce the block being executed. The announcement format is:
+
+```
+📋 Block [{block-id}] (type={block-type}, action={action}) — {block-desc}
+```
+
+**Rules:**
+1. The announcement MUST be made BEFORE the block execution begins, not after.
+2. ALL block types require announcement: `task`, `loop`, `checkpoint`, `rule`, `gateway`, `input`, `output`.
+3. For `<block type="loop">` blocks, announce the loop entry with iteration context (e.g., "Loop [S2-L2] — Iterating over ${batch}, 5 items, parallel=true").
+4. For `<block type="checkpoint">` blocks, announce the checkpoint and its validation result.
+5. For `<block type="rule">` blocks, announce the rule being applied.
+6. This protocol applies to ALL agents executing XML workflows — both orchestrating agents (Team Leader) and worker agents.
+7. Nested blocks inside loops should also be announced for each iteration.