speccrew 0.7.60 → 0.7.61

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

@@ -133,6 +133,7 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 | Phase 4 | WORKER-DISPATCH + HARD STOP | DESIGN-OVERVIEW.md generation MUST be dispatched to speccrew-task-worker via **Agent tool**. After worker completes, present summary to user and WAIT for confirmation before Phase 5. |
 | Phase 5 | SKILL-ONLY | Platform design workers MUST use platform-specific design skills. Agent MUST NOT write design documents itself |
 | Phase 5 | SKIP-CONFIRMATION | Batch dispatch MUST include `skip_confirmation: true` and `skip_index_generation: true` in worker context. Workers skip Checkpoint A and Step 5 in batch mode |
+| Phase 5 | WORKER-SELF-UPDATE | Batch dispatch MUST include `dispatch_progress_file` and `update_progress_script` in worker context. Workers self-update task status in DISPATCH-PROGRESS.json upon completion (Step 7 of platform skills). Orchestrator's P5-B4-POST serves as fallback |
 | Phase 5.5 | WORKER-DISPATCH-INDEX | After all workers complete, dispatch ONE worker per platform with `index_only: true` to generate INDEX.md. Orchestrator MUST NOT generate INDEX.md directly |
 | Phase 6 | HARD STOP | User must confirm all designs before finalizing |
 | ALL | ABORT ON FAILURE | If any skill invocation fails → STOP and report. Do NOT generate content manually as fallback |
@@ -776,6 +777,8 @@ Each worker receives:
   - `techs_knowledge_paths`: Techs knowledge paths for this platform
   - `framework_decisions`: Framework decisions from Phase 3
   - `output_base_path`: Path to `03.system-design/` directory
+  - `dispatch_progress_file`: Path to DISPATCH-PROGRESS.json (enables Worker to self-update task status on completion)
+  - `update_progress_script`: Path to update-progress.js script
 
 **Before dispatch**: Update each task status to `in_progress`:
 ```bash
@@ -796,7 +799,7 @@ All workers execute simultaneously to maximize efficiency.
 > 1. **ONE Worker per Feature×Platform combination** — DO NOT group
 > 2. Use **Agent tool** to create `speccrew-task-worker` for each task
 > 3. Pass `skill_path`: `${ide_skills_dir}/${skill_name}/SKILL.md` (platform-specific skill)
-> 4. Pass context: task_id, feature_id, feature_name, platform_id, feature_spec_path, api_contract_path, techs_knowledge_paths, framework_decisions, output_base_path, **skip_confirmation: true**, **skip_index_generation: true**
+> 4. Pass context: task_id, feature_id, feature_name, platform_id, feature_spec_path, api_contract_path, techs_knowledge_paths, framework_decisions, output_base_path, **skip_confirmation: true**, **skip_index_generation: true**, **dispatch_progress_file**, **update_progress_script**
 > 5. Dispatch ALL Workers in the same batch **SIMULTANEOUSLY** in a single turn
 > 6. **Wait** for ALL Workers in the batch to complete before dispatching next batch
 > 7. Update DISPATCH-PROGRESS.json after each Worker completes

package/.speccrew/skills/speccrew-sd-backend/SKILL.md

@@ -28,6 +28,8 @@ tools: Read, Write, Glob, Grep
 
 3. **MANDATORY: Template-first workflow** — Copy template MUST execute before fill sections. Skipping copy and writing content directly is FORBIDDEN.
 
+4. **MANDATORY: Output filename pattern** — Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md`. Omitting feature_id or using alternative naming is FORBIDDEN.
+
 ## Step 1: Read Inputs
 
 > **Conditional Execution**: If `index_only` = `true`, **skip Steps 1-4** and jump directly to Step 5 to generate INDEX.md.
@@ -39,6 +41,9 @@ tools: Read, Write, Glob, Grep
 - `skip_confirmation` (optional, boolean): When `true`, skip Checkpoint A user confirmation (used in batch dispatch mode)
 - `skip_index_generation` (optional, boolean): When `true`, skip Step 5 INDEX.md generation (INDEX.md will be generated by orchestrator after all workers complete)
 - `index_only` (optional, boolean): When `true`, skip Steps 1-4 and ONLY execute Step 5 (INDEX.md generation). Used after all platform workers complete.
+- `task_id` (optional, string): Task identifier in DISPATCH-PROGRESS.json. Used for status tracking.
+- `dispatch_progress_file` (optional, string): Path to DISPATCH-PROGRESS.json. If provided, worker updates its own task status on completion.
+- `update_progress_script` (optional, string): Path to update-progress.js script.
 
 Read in order:
 
@@ -103,6 +108,30 @@ Mark each function as:
 
 For each function (or logical group = one controller/module):
 
+### Output File Naming Convention
+
+**MANDATORY**: The design document file MUST be named using this exact pattern:
+
+```
+{feature_id}-{feature_name}-design.md
+```
+
+Examples:
+- `F-M01-05-操作日志-design.md` ✅
+- `F-M02-01-顾客档案管理-design.md` ✅
+- `member-level-change-history-design.md` ❌ (missing feature_id prefix)
+- `customer-profile-design.md` ❌ (missing feature_id prefix)
+
+Where:
+- `feature_id`: The exact feature ID from dispatch context (e.g., `F-M01-05`, `F-M02-01`)
+- `feature_name`: The exact feature name from dispatch context (e.g., `操作日志`, `顾客档案管理`)
+
+> ⚠️ **FORBIDDEN**: 
+> - Using any filename format other than `{feature_id}-{feature_name}-design.md`
+> - Omitting the feature_id prefix
+> - Translating or paraphrasing the feature_name (must use the exact name from context)
+> - Using function/sub-feature names instead of the main feature_name
+
 ### 4.1 Read Template
 
 Read the SD-BACKEND-TEMPLATE.md to understand document structure.
@@ -236,7 +265,24 @@ Files Generated:
 - {list all file paths}
 ```
 
-## Step 7: Task Completion Report
+## Step 7: Update Task Status (if dispatch_progress_file provided)
+
+> **Conditional Execution**: Only execute this step if `dispatch_progress_file` and `task_id` parameters are provided in the dispatch context.
+
+Update the task status in DISPATCH-PROGRESS.json to mark this task as completed:
+
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status completed
+```
+
+If the design document generation failed at any step, update with status `failed` instead:
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status failed
+```
+
+> ⚠️ **IMPORTANT**: This step MUST be the last action before returning the completion report. Do NOT skip this step in batch dispatch mode.
+
+## Step 8: Task Completion Report
 
 After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
 
@@ -305,6 +351,7 @@ When executing this skill:
 | **FORBIDDEN: TODO/FIXME Placeholders** | Design documents MUST contain complete implementation logic. Do NOT use TODO, FIXME, HACK, or any placeholder comments. Every method, validation rule, and business logic MUST be fully specified with actual pseudocode. |
 | **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
 | **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy for when that Feature is not yet implemented. |
+| **Output Filename Pattern** | Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md` |
 
 # Mermaid Diagram Requirements
 
@@ -334,6 +381,7 @@ When generating Mermaid diagrams, follow compatibility guidelines:
 - [ ] Migration requirements documented
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
+- [ ] Output file named as `{feature_id}-{feature_name}-design.md`
 - [ ] All Mermaid diagrams follow compatibility guidelines
 - [ ] **No TODO/FIXME placeholders** — all methods have complete pseudocode implementation
 - [ ] **API routes match API Contract exactly** — verified route-by-route

package/.speccrew/skills/speccrew-sd-frontend/SKILL.md

@@ -28,6 +28,8 @@ tools: Read, Write, Glob, Grep
 
 3. **MANDATORY: Template-first workflow** — Copy template MUST execute before fill sections. Skipping copy and writing content directly is FORBIDDEN.
 
+4. **MANDATORY: Output filename pattern** — Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md`. Omitting feature_id or using alternative naming is FORBIDDEN.
+
 ## Step 1: Read Inputs
 
 > **Conditional Execution**: If `index_only` = `true`, **skip Steps 1-4** and jump directly to Step 5 to generate INDEX.md.
@@ -39,6 +41,9 @@ tools: Read, Write, Glob, Grep
 - `skip_confirmation` (optional, boolean): When `true`, skip Checkpoint A user confirmation (used in batch dispatch mode)
 - `skip_index_generation` (optional, boolean): When `true`, skip Step 5 INDEX.md generation (INDEX.md will be generated by orchestrator after all workers complete)
 - `index_only` (optional, boolean): When `true`, skip Steps 1-4 and ONLY execute Step 5 (INDEX.md generation). Used after all platform workers complete.
+- `task_id` (optional, string): Task identifier in DISPATCH-PROGRESS.json. Used for status tracking.
+- `dispatch_progress_file` (optional, string): Path to DISPATCH-PROGRESS.json. If provided, worker updates its own task status on completion.
+- `update_progress_script` (optional, string): Path to update-progress.js script.
 
 Read in order:
 
@@ -101,6 +106,30 @@ Mark each function's components as:
 
 For each function (or logical group of closely related functions = one module):
 
+### Output File Naming Convention
+
+**MANDATORY**: The design document file MUST be named using this exact pattern:
+
+```
+{feature_id}-{feature_name}-design.md
+```
+
+Examples:
+- `F-M01-05-操作日志-design.md` ✅
+- `F-M02-01-顾客档案管理-design.md` ✅
+- `member-level-change-history-design.md` ❌ (missing feature_id prefix)
+- `customer-profile-design.md` ❌ (missing feature_id prefix)
+
+Where:
+- `feature_id`: The exact feature ID from dispatch context (e.g., `F-M01-05`, `F-M02-01`)
+- `feature_name`: The exact feature name from dispatch context (e.g., `操作日志`, `顾客档案管理`)
+
+> ⚠️ **FORBIDDEN**: 
+> - Using any filename format other than `{feature_id}-{feature_name}-design.md`
+> - Omitting the feature_id prefix
+> - Translating or paraphrasing the feature_name (must use the exact name from context)
+> - Using function/sub-feature names instead of the main feature_name
+
 ### 4.1 Read Template
 
 Read `SD-FRONTEND-TEMPLATE.md` for document structure.
@@ -234,7 +263,24 @@ Concerns/Trade-offs:
 3. Do the pseudo-code patterns match project conventions?
 4. Are all API calls from API Contract covered?
 
-## Step 7: Task Completion Report
+## Step 7: Update Task Status (if dispatch_progress_file provided)
+
+> **Conditional Execution**: Only execute this step if `dispatch_progress_file` and `task_id` parameters are provided in the dispatch context.
+
+Update the task status in DISPATCH-PROGRESS.json to mark this task as completed:
+
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status completed
+```
+
+If the design document generation failed at any step, update with status `failed` instead:
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status failed
+```
+
+> ⚠️ **IMPORTANT**: This step MUST be the last action before returning the completion report. Do NOT skip this step in batch dispatch mode.
+
+## Step 8: Task Completion Report
 
 After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
 
@@ -286,6 +332,7 @@ After completing all steps, output a structured completion report for the System
 | **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
 | **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy (e.g., hide button, show placeholder) for when that Feature is not yet implemented. |
 | **Mermaid for All Diagrams** | ALL component trees, interaction flows, and state management diagrams MUST use Mermaid syntax (`graph TB`, `sequenceDiagram`, `flowchart`). Plain text ASCII diagrams are FORBIDDEN for these sections. |
+| **Output Filename Pattern** | Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md` |
 
 # Checklist
 
@@ -299,6 +346,7 @@ After completing all steps, output a structured completion report for the System
 - [ ] Directory structure follows conventions-design.md
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
+- [ ] Output file named as `{feature_id}-{feature_name}-design.md`
 - [ ] Checkpoint A passed: function extraction confirmed (or skipped via skip_confirmation)
 - [ ] **No TODO/FIXME placeholders** — all components and methods have complete pseudocode
 - [ ] **API routes match API Contract exactly** — verified route-by-route

package/.speccrew/skills/speccrew-sd-mobile/SKILL.md

@@ -28,6 +28,8 @@ tools: Read, Write, Glob, Grep
 
 3. **MANDATORY: Template-first workflow** — Copy template MUST execute before fill sections. Skipping copy and writing content directly is FORBIDDEN.
 
+4. **MANDATORY: Output filename pattern** — Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md`. Omitting feature_id or using alternative naming is FORBIDDEN.
+
 ## Step 1: Read Inputs
 
 > **Conditional Execution**: If `index_only` = `true`, **skip Steps 1-4** and jump directly to Step 5 to generate INDEX.md.
@@ -39,6 +41,9 @@ tools: Read, Write, Glob, Grep
 - `skip_confirmation` (optional, boolean): When `true`, skip Checkpoint A user confirmation (used in batch dispatch mode)
 - `skip_index_generation` (optional, boolean): When `true`, skip Step 5 INDEX.md generation (INDEX.md will be generated by orchestrator after all workers complete)
 - `index_only` (optional, boolean): When `true`, skip Steps 1-4 and ONLY execute Step 5 (INDEX.md generation). Used after all platform workers complete.
+- `task_id` (optional, string): Task identifier in DISPATCH-PROGRESS.json. Used for status tracking.
+- `dispatch_progress_file` (optional, string): Path to DISPATCH-PROGRESS.json. If provided, worker updates its own task status on completion.
+- `update_progress_script` (optional, string): Path to update-progress.js script.
 
 Read in order:
 
@@ -100,6 +105,30 @@ Mark each function's screens/widgets as:
 
 For each function (or logical group of closely related functions = one module):
 
+### Output File Naming Convention
+
+**MANDATORY**: The design document file MUST be named using this exact pattern:
+
+```
+{feature_id}-{feature_name}-design.md
+```
+
+Examples:
+- `F-M01-05-操作日志-design.md` ✅
+- `F-M02-01-顾客档案管理-design.md` ✅
+- `member-level-change-history-design.md` ❌ (missing feature_id prefix)
+- `customer-profile-design.md` ❌ (missing feature_id prefix)
+
+Where:
+- `feature_id`: The exact feature ID from dispatch context (e.g., `F-M01-05`, `F-M02-01`)
+- `feature_name`: The exact feature name from dispatch context (e.g., `操作日志`, `顾客档案管理`)
+
+> ⚠️ **FORBIDDEN**: 
+> - Using any filename format other than `{feature_id}-{feature_name}-design.md`
+> - Omitting the feature_id prefix
+> - Translating or paraphrasing the feature_name (must use the exact name from context)
+> - Using function/sub-feature names instead of the main feature_name
+
 ### 4.1 Read Template
 
 Read `SD-MOBILE-TEMPLATE.md` for document structure.
@@ -228,7 +257,24 @@ Concerns/Trade-offs:
 4. Are all API calls from API Contract covered?
 5. Are platform-specific features (permissions, native integration) properly handled?
 
-## Step 7: Task Completion Report
+## Step 7: Update Task Status (if dispatch_progress_file provided)
+
+> **Conditional Execution**: Only execute this step if `dispatch_progress_file` and `task_id` parameters are provided in the dispatch context.
+
+Update the task status in DISPATCH-PROGRESS.json to mark this task as completed:
+
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status completed
+```
+
+If the design document generation failed at any step, update with status `failed` instead:
+```
+node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status failed
+```
+
+> ⚠️ **IMPORTANT**: This step MUST be the last action before returning the completion report. Do NOT skip this step in batch dispatch mode.
+
+## Step 8: Task Completion Report
 
 After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
 
@@ -281,6 +327,7 @@ After completing all steps, output a structured completion report for the System
 | **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
 | **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy (e.g., hide button, show placeholder) for when that Feature is not yet implemented. |
 | **Mermaid for All Diagrams** | ALL screen trees, navigation flows, interaction sequences, and state diagrams MUST use Mermaid syntax (`graph TB`, `sequenceDiagram`, `flowchart`). Plain text ASCII diagrams are FORBIDDEN for these sections. |
+| **Output Filename Pattern** | Output filename MUST follow pattern: `{feature_id}-{feature_name}-design.md` |
 
 # Checklist
 
@@ -297,6 +344,7 @@ After completing all steps, output a structured completion report for the System
 - [ ] App lifecycle handling documented
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
+- [ ] Output file named as `{feature_id}-{feature_name}-design.md`
 - [ ] **Checkpoint A passed**: function extraction confirmed (or skipped via skip_confirmation)
 - [ ] **No TODO/FIXME placeholders** — all screens and methods have complete pseudocode
 - [ ] **API routes match API Contract exactly** — verified route-by-route

package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.md

@@ -130,7 +130,7 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
 4. Compute batch plan (batch size = 6)
 5. For each batch:
    a. Use **Agent tool** to create `speccrew-task-worker` agents for ALL tasks in the batch **SIMULTANEOUSLY**
-   b. Each Worker receives: `skill_path` (platform-specific skill), `task_id`, `feature_id`, `feature_name`, `platform_id`, `feature_spec_path`, `api_contract_path`, `techs_knowledge_paths`, `framework_decisions`, `output_base_path`, `skip_confirmation: true`, `skip_index_generation: true`
+   b. Each Worker receives: `skill_path` (platform-specific skill), `task_id`, `feature_id`, `feature_name`, `platform_id`, `feature_spec_path`, `api_contract_path`, `techs_knowledge_paths`, `framework_decisions`, `output_base_path`, `skip_confirmation: true`, `skip_index_generation: true`, `dispatch_progress_file`, `update_progress_script`
    c. **Wait** for ALL Workers in the batch to complete
    d. Update DISPATCH-PROGRESS.json for each completed Worker
    e. Log batch progress
@@ -142,6 +142,11 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
 **Batch Dispatch Context Parameters**: When dispatching Workers in batch mode, the following parameters MUST be included in each Worker's context:
 - `skip_confirmation: true` — Workers skip Checkpoint A user confirmation (not feasible in batch mode)
 - `skip_index_generation: true` — Workers skip Step 5 INDEX.md generation (INDEX.md will be generated by orchestrator after all workers complete)
+- `dispatch_progress_file` — Path to DISPATCH-PROGRESS.json, enables Worker to self-update its task status on completion
+- `update_progress_script` — Path to update-progress.js script, used by Worker to execute status updates
+- `task_id` — Task identifier in DISPATCH-PROGRESS.json (already part of dispatch context, listed here for completeness)
+
+> **Worker Self-Update**: When `dispatch_progress_file` and `task_id` are provided, the Worker is responsible for updating its own task status in DISPATCH-PROGRESS.json upon completion (Step 7 of platform skills). The orchestrator's P5-B4-POST block serves as a fallback, but the Worker self-update is the primary mechanism.
 
 ### Phase 5.5: INDEX.md Generation (WORKER-DISPATCH)
 
@@ -159,6 +164,9 @@ After ALL Feature×Platform workers complete successfully, dispatch ONE worker p
   - `completed_documents`: ${platform.completed_documents}
   - `techs_knowledge_dir`: ${techs_knowledge_dir}
   - `workspace_path`: ${workspace_path}
+  - `task_id`: idx-${platform.id}
+  - `dispatch_progress_file`: ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json
+  - `update_progress_script`: ${update_progress_script}
 
 **FORBIDDEN**: Orchestrator generating INDEX.md directly. INDEX.md MUST be generated by worker.
 

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

@@ -391,7 +391,9 @@
                 framework_decisions: ${framework_result.decisions},
                 output_base_path: ${iterations_dir}/${current_iteration}/03.system-design,
                 skip_confirmation: true,
-                skip_index_generation: true
+                skip_index_generation: true,
+                dispatch_progress_file: ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json,
+                update_progress_script: ${update_progress_script}
               </field>
               <field name="output" var="worker_result_${task.id}"/>
             </block>
@@ -449,6 +451,9 @@
           completed_documents: ${platform.completed_documents}
           techs_knowledge_dir: ${techs_knowledge_dir}
           workspace_path: ${workspace_path}
+          task_id: idx-${platform.id}
+          dispatch_progress_file: ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json
+          update_progress_script: ${update_progress_script}
         </field>
       </block>
     </block>

package/package.json

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