speccrew 0.7.59 → 0.7.61

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

@@ -38,8 +38,8 @@ Phase 5: Dispatch Per-Platform Skills
   ├── Single Feature + Single Platform → Direct skill invocation
   └── Multi-Feature or Multi-Platform → Worker dispatch (batch of 6, skip_confirmation + skip_index_generation)
         ↓
-Phase 5.5: Generate Platform INDEX.md (AGENT-OWNED)
-  └── Orchestrator generates INDEX.md per platform after all workers complete
+Phase 5.5: Generate Platform INDEX.md (WORKER-DISPATCH)
+  └── Dispatch worker per platform with index_only=true to generate INDEX.md
         ↓
 Phase 6: Joint Confirmation (HARD STOP)
   └── Present all designs → User confirms → Finalize stage
@@ -62,7 +62,7 @@ This agent is an **orchestrator/dispatcher**. For system design execution (Phase
 This agent MAY directly create/modify ONLY the following files:
 - ✅ `DISPATCH-PROGRESS.json` (via update-progress.js script only)
 - ✅ `.checkpoints.json` (via update-progress.js script only)
-- ✅ `INDEX.md` per platform directory (AGENT-OWNED — generated by orchestrator after all workers complete, NOT by workers in batch mode)
+- ✅ `INDEX.md` per platform directory (generated by worker dispatched with `index_only: true` after all Feature×Platform workers complete)
 - ✅ Progress summary messages to user
 
 > Note: `framework-evaluation.md` is generated **ONLY** by the `speccrew-sd-framework-evaluate` skill.
@@ -78,7 +78,7 @@ This agent MAY directly create/modify ONLY the following files:
 3. ❌ DO NOT invoke `speccrew-sd-mobile` skill directly
 4. ❌ DO NOT invoke `speccrew-sd-desktop` skill directly
 5. ❌ DO NOT generate `*-design.md` files yourself
-6. ❌ DO NOT let individual workers generate platform `INDEX.md` in batch mode — orchestrator generates INDEX.md in Phase 5.5 (AGENT-OWNED)
+6. ❌ DO NOT generate INDEX.md directly — MUST dispatch worker with `index_only: true` in Phase 5.5 (WORKER-DISPATCH)
 7. ❌ DO NOT create design document content as fallback if worker fails
 
 ### Violation Recovery
@@ -133,7 +133,8 @@ 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.5 | AGENT-OWNED-INDEX | After all workers complete, orchestrator generates INDEX.md per platform. Workers MUST NOT generate INDEX.md 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 |
 | ALL | SCRIPT ENFORCEMENT | All .checkpoints.json and WORKFLOW-PROGRESS.json updates via update-progress.js script. Manual JSON creation FORBIDDEN |
@@ -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,17 +799,17 @@ 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
-> 8. After ALL workers complete, generate INDEX.md for each platform directory (AGENT-OWNED task — see Phase 5.5 in orchestration SKILL.md)
+> 8. After ALL workers complete, dispatch ONE worker per platform with `index_only: true` to generate INDEX.md (WORKER-DISPATCH — see Phase 5.5 in orchestration SKILL.md)
 > **FORBIDDEN**:
 > - ❌ DO NOT group multiple features into one Worker
 > - ❌ DO NOT use Skill tool to invoke platform skills (when Features ≥ 2 OR Platforms ≥ 2)
 > - ❌ DO NOT dispatch Workers sequentially — ALL in same batch must be simultaneous
 > - ❌ DO NOT generate *-design.md files yourself as fallback
-> - ❌ DO NOT let individual workers generate INDEX.md in batch mode — set `skip_index_generation: true`; orchestrator generates INDEX.md after all workers complete
+> - ❌ DO NOT let individual workers generate INDEX.md in batch mode — set `skip_index_generation: true`; INDEX.md is generated in Phase 5.5 by separate worker with `index_only: true`
 
 ### 5.5 Update DISPATCH-PROGRESS.json
 
@@ -1096,7 +1099,7 @@ Otherwise
 - DO NOT create or manually edit DISPATCH-PROGRESS.json, .checkpoints.json, or WORKFLOW-PROGRESS.json — use update-progress.js script only
 - DO NOT update WORKFLOW-PROGRESS.json status to "confirmed" before joint user confirmation in Phase 6
 - DO NOT proceed to the next batch or Phase 6 if any Phase 5 batch worker failure rate > 50% — follow the Batch Failure recovery flow in Phase 5.6
-- DO NOT let individual workers generate INDEX.md in batch mode — set `skip_index_generation: true` in worker context; orchestrator generates INDEX.md in Phase 5.5 (AGENT-OWNED)
+- DO NOT generate INDEX.md directly — set `skip_index_generation: true` in Feature×Platform worker context; dispatch separate worker with `index_only: true` in Phase 5.5 (WORKER-DISPATCH)
 - DO NOT skip backward compatibility checks for old format Feature Specs
 - DO NOT automatically transition to or invoke the next stage agent — user starts next stage in a new conversation
 

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

@@ -28,14 +28,22 @@ 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.
+
 **Input Parameters** (from agent context):
 - `feature_id` (optional): Feature identifier, e.g., `F-CRM-01`. If provided, use new naming format.
 - `feature_name`: Feature name, e.g., `customer-list`.
 - `platform_id`: Target platform, e.g., `backend-spring`, `backend-nestjs`.
 - `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 +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.
@@ -166,7 +198,9 @@ Verify the completed design document:
 
 ## Step 5: Generate Platform INDEX.md
 
-> **Conditional Execution**: If `skip_index_generation` = `true`, **skip this entire Step 5** and proceed to completion. INDEX.md will be generated by the orchestrator after all platform workers complete.
+> **Conditional Execution**:
+> - If `skip_index_generation` = `true`, **skip this entire Step 5**.
+> - If `index_only` = `true`, this step is the ONLY step to execute (Steps 1-4 are skipped).
 
 After all module designs are complete:
 
@@ -231,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:
 
@@ -300,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
 
@@ -329,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,14 +28,22 @@ 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.
+
 **Input Parameters** (from agent context):
 - `feature_id` (optional): Feature identifier, e.g., `F-CRM-01`. If provided, use new naming format.
 - `feature_name`: Feature name, e.g., `customer-list`.
 - `platform_id`: Target platform, e.g., `frontend-vue`, `frontend-react`.
 - `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:
 
@@ -98,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.
@@ -149,7 +181,9 @@ Verify the completed design document:
 
 ## Step 5: Generate Platform INDEX.md
 
-> **Conditional Execution**: If `skip_index_generation` = `true`, **skip this entire Step 5** and proceed to completion. INDEX.md will be generated by the orchestrator after all platform workers complete.
+> **Conditional Execution**:
+> - If `skip_index_generation` = `true`, **skip this entire Step 5**.
+> - If `index_only` = `true`, this step is the ONLY step to execute (Steps 1-4 are skipped).
 
 After all module designs are complete:
 
@@ -229,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:
 
@@ -281,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
 
@@ -294,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,14 +28,22 @@ 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.
+
 **Input Parameters** (from agent context):
 - `feature_id` (optional): Feature identifier, e.g., `F-CRM-01`.
 - `feature_name`: Feature name, e.g., `customer-list`.
 - `platform_id`: Target platform, e.g., `mobile-uniapp`, `mobile-flutter`.
 - `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:
 
@@ -97,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.
@@ -147,7 +179,9 @@ Verify the completed design document:
 
 ## Step 5: Generate Platform INDEX.md
 
-> **Conditional Execution**: If `skip_index_generation` = `true`, **skip this entire Step 5** and proceed to completion. INDEX.md will be generated by the orchestrator after all platform workers complete.
+> **Conditional Execution**:
+> - If `skip_index_generation` = `true`, **skip this entire Step 5**.
+> - If `index_only` = `true`, this step is the ONLY step to execute (Steps 1-4 are skipped).
 
 After all module designs are complete:
 
@@ -223,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:
 
@@ -276,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
 
@@ -292,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,33 +130,45 @@ 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
 6. After all batches complete, read final progress summary
-7. Generate INDEX.md for each platform (AGENT-OWNED, see Phase 5.5)
+7. Dispatch worker per platform with `index_only: true` to generate INDEX.md (see Phase 5.5)
 
 **CRITICAL**: Each Worker handles exactly ONE feature on ONE platform. DO NOT group multiple features or platforms into a single Worker.
 
 **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)
-
-### Phase 5.5: INDEX.md Generation (AGENT-OWNED)
-
-After ALL Feature×Platform workers complete successfully, the orchestrator generates INDEX.md for each platform directory. This is an AGENT-OWNED task — the orchestrator generates INDEX.md directly, NOT by dispatching a worker.
-
-**Steps per platform**:
-1. Read INDEX-TEMPLATE.md from techs knowledge templates
-2. Copy template to `{output_dir}/{platform_id}/INDEX.md`
-3. Fill sections using `search_replace` with actual content from:
-   - Tech stack summary from techs knowledge
-   - Module list table from completed design documents
-   - Shared design decisions from architecture knowledge
-4. Verify all placeholders are replaced
-
-**FORBIDDEN**: Dispatching a worker for INDEX.md generation. INDEX.md is a summary/aggregation file that the orchestrator creates by reading completed worker outputs.
+- `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)
+
+After ALL Feature×Platform workers complete successfully, dispatch ONE worker per platform to generate INDEX.md. Each worker receives `index_only: true` and `skip_index_generation: false`, executing ONLY Step 5 of the platform skill.
+
+**Dispatch parameters per platform**:
+- `agent`: speccrew-task-worker
+- `skill`: speccrew-sd-${platform.type}
+- `skill_path`: ${ide_skills_dir}/speccrew-sd-${platform.type}/SKILL.md
+- `context`:
+  - `index_only: true`
+  - `skip_index_generation: false`
+  - `platform_id`: ${platform.id}
+  - `output_dir`: ${iterations_dir}/${current_iteration}/03.system-design/${platform.id}
+  - `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.
 
 **Example** (5 features × 3 platforms = 15 workers, 3 batches of 6/6/3):
 - Batch 1: Workers 1-6 (parallel)
@@ -189,7 +201,7 @@ DO NOT proceed past these checkpoints without explicit user confirmation.
 - **DO NOT generate framework-evaluation.md yourself** — Only workers generate it
 - **DO NOT create scripts for batch analysis** — Workers handle this via their own skill
 - **DO NOT fallback to inline execution if worker fails** — ABORT instead
-- **DO NOT let individual workers generate INDEX.md in batch mode** — `skip_index_generation: true` must be set; orchestrator generates INDEX.md after all workers complete
+- **DO NOT let individual workers generate INDEX.md in batch mode** — `skip_index_generation: true` must be set; INDEX.md is generated in Phase 5.5 by separate worker with `index_only: true`
 - **DO NOT skip reading workflow.agentflow.xml** — XML is the execution authority
 - **DO NOT generate DESIGN-OVERVIEW.md yourself** — Dispatch speccrew-task-worker with speccrew-sd-design-overview-generate skill
 - **DO NOT use Skill tool for Phase 4 design overview generation** — Skill tool executes inline, Agent tool creates a 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>
@@ -426,30 +428,36 @@
     <!-- batch-update is available via: node update-progress.js batch-update --file <progress.json> --tasks-file <tasks.json> -->
     <!-- Use when orchestrator needs to batch-update multiple task statuses at once -->
 
-    <!-- Phase 5.5: Generate Platform INDEX.md (AGENT-OWNED) -->
-    <block type="rule" id="P5-IDX-R1" level="mandatory" desc="INDEX.md Generation - Agent Owned">
+    <!-- Phase 5.5: Generate Platform INDEX.md (WORKER-DISPATCH) -->
+    <block type="rule" id="P5-IDX-R1" level="mandatory" desc="INDEX.md Generation via Worker Dispatch">
       <field name="text">
-        After all workers complete, the orchestrator generates INDEX.md for each platform.
-        Steps per platform:
-        1. Read INDEX-TEMPLATE.md from techs knowledge templates
-        2. Copy template to {output_dir}/{platform_id}/INDEX.md
-        3. Fill sections using search_replace with actual content from:
-           - Tech stack summary from techs knowledge
-           - Module list table from completed design documents
-           - Shared design decisions from architecture knowledge
-        4. Verify all placeholders are replaced
-        FORBIDDEN: Dispatching a worker for INDEX.md generation.
+        After ALL Feature×Platform workers complete, dispatch ONE worker per platform to generate INDEX.md.
+        - Each worker receives index_only=true, skip_index_generation=false
+        - Worker executes ONLY Step 5 of the platform skill
+        - FORBIDDEN: Orchestrator generating INDEX.md directly (must use worker)
       </field>
     </block>
     <block type="loop" id="P5-IDX-L1" over="${platforms}" as="platform">
-      <block type="task" id="P5-IDX-B1" action="write-file" status="pending"
-             desc="Generate INDEX.md for ${platform.id}">
-        <field name="template_source">${techs_knowledge_dir}/${platform.id}/templates/INDEX-TEMPLATE.md</field>
-        <field name="output">${iterations_dir}/${current_iteration}/03.system-design/${platform.id}/INDEX.md</field>
-        <field name="fill_method">search_replace per section</field>
-        <field name="module_list_source">${platform.completed_documents}</field>
+      <block type="task" id="P5-IDX-DISPATCH" action="dispatch-to-worker" status="pending"
+             desc="Dispatch worker to generate INDEX.md for ${platform.id}">
+        <field name="agent">speccrew-task-worker</field>
+        <field name="skill">speccrew-sd-${platform.type}</field>
+        <field name="skill_path">${ide_skills_dir}/speccrew-sd-${platform.type}/SKILL.md</field>
+        <field name="context">
+          index_only: true
+          skip_index_generation: false
+          platform_id: ${platform.id}
+          output_dir: ${iterations_dir}/${current_iteration}/03.system-design/${platform.id}
+          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>
+    <block type="gateway" id="P5-IDX-GW1" mode="wait" desc="Wait for all INDEX.md workers to complete"/>
 
     <!-- Step 5.5: Read final dispatch progress -->
     <block type="task" id="P5-B5" action="run-script" status="pending"

package/package.json

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