speccrew 0.7.59 → 0.7.60

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,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.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.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 |
@@ -800,13 +800,13 @@ All workers execute simultaneously to maximize efficiency.
 > 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 +1096,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

@@ -30,12 +30,15 @@ tools: Read, Write, Glob, Grep
 
 ## 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.
 
 Read in order:
 
@@ -166,7 +169,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:
 

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

@@ -30,12 +30,15 @@ tools: Read, Write, Glob, Grep
 
 ## 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.
 
 Read in order:
 
@@ -149,7 +152,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:
 

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

@@ -30,12 +30,15 @@ tools: Read, Write, Glob, Grep
 
 ## 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.
 
 Read in order:
 
@@ -147,7 +150,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:
 

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

@@ -135,7 +135,7 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
    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.
 
@@ -143,20 +143,24 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
 - `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)
+### Phase 5.5: INDEX.md Generation (WORKER-DISPATCH)
 
-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.
+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.
 
-**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
+**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}
 
-**FORBIDDEN**: Dispatching a worker for INDEX.md generation. INDEX.md is a summary/aggregation file that the orchestrator creates by reading completed worker outputs.
+**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 +193,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

@@ -426,30 +426,33 @@
     <!-- 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}
+        </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.60",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {