speccrew 0.1.10 → 0.1.12

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

@@ -141,7 +141,9 @@ When there is only one Feature Spec and one platform, call skill directly with p
 
 ### 5.3 Parallel Execution (Feature × Platform)
 
-When multiple Feature Specs and/or multiple platforms exist, create a worker matrix of **Feature × Platform** and invoke `speccrew-task-worker` agents in parallel:
+> **IMPORTANT**: Use the **Skill tool** (not the Agent tool) to invoke each design skill.
+
+When multiple Feature Specs and/or multiple platforms exist, create a matrix of **Feature × Platform** and use the **Skill tool** to invoke per-platform design skills in parallel:
 
 **Worker Matrix:**
 
@@ -160,16 +162,16 @@ Each worker receives:
   - `framework_decisions`: Framework decisions from Phase 3
   - `output_base_path`: Path to `03.system-design/` directory
 
-**Parallel execution example** (2 features × 3 platforms = 6 workers):
-- Worker 1: speccrew-sd-frontend for Feature A on web-vue → 03.system-design/web-vue/
-- Worker 2: speccrew-sd-backend for Feature A on backend-spring → 03.system-design/backend-spring/
-- Worker 3: speccrew-sd-mobile for Feature A on mobile-uniapp → 03.system-design/mobile-uniapp/
-- Worker 4: speccrew-sd-frontend for Feature B on web-vue → 03.system-design/web-vue/
-- Worker 5: speccrew-sd-backend for Feature B on backend-spring → 03.system-design/backend-spring/
-- Worker 6: speccrew-sd-mobile for Feature B on mobile-uniapp → 03.system-design/mobile-uniapp/
+**Parallel execution example** (2 features × 3 platforms = 6 skill invocations):
+- Skill 1: speccrew-sd-frontend for Feature A on web-vue → 03.system-design/web-vue/
+- Skill 2: speccrew-sd-backend for Feature A on backend-spring → 03.system-design/backend-spring/
+- Skill 3: speccrew-sd-mobile for Feature A on mobile-uniapp → 03.system-design/mobile-uniapp/
+- Skill 4: speccrew-sd-frontend for Feature B on web-vue → 03.system-design/web-vue/
+- Skill 5: speccrew-sd-backend for Feature B on backend-spring → 03.system-design/backend-spring/
+- Skill 6: speccrew-sd-mobile for Feature B on mobile-uniapp → 03.system-design/mobile-uniapp/
 
-All workers execute simultaneously to maximize efficiency.
-Wait for all workers to complete before proceeding to Phase 6.
+All skills execute simultaneously to maximize efficiency.
+Wait for all skills to complete before proceeding to Phase 6.
 
 ## Phase 6: Joint Confirmation
 

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

@@ -1,9 +1,7 @@
-# speccrew-system-developer
-
-**Description**: SpecCrew System Developer. Reads system design blueprints and coordinates cross-platform development task dispatch. Loads techs knowledge, verifies environment readiness, dispatches per-platform dev skills, performs integration checks, and delivers development completion reports. Supports web, mobile, desktop, and backend platforms.
-
-**Tools**: Bash, Edit, Write, Glob, Grep, Read, WebFetch, WebSearch
-
+---
+name: speccrew-system-developer
+description: SpecCrew System Developer. Reads system design blueprints and coordinates cross-platform development task dispatch. Loads techs knowledge, verifies environment readiness, dispatches per-platform dev skills, performs integration checks, and delivers development completion reports. Supports web, mobile, desktop, and backend platforms.
+tools: Read, Write, Glob, Grep, Bash
 ---
 
 # Role Positioning
@@ -97,50 +95,83 @@ If any pre-check fails:
 3. Wait for user to resolve before proceeding
 4. Re-run pre-check after user confirms resolution
 
-## Step 4: Dispatch Per-Platform Dev Skills
+## Step 4: Dispatch Per-Module Dev Skills
+
+> **IMPORTANT**: Use the **Skill tool** (not the Agent tool) to invoke each dev skill.
 
 ### 4.1 Determine Skill for Each Platform
 
 Platform type mapping:
 
 | Platform prefix | Skill to invoke |
-|-----------------|-----------------|
+|-----------------|------------------|
 | `web-*` | `speccrew-dev-frontend` |
 | `backend-*` | `speccrew-dev-backend` |
 | `mobile-*` | `speccrew-dev-mobile` |
 | `desktop-*` | `speccrew-dev-desktop` |
 
-### 4.2 Dispatch Parameters
-
-For each platform, pass the following context:
-- `platform_id`: Platform identifier from design overview
-- `iteration_path`: Path to current iteration directory
-- `design_doc_paths`: List of module design documents for this platform
-- `techs_knowledge_paths`: Relevant techs knowledge file paths
-
-### 4.3 Multi-Platform Parallel Execution
-
-When multiple platforms are identified in DESIGN-OVERVIEW.md, invoke `speccrew-task-worker` agents in parallel:
-- Each worker handles one platform's development end-to-end
-- Each worker receives:
-  - `skill_name`: Per-platform dev skill based on platform type:
-    - `web-*` → `speccrew-dev-frontend`
-    - `backend-*` → `speccrew-dev-backend`
-    - `mobile-*` → `speccrew-dev-mobile`
-    - `desktop-*` → `speccrew-dev-desktop`
-  - `context`:
-    - `platform_id`: Platform identifier from design overview
-    - `iteration_path`: Path to current iteration directory
-    - `design_doc_paths`: List of module design documents for this platform (from `03.system-design/{platform_id}/`)
-    - `api_contract_path`: Path to API Contract document
-    - `techs_knowledge_paths`: Relevant techs knowledge file paths for this platform
-- Parallel execution pattern:
-  - Worker 1: speccrew-dev-frontend for web-vue → implements frontend code
-  - Worker 2: speccrew-dev-backend for backend-springboot → implements backend code
-  - Worker N: platform-specific skill for {platform_id} → implements platform code
-- All workers execute simultaneously to maximize efficiency
-- Track all dispatched workers and their completion status
-- Wait for all workers to complete before proceeding to Step 5 (Integration Check)
+### 4.2 Build Module Task List
+
+From Step 1.3, flatten all module design documents into a unified task list:
+
+```
+task_list = []
+for each platform_id:
+  read INDEX.md → get module design file list
+  for each module_design_doc:
+    task_list.append({
+      platform_id,
+      skill_name: determined by platform prefix (see 4.1),
+      module_design_path: 03.system-design/{platform_id}/{module}-design.md,
+      techs_knowledge_paths: relevant techs knowledge for this platform,
+      api_contract_path: API Contract path,
+      iteration_path: current iteration directory
+    })
+```
+
+**Example** (3 platforms × ~11 modules each = ~33 tasks):
+- Task 1: `speccrew-dev-backend` for `backend-spring/crm-design.md`
+- Task 2: `speccrew-dev-backend` for `backend-spring/member-design.md`
+- ...
+- Task 12: `speccrew-dev-frontend` for `web-vue/crm-design.md`
+- ...
+- Task 23: `speccrew-dev-mobile` for `mobile-uniapp/crm-design.md`
+- ...
+
+### 4.3 Parallel Execution with Concurrency Limit
+
+**Max concurrent skill invocations: 10**
+
+Process `task_list` in batches:
+
+```
+MAX_CONCURRENT = 10
+pending = [...task_list]
+completed = []
+
+while pending is not empty:
+  batch = pending.take(min(MAX_CONCURRENT, pending.length))
+  for each task in batch:
+    invoke Skill tool with:
+      - skill_name: task.skill_name
+      - context:
+        - platform_id: task.platform_id
+        - iteration_path: task.iteration_path
+        - design_doc_path: task.module_design_path  (single module design doc)
+        - api_contract_path: task.api_contract_path
+        - techs_knowledge_paths: task.techs_knowledge_paths
+  wait for all batch skills to complete
+  move completed tasks to completed[]
+```
+
+**Dispatch rules:**
+- Each skill invocation handles **one module** on **one platform** (not all modules)
+- Pass `design_doc_path` (singular) pointing to ONE module design document
+- Up to 10 skills execute simultaneously per batch
+- Wait for current batch to complete before starting next batch
+- Track all dispatched skills: completed / failed / blocked
+- If a skill fails, log the failure and continue with remaining tasks
+- Wait for all batches to complete before proceeding to Step 5 (Integration Check)
 
 ## Step 5: Integration Check
 

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

@@ -1,7 +1,7 @@
 ---
 name: speccrew-task-worker
 description: Generic task execution Worker. Invoked in parallel by other Agents with multiple instances, receives context parameters and optional Skill path, executes tasks according to Skill definition if provided, or directly processes the task based on context. Specialized for batch document read/write operations, splitting large tasks into small, context-isolated subtasks for parallel execution.
-tools: Read, Grep, Glob, Write, Bash, Edit
+tools: Read, Grep, Glob, Write, Bash, Edit, WebFetch, WebSearch
 ---
 
 # Role Definition

package/.speccrew/agents/speccrew-test-manager.md

@@ -93,7 +93,7 @@ Design test cases based on loaded knowledge:
 
 After reading `DESIGN-OVERVIEW.md`:
 - **Single Platform**: Invoke Skill directly
-- **Multiple Platforms**: Dispatch via `speccrew-task-worker` agents in parallel
+- **Multiple Platforms**: Use **Skill tool** to invoke per-platform skills in parallel
 
 ### 3.2 Single Platform Execution
 
@@ -107,7 +107,9 @@ Invoke Skill directly with parameters:
 
 ### 3.3 Multi-Platform Parallel Execution
 
-Invoke `speccrew-task-worker` agents in parallel:
+> **IMPORTANT**: Use the **Skill tool** (not the Agent tool) to invoke each test skill.
+
+Use the **Skill tool** to invoke `speccrew-test-case-design` for each platform in parallel:
 - Each worker receives:
   - `skill_name`: `speccrew-test-case-design`
   - `context`:
@@ -163,9 +165,7 @@ Invoke Skill directly:
 
 ### 4.3 Multi-Platform Parallel Execution
 
-Invoke `speccrew-task-worker` agents in parallel:
-- Each worker receives:
-  - `skill_name`: `speccrew-test-code-gen`
+Use the **Skill tool** to invoke `speccrew-test-code-gen` for each platform in parallel:
   - `context`:
     - `test_cases_path`: Path to the platform-specific test cases document
     - `system_design_path`: Path to the platform system design document
@@ -214,9 +214,7 @@ Invoke Skill directly:
 
 ### 5.3 Multi-Platform Parallel Execution
 
-Invoke `speccrew-task-worker` agents in parallel:
-- Each worker receives:
-  - `skill_name`: `speccrew-test-execute`
+Use the **Skill tool** to invoke `speccrew-test-execute` for each platform in parallel:
   - `context`:
     - `test_code_path`: Path to the platform test code directory
     - `platform_id`: Platform identifier
@@ -299,7 +297,7 @@ Provide clear recommendation:
 **Must do:**
 - Execute three phases in strict order: test case design → code generation → test execution
 - Each phase must have a Checkpoint with user confirmation before proceeding
-- Multi-platform scenarios must be dispatched via `speccrew-task-worker` for parallel execution
+- Multi-platform scenarios must use the **Skill tool** to invoke per-platform skills in parallel
 - Test cases must be traceable to Feature Spec requirements
 - Bug reports must reference specific test case IDs
 - Use platform_id from design overview as directory names

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

@@ -26,9 +26,11 @@ tools: Bash, Edit, Write, Glob, Grep, Read
 
 ## Step 1: Read Design Documents
 
+Input: `design_doc_path` — Path to a single module design document (passed by upstream system-developer agent).
+
 Read in order:
 
-1. **Backend Design Documents**: `speccrew-workspace/iterations/{number}-{type}-{name}/03.system-design/{platform_id}/*-design.md`
+1. **Module Design Document**: The `design_doc_path` provided (single module's design)
 2. **Platform INDEX**: `speccrew-workspace/iterations/{number}-{type}-{name}/03.system-design/{platform_id}/INDEX.md`
 3. **API Contract**: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-api-contract.md`
 4. **Techs Knowledge** (from agent context):

package/.speccrew/skills/speccrew-dev-desktop/SKILL.md

@@ -26,12 +26,13 @@ tools: Bash, Edit, Write, Glob, Grep, Read
 
 ## Step 1: Read Design Documents
 
+**Input**: Single module design document path `design_doc_path` (provided by upstream system-developer agent).
+
 Read in order:
 
-1. **INDEX.md**: `speccrew-workspace/iterations/{number}-{type}-{name}/03.system-design/{platform_id}/INDEX.md`
-2. **Module Design Documents**: All `*-design.md` files from same directory
-3. **API Contract**: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-api-contract.md`
-4. **Techs Knowledge** (paths from agent context):
+1. **Module design document**: `design_doc_path` (single module design document)
+2. **API Contract**: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-api-contract.md`
+3. **Techs Knowledge** (paths from agent context):
    - `speccrew-workspace/knowledges/techs/{platform_id}/tech-stack.md`
    - `speccrew-workspace/knowledges/techs/{platform_id}/architecture.md`
    - `speccrew-workspace/knowledges/techs/{platform_id}/conventions-design.md`
@@ -267,11 +268,11 @@ Task Record: speccrew-workspace/iterations/{number}-{type}-{name}/04.development
 
 # Checklist
 
-- [ ] All design documents loaded before implementation
+- [ ] Design document loaded before implementation (single module design_doc_path)
 - [ ] Existing code structure analyzed via Glob/Grep
 - [ ] Task record created with complete checklist
 - [ ] Checkpoint A passed: task extraction confirmed with user
-- [ ] Every design document module covered in task list
+- [ ] All modules in the design document covered in task list
 - [ ] All IPC channels from design implemented
 - [ ] Context isolation enabled for all windows
 - [ ] Preload scripts expose only necessary APIs

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

@@ -26,10 +26,12 @@ tools: Bash, Edit, Write, Glob, Grep, Read
 
 ## Step 1: Read Design Documents
 
+Input: `design_doc_path` — Path to a single module design document (passed by upstream system-developer agent).
+
 Read in order:
 
 1. **Platform INDEX**: `speccrew-workspace/iterations/{number}-{type}-{name}/03.system-design/{platform_id}/INDEX.md`
-2. **Module design documents**: All `*-design.md` files listed in INDEX
+2. **Module Design Document**: The `design_doc_path` provided (single module's design)
 3. **API Contract**: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/*-api-contract.md`
 4. **Task record template**: `speccrew-dev-frontend/templates/TASK-RECORD-TEMPLATE.md`
 
@@ -49,9 +51,9 @@ Read platform-specific techs knowledge:
 
 From design documents, extract ALL implementation items into a task checklist.
 
-### 3.1 Parse Module Designs
+### 3.1 Parse Module Design
 
-For each module design document, identify:
+From the module design document, identify:
 
 | Item Type | Markers | Example |
 |-----------|---------|---------|

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

@@ -26,12 +26,13 @@ tools: Bash, Edit, Write, Glob, Grep, Read
 
 ## Step 1: Read Design Documents
 
+**Input**: Single module design document path `design_doc_path` (provided by upstream system-developer agent).
+
 Read in order:
 
-1. **INDEX.md**: `speccrew-workspace/iterations/{iteration}/03.system-design/{platform_id}/INDEX.md`
-2. **Module design documents**: `speccrew-workspace/iterations/{iteration}/03.system-design/{platform_id}/{module}-design.md`
-3. **API Contract**: `speccrew-workspace/iterations/{iteration}/02.feature-design/{feature-name}-api-contract.md`
-4. **Task record template**: `speccrew-dev-mobile/templates/TASK-RECORD-TEMPLATE.md`
+1. **Module design document**: `design_doc_path` (single module design document)
+2. **API Contract**: `speccrew-workspace/iterations/{iteration}/02.feature-design/{feature-name}-api-contract.md`
+3. **Task record template**: `speccrew-dev-mobile/templates/TASK-RECORD-TEMPLATE.md`
 
 ## Step 2: Read Techs Knowledge
 
@@ -213,7 +214,7 @@ Ready for QA Agent acceptance testing.
 
 # Checklist
 
-- [ ] Design documents loaded (INDEX.md + module designs)
+- [ ] Design document loaded (single module design_doc_path)
 - [ ] Techs knowledge loaded (conventions-dev, architecture, tech-stack)
 - [ ] Task record file created
 - [ ] All design tasks extracted to checklist

package/package.json

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