speccrew 0.6.10 → 0.6.12

package/.speccrew/agents/speccrew-product-manager.md

@@ -93,33 +93,14 @@ Use Glob to search `{iterations_dir}/*/WORKFLOW-PROGRESS.json`
    - If `01_prd.status` is `confirmed`, check resume state (Step 0.2)
 3. **If WORKFLOW-PROGRESS.json does not exist**:
    - **MUST use script to initialize:**
+
+     > 🛑 **FORBIDDEN**: DO NOT manually create WORKFLOW-PROGRESS.json via Write/Edit tools. ALL initialization MUST be done via `update-progress.js` script.
+
      ```bash
      node "{update_progress_script}" update-workflow \
-       --file {iterations_dir}/{iteration}/WORKFLOW-PROGRESS.json \
+       --file "{iterations_dir}/{iteration_name}/WORKFLOW-PROGRESS.json" \
        --stage 01_prd --status in_progress
      ```
-   - **Fallback** (ONLY if script file does not exist):
-     Create manually with the following structure:
-     ```json
-     {
-       "iteration": "{iteration-name}",
-       "current_stage": "01_prd",
-       "stages": {
-         "01_prd": {
-           "status": "in_progress",
-           "started_at": "<current-timestamp>",
-           "completed_at": null,
-           "confirmed_at": null,
-           "outputs": []
-         },
-         "02_feature_design": { "status": "pending" },
-         "03_system_design": { "status": "pending" },
-         "04_development": { "status": "pending" },
-         "05_deployment": { "status": "pending" },
-         "06_system_test": { "status": "pending" }
-       }
-     }
-     ```
 
 ## Phase 0.2: Check Resume State (Checkpoint Recovery)
 
@@ -221,6 +202,7 @@ After IDE detection, compute and store all absolute paths as workflow context va
 
 | Variable | Derivation | Example |
 |----------|-----------|---------|
+| `source_path` | Project source root (from `.speccrewrc` config or user provided) | `d:/dev/litemes` |
 | `workspace_path` | Project root + `/speccrew-workspace` | `d:/dev/litemes/speccrew-workspace` |
 | `sync_state_bizs_dir` | `{workspace_path}/knowledges/base/sync-state/knowledge-bizs` | `d:/dev/litemes/speccrew-workspace/knowledges/base/sync-state/knowledge-bizs` |
 | `iterations_dir` | `{workspace_path}/iterations` | `d:/dev/litemes/speccrew-workspace/iterations` |
@@ -448,18 +430,31 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
    ```
 
    **Agent Tool Invocation for Path B Step 2 (Module Initializer)**:
+
+   > 🛑 **MANDATORY**: You MUST dispatch a separate Worker for EACH module in matched_modules. 
+   > Each Worker handles ONE module on ONE platform.
+
+   For each module in matched_modules:
    ```
    Use the Agent tool to invoke speccrew-task-worker:
    - agent: speccrew-task-worker
-   - task: Execute speccrew-pm-module-initializer skill
+   - task: Execute speccrew-pm-module-initializer skill for module "{module.module_name}" on platform "{module.platform_id}"
    - context:
        skill: speccrew-pm-module-initializer
+       source_path: {source_path}
+       module_name: {module.module_name}
+       platform_id: {module.platform_id}
+       platform_type: {module.platform_type}
+       features_file: {sync_state_bizs_dir}/features-{module.platform_id}.json
+       output_path: {workspace_path}/knowledges
+       completed_dir: {sync_state_bizs_dir}/completed
+       sourceFile: features-{module.platform_id}.json
+       language: {detected user language}
        workspace_path: {workspace_path}
-       matched_modules: <modules from matcher result>
-       sync_state_bizs_dir: {sync_state_bizs_dir}
-       ide_skills_dir: {ide_skills_dir}
    ```
 
+   Wait for ALL module-initializer Workers to complete before proceeding to Phase 2.
+
 4. **IF feature inventory fails**:
    - Report to user: "Project structure scan encountered issues: [specific error]. Continuing without knowledge base context."
    - Log the error details for debugging
@@ -657,6 +652,9 @@ Clarification File: {iteration_path}/01.product-requirement/.clarification-summa
 
 - **IF user confirms** (explicit "确认" or "OK"):
   1. Update checkpoint to record user confirmation:
+
+     > 🛑 **FORBIDDEN**: DO NOT manually edit .checkpoints.json via Write/Edit tools. ALL checkpoint updates MUST be done via `update-progress.js` script.
+
      ```bash
      node "{update_progress_script}" write-checkpoint \
        --file {iteration_path}/01.product-requirement/.checkpoints.json \
@@ -1289,10 +1287,14 @@ After presenting the documents above, you MUST stop and ask:
 > - If NO → Return to Phase 6.2 and wait for confirmation
 > - If YES → Proceed with the steps below
 
+> 🛑 **FORBIDDEN**: DO NOT manually edit WORKFLOW-PROGRESS.json via Write/Edit tools. ALL updates to this file MUST be done via `update-progress.js` script through `run_in_terminal`.
+
 **5.3.1 Update Checkpoints**
 
 Now update all checkpoints (user has confirmed):
 
+> 🛑 **FORBIDDEN**: DO NOT manually edit .checkpoints.json via Write/Edit tools. ALL checkpoint updates MUST be done via `update-progress.js` script.
+
 ```bash
 # Update verification_checklist checkpoint
 node "{update_progress_script}" write-checkpoint \
@@ -1309,10 +1311,14 @@ node "{update_progress_script}" write-checkpoint \
 
 **5.3.2 Update WORKFLOW-PROGRESS.json**
 
+**Update workflow status to completed:**
+```bash
+node "{update_progress_script}" update-workflow --file "{iterations_dir}/{iteration_name}/WORKFLOW-PROGRESS.json" --stage 01_prd --status completed
+```
+
+**Update workflow status to confirmed (after user confirms):**
 ```bash
-node "{update_progress_script}" update-workflow \
-  --file {iterations_dir}/{iteration}/WORKFLOW-PROGRESS.json \
-  --stage 01_prd --status completed
+node "{update_progress_script}" update-workflow --file "{iterations_dir}/{iteration_name}/WORKFLOW-PROGRESS.json" --stage 01_prd --status confirmed
 ```
 
 **5.3.3 Update PRD Status**

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

@@ -852,21 +852,21 @@ function main() {
       }
     }
 
-    // 使用目录路径构建唯一 ID，避免同名文件碰撞
-    // 例: mail/account/index.vue → mail-account-index
-    // 例: mail/template/index.vue → mail-template-index
-    // 例: dict/index.vue → dict-index (无嵌套时保持兼容)
+    // Use directory path to build unique ID, avoid filename collisions
+    // Example: mail/account/index.vue → mail-account-index
+    // Example: mail/template/index.vue → mail-template-index
+    // Example: dict/index.vue → dict-index (keep compatible when no nesting)
     let dirSegments = file.directory
       ? file.directory.replace(/[\/\\]/g, '-').replace(/^-+|-+$/g, '').replace(/-+/g, '-')
       : '';
 
-    // 顶层文件（directory = "."）不应引入 "."
+    // Top-level files (directory = ".") should not include "."
     if (dirSegments === '.' || dirSegments === './') {
       dirSegments = '';
     }
 
-    // 如果 dirSegments 已包含 moduleName 前缀，去除避免重复
-    // 例: directory='mail/account', moduleName='mail' → dirSegments='account'
+    // If dirSegments already contains moduleName prefix, remove to avoid duplication
+    // Example: directory='mail/account', moduleName='mail' → dirSegments='account'
     if (moduleName && dirSegments.startsWith(moduleName + '-')) {
       dirSegments = dirSegments.slice(moduleName.length + 1);
     } else if (moduleName && dirSegments === moduleName) {

package/.speccrew/skills/speccrew-knowledge-bizs-module-classify/scripts/apply-module-mapping.js

@@ -142,7 +142,7 @@ function main() {
       reclassifiedCount++;
       reclassifiedModules.add(oldModule);
       
-      // Rebuild documentPath（使用 fileName 而非 feature.id，避免文件名过长）
+      // Rebuild documentPath (use fileName instead of feature.id to avoid long filenames)
       const newDocumentPath = `speccrew-workspace/knowledges/bizs/${platformId}/${newModule}/${feature.fileName}.md`;
       
       return {

package/.speccrew/skills/speccrew-knowledge-bizs-module-classify/scripts/reindex-modules.js

@@ -1,20 +1,20 @@
 #!/usr/bin/env node
 /**
- * reindex-modules.js - 确定性脚本，用更新后的 exclude_dirs 对已有 features JSON 重新提取 module 名
+ * reindex-modules.js - Deterministic script to re-extract module names from existing features JSON with updated exclude_dirs
  * 
- * 调用方式:
+ * Usage:
  *   node reindex-modules.js --featuresFile "path/to/features-backend-system.json" --projectRoot "d:\dev\ruoyi-vue-pro"
  * 
- * 可选参数:
- *   --platformType "backend" - 如果不提供，从 features JSON 的 platformType 字段读取
- *   --techIdentifier "spring" - 如果不提供，尝试从 features JSON 推断（如 techStack 数组）
- *   --excludeDirs "controller,admin,api,service" - 如果不提供，从 tech-stack-mappings.json 加载
+ * Optional parameters:
+ *   --platformType "backend" - If not provided, read from features JSON's platformType field
+ *   --techIdentifier "spring" - If not provided, try to infer from features JSON (e.g., techStack array)
+ *   --excludeDirs "controller,admin,api,service" - If not provided, load from tech-stack-mappings.json
  */
 
 const fs = require('fs');
 const path = require('path');
 
-// === 工具函数（从 generate-inventory.js 复用） ===
+// === Utility functions (reused from generate-inventory.js) ===
 
 function normalizePath(filePath) {
   if (!filePath) return '';
@@ -32,7 +32,7 @@ function parseArrayParam(value) {
   return trimmed.split(',').map(s => s.trim()).filter(Boolean);
 }
 
-// Java/Kotlin 标准源码路径前缀
+// Java/Kotlin standard source path prefixes
 const STANDARD_SOURCE_PREFIXES = [
   'src/main/java',
   'src/main/kotlin',
@@ -77,7 +77,7 @@ function getModuleName(dirPath, excludeDirs, fallbackModuleName) {
   return '_root';
 }
 
-// === 辅助函数 ===
+// === Helper functions ===
 
 function parseArgs(argv) {
   const args = {};
@@ -113,10 +113,10 @@ function findProjectRoot(startPath) {
 function loadExcludeDirs(projectRoot, platformType, techIdentifier, featuresData) {
   console.log(`Loading exclude_dirs: platformType="${platformType}", techIdentifier="${techIdentifier || '(auto)'}"`);
   
-  // 尝试推断 techIdentifier
+  // Try to infer techIdentifier
   if (!techIdentifier) {
     const techStack = featuresData.techStack || [];
-    // 常见映射
+    // Common mappings
     const techMap = {
       'spring': 'spring', 'spring-boot': 'spring', 'java': 'spring',
       'vue': 'vue', 'vue3': 'vue', 'vue2': 'vue',
@@ -147,7 +147,7 @@ function loadExcludeDirs(projectRoot, platformType, techIdentifier, featuresData
   // Get fallback dirs for this platformType
   const fallback = FALLBACK_EXCLUDE_DIRS[platformType] || [];
   
-  // 查找 tech-stack-mappings.json
+  // Find tech-stack-mappings.json
   const configPaths = [
     path.join(projectRoot, 'speccrew-workspace', 'docs', 'configs', 'tech-stack-mappings.json'),
     path.join(projectRoot, 'docs', 'configs', 'tech-stack-mappings.json'),
@@ -207,25 +207,25 @@ function loadExcludeDirs(projectRoot, platformType, techIdentifier, featuresData
 }
 
 function extractPlatformId(featuresData) {
-  // 从第一个 feature 的 documentPath 提取 platformId
-  // 格式: "speccrew-workspace/knowledges/bizs/{platformId}/..."
+  // Extract platformId from first feature's documentPath
+  // Format: "speccrew-workspace/knowledges/bizs/{platformId}/..."
   for (const feature of (featuresData.features || [])) {
     if (feature.documentPath) {
       const match = normalizePath(feature.documentPath).match(/knowledges\/bizs\/([^/]+)\//);
       if (match) return match[1];
     }
   }
-  // 如果无法提取，用 platformType-platformSubtype 构建
+  // If unable to extract, build from platformType-platformSubtype
   if (featuresData.platformType && featuresData.platformSubtype) {
     return `${featuresData.platformType}-${featuresData.platformSubtype}`;
   }
   return null;
 }
 
-// === 主逻辑 ===
+// === Main logic ===
 
 function main() {
-  // 1. 解析命令行参数
+  // 1. Parse command line arguments
   const args = parseArgs(process.argv.slice(2));
   const featuresFile = args.featuresFile;
   
@@ -234,7 +234,7 @@ function main() {
     process.exit(1);
   }
   
-  // 2. 读取 features JSON
+  // 2. Read features JSON
   let featuresData;
   try {
     featuresData = JSON.parse(fs.readFileSync(featuresFile, 'utf8'));
@@ -250,16 +250,16 @@ function main() {
   const inventorySourcePath = normalizePath(featuresData.sourcePath || '');
   const platformType = args.platformType || featuresData.platformType || '';
   
-  // 3. 加载 exclude_dirs
+  // 3. Load exclude_dirs
   let excludeDirs = [];
   let stripModulePrefixes = [];
   if (args.excludeDirs) {
     excludeDirs = parseArrayParam(args.excludeDirs);
   } else {
-    // 从 tech-stack-mappings.json 加载，按优先级确定 techIdentifier：
-    // 1. 命令行参数 --techIdentifier
-    // 2. features JSON 中的 techIdentifier
-    // 3. features JSON 中的 platformSubtype (兼容旧数据)
+    // Load from tech-stack-mappings.json, determine techIdentifier by priority:
+    // 1. Command line parameter --techIdentifier
+    // 2. techIdentifier in features JSON
+    // 3. platformSubtype in features JSON (backward compatibility)
     const techId = args.techIdentifier || featuresData.techIdentifier || featuresData.platformSubtype;
     const config = loadExcludeDirs(projectRoot, platformType, techId, featuresData);
     excludeDirs = config.excludeDirs;
@@ -274,29 +274,29 @@ function main() {
   console.log(`Exclude dirs (${excludeDirs.length}): ${excludeDirs.join(', ')}`);
   console.log(`Total features: ${featuresData.features.length}`);
   
-  // 4. 重新计算每个 feature 的 module
+  // 4. Recalculate module for each feature
   const modulesBefore = [...new Set(featuresData.features.map(f => f.module))].sort();
   let reclassifiedCount = 0;
   
-  // 从 features JSON 获取 platformId（用于重建 documentPath）
-  // platformId 格式: "{platformType}-{platformSubtype}" 
-  // 从现有 documentPath 提取: "speccrew-workspace/knowledges/bizs/{platformId}/..."
+  // Get platformId from features JSON (for rebuilding documentPath)
+  // platformId format: "{platformType}-{platformSubtype}"
+  // Extract from existing documentPath: "speccrew-workspace/knowledges/bizs/{platformId}/..."
   const platformId = extractPlatformId(featuresData);
   
   featuresData.features.forEach(feature => {
-    // 计算 feature 源文件相对于 inventorySourcePath 的路径
+    // Calculate feature source file path relative to inventorySourcePath
     let relativePath = normalizePath(feature.sourcePath || '');
     
-    // 如果 feature.sourcePath 是绝对路径或相对于项目根，需要去掉 inventorySourcePath 前缀
+    // If feature.sourcePath is absolute or relative to project root, remove inventorySourcePath prefix
     if (inventorySourcePath && relativePath.startsWith(inventorySourcePath)) {
       relativePath = relativePath.slice(inventorySourcePath.length);
       if (relativePath.startsWith('/')) relativePath = relativePath.slice(1);
     }
-    // 也可能 inventorySourcePath 只是部分匹配
+    // inventorySourcePath may only partially match
     else if (inventorySourcePath) {
       const invParts = inventorySourcePath.split('/');
       const relParts = relativePath.split('/');
-      // 找到重叠部分
+      // Find overlapping part
       let startIdx = 0;
       for (let i = 0; i < relParts.length; i++) {
         if (relParts.slice(i, i + invParts.length).join('/') === inventorySourcePath) {
@@ -309,14 +309,14 @@ function main() {
       }
     }
     
-    // 取目录部分（去掉文件名）
+    // Get directory part (remove filename)
     const dirPath = path.dirname(relativePath).replace(/\\/g, '/');
     
-    // 用 getModuleName 重新提取模块名
+    // Re-extract module name using getModuleName
     const fallback = feature.module || '_root';
     let newModule = getModuleName(dirPath, excludeDirs, fallback);
     
-    // 应用 strip_module_prefixes 前缀去除
+    // Apply strip_module_prefixes prefix removal
     for (const prefix of stripModulePrefixes) {
       if (newModule.startsWith(prefix)) {
         newModule = newModule.substring(prefix.length);
@@ -328,21 +328,21 @@ function main() {
       reclassifiedCount++;
       feature.module = newModule;
       
-      // 重建 documentPath（使用 fileName 而非 feature.id，避免文件名过长）
+      // Rebuild documentPath (use fileName instead of feature.id to avoid long filenames)
       if (platformId) {
         feature.documentPath = `speccrew-workspace/knowledges/bizs/${platformId}/${newModule}/${feature.fileName}.md`;
       }
     }
   });
   
-  // 5. 更新 modules 数组
+  // 5. Update modules array
   const modulesAfter = [...new Set(featuresData.features.map(f => f.module))].sort();
   featuresData.modules = modulesAfter;
   
-  // 6. 写回文件
+  // 6. Write back to file
   fs.writeFileSync(featuresFile, JSON.stringify(featuresData, null, 2), 'utf8');
   
-  // 7. 输出结果
+  // 7. Output results
   const result = {
     status: 'success',
     modules_before: modulesBefore,

package/.speccrew/skills/speccrew-pm-module-initializer/SKILL.md

@@ -8,11 +8,14 @@ tools: Read, Write, Skill, Bash
 
 Initialize knowledge base for a single business module by analyzing its features. Dispatches api-analyze or ui-analyze based on platform type, then generates module summary. Used by Worker Agent, invoked by PM Agent for on-demand module initialization.
 
+> **Positioning**: Lightweight knowledge base initializer for PM phase, processes only modules matched by PM matcher.
+> Difference from bizs-dispatch: module-initializer processes single modules on-demand, does not generate graph data, output is for PRD authoring reference only.
+
 ## Language Adaptation
 
 **CRITICAL**: Generate all content in the language specified by the `language` parameter.
 
-- `language: "zh"` → Generate all content in 中文
+- `language: "zh"` → Generate all content in Chinese
 - `language: "en"` → Generate all content in English
 - Other languages → Use the specified language
 
@@ -29,15 +32,17 @@ Initialize knowledge base for a single business module by analyzing its features
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
-| `source_path` | string | Yes | 项目源码根路径 |
-| `module_name` | string | Yes | 模块名称 |
-| `platform_id` | string | Yes | 平台 ID (e.g., "web-vue3", "admin-api") |
+| `source_path` | string | Yes | Project source code root path |
+| `module_name` | string | Yes | Module name |
+| `platform_id` | string | Yes | Platform ID (e.g., "web-vue3", "admin-api") |
 | `platform_type` | string | Yes | web / mobile / backend / desktop |
 | `platform_subtype` | string | No | Platform subtype (e.g., "vue", "spring-boot") |
 | `tech_stack` | array | No | Platform tech stack (e.g., ["java", "spring-boot"]) |
-| `features_file` | string | Yes | 该平台的 features-{platform}.json 路径 |
-| `output_path` | string | Yes | 知识库输出根路径 (e.g., speccrew-workspace/knowledges) |
-| `language` | string | Yes | 输出语言 (zh / en) |
+| `features_file` | string | Yes | Path to the platform's features-{platform}.json file |
+| `output_path` | string | Yes | Knowledge base output root path (e.g., speccrew-workspace/knowledges) |
+| `completed_dir` | string | Yes | Marker file output directory for api-analyze .done.json markers. Value from PM Agent: `{sync_state_bizs_dir}/completed` |
+| `sourceFile` | string | Yes | Features JSON filename (e.g., "features-backend-system.json"), used for api-analyze marking |
+| `language` | string | Yes | Output language (zh / en) |
 
 ## Output JSON
 
@@ -100,38 +105,67 @@ Based on `platform_type`, select the appropriate analyzer Skill:
 
 **Output**: "Step 2 Status: ✅ COMPLETED - Selected analyzer: {skill_name}"
 
-### Step 3: Analyze Each Pending Feature
+### Step 3: Analyze Each Pending Feature (Sequential)
 
 **Step 3 Status: 🔄 IN PROGRESS**
 
-For each pending feature, invoke the selected analyzer Skill.
+For each pending feature from Step 1, call the appropriate analyzer skill.
+
+> 🛑 **FORBIDDEN**: DO NOT write custom scripts. You MUST call the analyzer skill directly using the Agent tool or execute it as defined in the skill's SKILL.md.
 
-**Important**: Process features sequentially (not parallel) since this Skill runs inside a single Worker Agent. The PM Agent handles parallelism at the module level (multiple Workers for different modules).
+#### For backend modules (api-analyze):
 
-#### Input Variables Preparation
+For each pending feature, invoke the `speccrew-knowledge-bizs-api-analyze` skill with these parameters:
 
-Prepare input variables matching the analyzer Skill's Input Variables format:
+```
+Use Agent tool to invoke speccrew-task-worker:
+- agent: speccrew-task-worker  
+- task: Execute speccrew-knowledge-bizs-api-analyze skill
+- context:
+    skill: speccrew-knowledge-bizs-api-analyze
+    fileName: {feature.fileName}
+    sourcePath: {source_path}/{feature.sourcePath}
+    documentPath: {output_path}/bizs/{platform_id}/{feature.module}/features
+    module: {feature.module}
+    analyzed: false
+    platform_type: backend
+    platform_subtype: {platform_subtype}
+    tech_stack: {tech_stack}
+    language: {language}
+    completed_dir: {completed_dir}
+    sourceFile: {sourceFile}
+```
 
-| Variable | Value Source |
-|----------|--------------|
-| `feature` | The complete feature object from features.json |
-| `fileName` | feature's fileName field |
-| `sourcePath` | feature's sourcePath field |
-| `documentPath` | Computed as `{output_path}/bizs/{platform_id}/{module_name}/{fileName}.md` |
-| `module` | module_name |
-| `analyzed` | false |
-| `platform_type` | From input |
-| `platform_subtype` | From input (if available) |
-| `tech_stack` | From input (if available) |
-| `language` | From input |
-| `completed_dir` | `{output_path}/base/sync-state/knowledge-bizs/completed/` |
-| `sourceFile` | Features JSON filename (e.g., "features-web-vue3.json") |
+#### For web/mobile/desktop modules (ui-analyze):
 
-#### Execution for Each Feature
+For each pending feature, invoke the `speccrew-knowledge-bizs-ui-analyze` skill with these parameters:
 
-1. Invoke the selected analyzer Skill with prepared parameters
-2. Track success/failure count
-3. On success, update the feature's `analyzed` field to `true` in features_file
+```
+Use Agent tool to invoke speccrew-task-worker:
+- agent: speccrew-task-worker
+- task: Execute speccrew-knowledge-bizs-ui-analyze skill  
+- context:
+    skill: speccrew-knowledge-bizs-ui-analyze
+    fileName: {feature.fileName}
+    sourcePath: {source_path}/{feature.sourcePath}
+    documentPath: {output_path}/bizs/{platform_id}/{feature.module}/features
+    module: {feature.module}
+    analyzed: false
+    platform_type: {platform_type}
+    platform_subtype: {platform_subtype}
+    tech_stack: {tech_stack}
+    language: {language}
+```
+
+> **NOTE**: UI Analyzer does NOT write .done.json marker files (handled by ui-graph skill in bizs-dispatch).
+
+#### After each successful analysis:
+Update the feature's `analyzed` field to `true` in the features JSON file.
+
+#### Error handling:
+- If an analyzer fails, log the error, increment `features_failed` counter
+- Continue with next feature (do NOT abort the entire module)
+- A module with partial analysis is better than no analysis
 
 **Output**: "Step 3 Status: ✅ COMPLETED - Analyzed {success} features, {failed} failed"
 
@@ -139,15 +173,25 @@ Prepare input variables matching the analyzer Skill's Input Variables format:
 
 **Step 4 Status: 🔄 IN PROGRESS**
 
-Invoke `speccrew-knowledge-module-summarize` Skill to generate/update the module overview document.
-
-**Input Parameters**:
-
-| Variable | Value |
-|----------|-------|
-| `module_name` | module_name |
-| `module_path` | `{output_path}/bizs/{platform_id}/{module_name}/` |
-| `language` | From input |
+**Pre-check**: Verify that feature documents exist at `{output_path}/bizs/{platform_id}/{module_name}/features/`.
+
+IF no feature documents exist AND features_analyzed == 0:
+  - Set status to "partial"
+  - Skip module-summarize
+  - Proceed to Step 5
+
+IF feature documents exist:
+  Invoke `speccrew-knowledge-module-summarize` skill:
+  ```
+  Use Agent tool to invoke speccrew-task-worker:
+  - agent: speccrew-task-worker
+  - task: Execute speccrew-knowledge-module-summarize skill
+  - context:
+      skill: speccrew-knowledge-module-summarize
+      module_name: {module_name}
+      module_path: {output_path}/bizs/{platform_id}/{module_name}
+      language: {language}
+  ```
 
 **Output**: "Step 4 Status: ✅ COMPLETED - Module overview generated at {module_path}/{module_name}-overview.md"
 

package/lib/commands/doctor.js

@@ -8,7 +8,7 @@ function run(projectRoot, args) {
 
   const results = [];
 
-  // 1. Node.js 版本检查
+  // 1. Node.js version check
   const nodeVersion = process.version;
   const majorVersion = parseInt(nodeVersion.slice(1).split('.')[0], 10);
   if (majorVersion >= 16) {
@@ -17,7 +17,7 @@ function run(projectRoot, args) {
     results.push({ status: 'FAIL', message: `Node.js ${nodeVersion} (< 16.0.0)` });
   }
 
-  // 2. SpecCrew 安装状态
+  // 2. SpecCrew installation status
   const rc = readSpeccrewRC(projectRoot);
   const version = getPackageVersion();
   if (rc) {
@@ -26,7 +26,7 @@ function run(projectRoot, args) {
     results.push({ status: 'WARN', message: 'Not initialized, run speccrew init' });
   }
 
-  // 3. IDE 目录检查
+  // 3. IDE directory check
   const detectedIDEs = detectIDE(projectRoot);
   if (detectedIDEs.length > 0) {
     const ideNames = detectedIDEs.map(ide => `${ide.name} (${ide.baseDir}/)`).join(', ');
@@ -35,7 +35,7 @@ function run(projectRoot, args) {
     results.push({ status: 'WARN', message: 'No supported IDE detected' });
   }
 
-  // 4. Agents 完整性检查
+  // 4. Agents integrity check
   const sourceRoot = getSourceRoot();
   const sourceAgentsDir = path.join(sourceRoot, 'agents');
   let sourceAgentCount = 0;
@@ -70,7 +70,7 @@ function run(projectRoot, args) {
     results.push({ status: 'WARN', message: 'Agents: source not found' });
   }
 
-  // 5. Skills 完整性检查
+  // 5. Skills integrity check
   const sourceSkillsDir = path.join(sourceRoot, 'skills');
   let sourceSkillCount = 0;
   let installedSkillCount = 0;
@@ -103,7 +103,7 @@ function run(projectRoot, args) {
     results.push({ status: 'WARN', message: 'Skills: source not found' });
   }
 
-  // 6. Workspace 目录检查
+  // 6. Workspace directory check
   const workspaceDir = path.join(projectRoot, 'speccrew-workspace');
   const docsDir = path.join(workspaceDir, 'docs');
   if (fs.existsSync(workspaceDir) && fs.existsSync(docsDir)) {
@@ -114,7 +114,7 @@ function run(projectRoot, args) {
     results.push({ status: 'WARN', message: 'Workspace: speccrew-workspace/ not found' });
   }
 
-  // 输出结果
+  // Output results
   let passCount = 0;
   let warnCount = 0;
   let failCount = 0;