speccrew 0.7.32 → 0.7.33

package/.speccrew/agents/speccrew-feature-designer.md

@@ -171,10 +171,21 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 > **If ANY of the following conditions occur, the Feature Designer Agent MUST immediately STOP the workflow and report to user.**
 
 1. **Skill Invocation Failure**: Any skill call returns error → STOP. Do NOT generate content manually.
-2. **Script Execution Failure**: `node ... update-progress.js` fails → STOP. Do NOT manually create/edit JSON files.
+2. **Script Execution Failure**: `node ... update-progress.js` exits with non-zero status or output contains "Error:" → STOP immediately.
+   - Do NOT attempt to continue batch processing
+   - Do NOT ask user for alternative options (A/B/C)
+   - Do NOT suggest "skip to next phase" or "process only some features"
+   - Report exact error message, failed task ID, and failed command
 3. **Missing Intermediate Artifacts**: Feature Spec output missing before Phase 4 → STOP.
 4. **User Rejection**: User rejects Feature List, batch design summary, or Joint Confirmation → STOP, ask for specific revision requirements.
 5. **Worker Batch Failure**: If >50% workers in a batch fail → STOP entire batch, report to user.
+6. **Progress File Read Failure**: Cannot read DISPATCH-PROGRESS.json → STOP.
+
+> 🛑 **FORBIDDEN ON SCRIPT FAILURE**:
+> - ❌ "Due to script errors, I suggest we..."
+> - ❌ "Let me offer you options: 1. Continue 2. Skip 3. ..."
+> - ❌ "进度更新脚本频繁失败，建议..."
+> - ✅ ONLY correct response: "STOP: update-progress.js failed with [error]. Task: [id]. Command: [cmd]."
 
 ## TIMESTAMP INTEGRITY
 
@@ -208,7 +219,7 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 ## Phase 0: Workflow Progress Management
 
 > **Path Variables** (provided by caller as absolute paths):
-> - `workspace_path`: Absolute path to speccrew-workspace directory
+> - `workspace_path`: **MANDATORY absolute path** — Worker MUST use this for ALL script calls. Example: `D:\dev\RuoYi-Vue3-FastAPI\speccrew-workspace`
 > - `update_progress_script`: `{workspace_path}/scripts/update-progress.js`
 > - `iterations_dir`: `{workspace_path}/iterations`
 

package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md

@@ -52,6 +52,14 @@ This skill applies ISA-95 Stages 1-6 as an internal thinking framework:
 4. **FORBIDDEN: Skip Checkpoint B** — User confirmation required before generating documents (unless `skip_checkpoint=true`)
 5. **FORBIDDEN: Rename features** — Output filename MUST use the exact `feature_name` parameter value. DO NOT translate, abbreviate, paraphrase, or substitute with alternative names found in PRD content. The `feature_name` parameter is the SINGLE SOURCE OF TRUTH for file naming.
 
+> **CRITICAL: Script Path Rule**
+> ALL update-progress.js commands MUST use absolute paths with `{workspace_path}`:
+> ```
+> node "{workspace_path}/scripts/update-progress.js" update-task --file "{workspace_path}/iterations/..." ...
+> ```
+> NEVER use relative paths like `node scripts/update-progress.js` or `cd ... ; node scripts/...`
+> The Worker may execute from project root directory, NOT from speccrew-workspace directory.
+
 ⛔ **ABSOLUTE PROHIBITION — Phase B Content Filling:**
 - NEVER use `create_file` to rewrite or recreate the document after Step 5 skeleton creation
 - NEVER abandon `search_replace` mid-way and switch to `create_file`
@@ -178,8 +186,8 @@ If `skip_analysis_checkpoint=false` (default):
 After user confirms (or if skipped):
 
 ```bash
-node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-  --file speccrew-workspace/iterations/{iteration_id}/02.feature-design/.checkpoints.json \
+node "{workspace_path}/scripts/update-progress.js" write-checkpoint \
+  --file "{workspace_path}/iterations/{iteration_id}/02.feature-design/.checkpoints.json" \
   --stage 02_feature_design \
   --checkpoint function_decomposition \
   --passed true
@@ -493,8 +501,8 @@ Document: `User Action → Frontend Response → Backend API Call`
 After user confirms (or if skipped):
 
 ```bash
-node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-  --file speccrew-workspace/iterations/{iteration_id}/02.feature-design/.checkpoints.json \
+node "{workspace_path}/scripts/update-progress.js" write-checkpoint \
+  --file "{workspace_path}/iterations/{iteration_id}/02.feature-design/.checkpoints.json" \
   --stage 02_feature_design \
   --checkpoint feature_design_review \
   --passed true
@@ -654,8 +662,8 @@ Verify all Mermaid diagrams follow compliance rules:
 Set final checkpoint status:
 
 ```bash
-node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-  --file speccrew-workspace/iterations/{iteration_id}/02.feature-design/.checkpoints.json \
+node "{workspace_path}/scripts/update-progress.js" write-checkpoint \
+  --file "{workspace_path}/iterations/{iteration_id}/02.feature-design/.checkpoints.json" \
   --stage 02_feature_design \
   --checkpoint feature_spec_review \
   --passed true

package/package.json

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

package/workspace-template/scripts/update-progress.js

@@ -35,6 +35,7 @@
  *      --output <text>         Task output (used when completed)
  *      --error <text>          Error message (used when failed)
  *      --error-category <cat>  Error category (used when failed)
+ *      --metadata <json>       Metadata JSON string to merge into task
  *
  * 4. update-counts - Force recalculate counts
  *    node update-progress.js update-counts --file <path>
@@ -252,7 +253,8 @@ function parseArgs() {
         confirmedAt: null,
         featuresDir: null,
         platforms: null,
-        force: false
+        force: false,
+        metadata: null
     };
 
     // First argument is the command
@@ -357,6 +359,10 @@ function parseArgs() {
             case '-Matcher-Result':
                 result.matcherResult = args[++i];
                 break;
+            case '--metadata':
+            case '-Metadata':
+                result.metadata = args[++i];
+                break;
         }
     }
 
@@ -619,6 +625,16 @@ function cmdUpdateTask(args) {
             }
         }
 
+        // Handle metadata (merge into task)
+        if (args.metadata) {
+            try {
+                const metadataObj = JSON.parse(args.metadata);
+                task.metadata = { ...task.metadata, ...metadataObj };
+            } catch (e) {
+                outputError(`Failed to parse metadata JSON: ${e.message}`);
+            }
+        }
+
         // Update task
         data.tasks[taskIndex] = task;
         data.updated_at = now;