speccrew 0.6.57 → 0.6.61

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-identify-entries-xml/SKILL.md

@@ -152,6 +152,19 @@ For each platform, generates:
         <field name="output" var="generated_json_path"/>
       </block>
 
+      <!-- Rule: Output JSON Format Validation -->
+      <block type="rule" id="R-FORMAT" scope="mandatory" desc="Output JSON format validation">
+        <field name="content">
+          The generated entry-dirs JSON file MUST strictly follow this structure:
+          - Root object MUST contain "modules" field (array type)
+          - Root object MUST NOT contain "businessModules", "subModules", or "components" fields
+          - Each module in "modules" array MUST have exactly two fields: "name" (string) and "entryDirs" (array of strings)
+          - For platforms with hierarchical directory structure (e.g. frontend views/system/user/), flatten into individual modules
+          - Module names should use hyphen-separated composite names for sub-modules (e.g. "system-user", "system-role")
+          - If the generated JSON does not match this format, you MUST regenerate it before proceeding
+        </field>
+      </block>
+
       <!-- Checkpoint: Persist Generated JSON -->
       <block type="checkpoint" id="CP1" name="entry-dirs-generated" desc="Verify entry-dirs JSON was generated">
         <field name="file" value="${sync_state_bizs_dir}/entry-dirs-${platform.platformId}.json"/>
@@ -227,6 +240,14 @@ For each platform, generates:
 }
 ```
 
+### Format Constraints
+
+- **MUST use `modules` array** — never use `businessModules`, `components`, or any alternative field name
+- **MUST flatten hierarchy** — if a platform has sub-modules (e.g. frontend `system/user`, `system/role`), each sub-module must be a separate top-level module entry in the `modules` array
+  - 例如：`system` 有 `user` 和 `role` 子目录 → 生成 `{ "name": "system-user", "entryDirs": ["src/views/system/user"] }` 和 `{ "name": "system-role", "entryDirs": ["src/views/system/role"] }`
+- **Forbidden fields**: `businessModules`, `subModules`, `components`, `hasSubModules` — 这些都不被下游脚本支持
+- **Each module's entryDirs** must point to directories containing actual entry files (e.g. .vue, .py, .java), not parent wrapper directories
+
 ### Field Definitions
 
 - `platformId`: Platform identifier (e.g., `backend-ai`, `web-vue`, `mobile-uniapp`)

package/.speccrew/skills/speccrew-knowledge-bizs-init-features/scripts/generate-inventory.js

@@ -647,8 +647,24 @@ function main() {
       console.error('Error: entryDirsFile missing required field "sourcePath"');
       process.exit(1);
     }
+    // Check for common format mistakes
+    if (entryDirsData.businessModules && Array.isArray(entryDirsData.businessModules)) {
+      console.error('Error: entryDirsFile uses unsupported "businessModules" format.');
+      console.error('Expected: { "modules": [ { "name": "...", "entryDirs": ["..."] } ] }');
+      console.error('Received: { "businessModules": [...] }');
+      console.error('');
+      console.error('Fix: The entry-dirs JSON must use a flat "modules" array.');
+      console.error('Each module should have "name" (string) and "entryDirs" (array of strings).');
+      console.error('Sub-modules must be flattened into top-level entries.');
+      console.error('Re-run the identify-entries skill to regenerate with correct format.');
+      process.exit(1);
+    }
+
     if (!entryDirsData.modules || !Array.isArray(entryDirsData.modules)) {
-      console.error('Error: entryDirsFile missing required field "modules" array');
+      console.error('Error: entryDirsFile missing required field "modules" array.');
+      console.error('Expected format: { "platformId": "...", "modules": [ { "name": "...", "entryDirs": ["..."] } ] }');
+      const foundKeys = Object.keys(entryDirsData).join(', ');
+      console.error(`Found top-level keys: ${foundKeys}`);
       process.exit(1);
     }
     

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.61",
   "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.