speccrew 0.7.34 → 0.7.35

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

@@ -54,7 +54,7 @@ Phase 4: API Contract Generation
 | ALL | ABORT ON FAILURE | If any skill invocation fails → STOP and report. Do NOT attempt to generate content manually as fallback |
 | ALL | SCRIPT ENFORCEMENT | All .checkpoints.json and WORKFLOW-PROGRESS.json updates via update-progress.js script. Manual JSON creation FORBIDDEN |
 | ALL | NAME LOCK | After Phase 2 Feature List is confirmed, feature_name is immutable. All Skills MUST use the exact parameter value for output filenames. Name translation or substitution is FORBIDDEN |
-| ALL | ANTI-SCRIPT | Agent MUST NOT create custom automation scripts. DO NOT generate helper scripts (.sh, .ps1, .js) for batch processing or progress checking. Use ONLY the standard update-progress.js commands in documented workflow order. |
+| ALL | ANTI-SCRIPT | Agent MUST NOT create custom automation scripts. DO NOT generate helper scripts (.sh, .ps1, .js) for batch processing or progress checking. Use ONLY the standard update-progress.js commands in documented workflow order. If a required temp file (.tasks-temp.json) is missing, this indicates a workflow orchestration gap — follow the XML workflow's regeneration step, do NOT implement workarounds with ad-hoc commands. |
 
 ## MANDATORY WORKER ENFORCEMENT
 
@@ -756,15 +756,33 @@ If **2+ Feature Specs** in registry:
 > Worker will read the skill's workflow.agentflow.xml for its execution plan.
 > See: MANDATORY: Worker Dispatch Prompt Format section above.
 
+### Phase 4: API Contract — Task File Management
+
+⚠️ **CRITICAL: .tasks-temp.json Regeneration**
+
+Phase 3 deletes `.tasks-temp.json` after init. Phase 4 MUST regenerate it before init:
+
+1. Read `{iteration_path}/02.feature-design/DISPATCH-PROGRESS.json` (Phase 3 results)
+2. Extract ALL task IDs from the tasks array
+3. Build flat JSON array: `[{"id":"F-M01-01"},{"id":"F-M01-02"},...]`
+4. Write to `{iteration_path}/03.api-contract/.tasks-temp.json`
+5. Run init: `node {workspace_path}/scripts/update-progress.js init --file {iteration_path}/03.api-contract/DISPATCH-PROGRESS.json --stage 02_feature_design_api_contract --tasks-file {iteration_path}/03.api-contract/.tasks-temp.json`
+6. Delete `.tasks-temp.json` after successful init
+
+**DO NOT**:
+- Run ad-hoc PowerShell/Bash commands to parse `.prd-feature-list.json`
+- Create custom scripts to build task lists
+- Skip the init step and manually edit DISPATCH-PROGRESS.json
+
 1. **Initialize DISPATCH-PROGRESS.json for API Contract stage**:
 
    > ⚠️ Use `--tasks-file` instead of `--tasks` to avoid PowerShell JSON parsing issues.
 
    ```bash
-   # Step 1: Write tasks JSON to temp file inside iteration directory
-   # Create .tasks-temp.json with the task array content
+   # Step 1: Read Phase 3 DISPATCH-PROGRESS.json and extract all task IDs
+   # Build flat JSON array: [{"id":"F-XXX"},...] and write to .tasks-temp.json
    # Step 2: Initialize with --tasks-file
-   node {update_progress_script} init --file {iterations_dir}/{iteration}/03.api-contract/DISPATCH-PROGRESS.json --stage 02_feature_design_api_contract --tasks-file {iterations_dir}/{iteration}/02.feature-design/.tasks-temp.json
+   node {update_progress_script} init --file {iterations_dir}/{iteration}/03.api-contract/DISPATCH-PROGRESS.json --stage 02_feature_design_api_contract --tasks-file {iterations_dir}/{iteration}/03.api-contract/.tasks-temp.json
    # Step 3: Delete .tasks-temp.json after successful init
    ```
 

package/.speccrew/agents/speccrew-task-worker.md

@@ -65,6 +65,13 @@ When executing design or document generation skills:
 - Only output brief block execution announcements
 - This is especially critical in batch mode where multiple Workers run simultaneously
 
+### FILE ENCODING
+
+ALL file operations MUST use UTF-8 encoding explicitly:
+- When creating files via tools: ensure UTF-8 (most IDE tools default to UTF-8)
+- When writing via Node.js: always pass `'utf8'` as encoding parameter
+- NEVER rely on system default encoding — Chinese Windows defaults to GBK which corrupts Unicode characters
+
 **FORBIDDEN output in conversation during design tasks:**
 - ASCII wireframes / UI prototypes
 - Mermaid diagrams (these go in the file only)

package/.speccrew/skills/speccrew-feature-designer-orchestration/workflow.agentflow.xml

@@ -355,9 +355,15 @@
           <field name="text">DO NOT invoke speccrew-fd-api-contract directly</field>
         </block>
 
+        <!-- Phase 4.1a: Regenerate tasks file from Phase 3 completed features -->
+        <block type="task" id="P4-B1c" action="analyze" status="pending" desc="Build API Contract task list from Phase 3 DISPATCH-PROGRESS.json">
+          <field name="text">Read ${iteration_path}/02.feature-design/DISPATCH-PROGRESS.json. Extract all task IDs (regardless of status). Build a flat JSON array: [{"id":"F-M01-01"},{"id":"F-M01-02"},...]. Write this array to ${iteration_path}/03.api-contract/.tasks-temp.json</field>
+          <field name="output" var="api_contract_tasks_file"/>
+        </block>
+
         <!-- Initialize DISPATCH-PROGRESS.json for API Contract stage -->
         <block type="task" id="P4-B2" action="run-script" status="pending" desc="Initialize API contract dispatch">
-          <field name="command">node ${workspace_root}/scripts/update-progress.js init --file ${iteration_path}/03.api-contract/DISPATCH-PROGRESS.json --stage 02_feature_design_api_contract --tasks-file ${iteration_path}/02.feature-design/.tasks-temp.json</field>
+          <field name="command">node ${workspace_root}/scripts/update-progress.js init --file ${iteration_path}/03.api-contract/DISPATCH-PROGRESS.json --stage 02_feature_design_api_contract --tasks-file ${iteration_path}/03.api-contract/.tasks-temp.json</field>
         </block>
 
         <!-- MANDATORY: Dispatch prompt must contain ONLY skill path + context data parameters.

package/.speccrew/skills/speccrew-pm-sub-prd-generate/SKILL.md

@@ -201,6 +201,14 @@ IF verification fails:
 > **Purpose:** Separate feature data from dispatch plan into dedicated `.prd-feature-list.json` file.
 > Each Sub-PRD Worker writes its module's features upon completion.
 
+> **CRITICAL: UTF-8 Encoding**
+> 
+> When writing ANY file (JSON, Markdown, or other text files), you MUST ensure UTF-8 encoding:
+> - Use `create_file` tool (which defaults to UTF-8) for file creation
+> - If using Node.js scripts: `fs.writeFileSync(path, content, 'utf8')`
+> - NEVER rely on system default encoding (may be GBK on Chinese Windows)
+> - This applies to ALL output files including `.prd-feature-list.json`
+
 ### 5.1 Determine Feature List File Path
 
 ```

package/.speccrew/skills/speccrew-pm-sub-prd-generate/workflow.agentflow.xml

@@ -190,6 +190,7 @@
 
     <block type="task" id="B17" action="write-file" desc="Update feature list file">
       <field name="path" value="${feature_list_path}"/>
+      <field name="encoding">utf8</field>
       <field name="merge">true</field>
       <field name="entry" value="${feature_list_entry}"/>
       <field name="output" var="feature_list_updated"/>

package/package.json

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