speccrew 0.2.3 → 0.2.5

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

@@ -25,7 +25,7 @@ Before starting any feature design work:
 
 1. **Read `WORKFLOW-PROGRESS.json` overview**:
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --overview
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --overview
    ```
    - If the file does not exist → Skip to Phase 1 (backward compatibility mode)
 
@@ -40,7 +40,7 @@ Before starting any feature design work:
 
 3. **Update Stage Status**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --stage 02_feature_design --status in_progress
+   node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --stage 02_feature_design --status in_progress
    ```
 
 ### 0.2 Check Resume State (Checkpoint Recovery)
@@ -49,7 +49,7 @@ If resuming from an interrupted session:
 
 1. **Read checkpoints** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/02.feature-design/.checkpoints.json --checkpoints
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/02.feature-design/.checkpoints.json --checkpoints
    ```
    - If the file does not exist → Start from Phase 1 (no previous progress)
 
@@ -79,7 +79,7 @@ If the feature involves multiple frontend platforms:
 
 1. **Read `DISPATCH-PROGRESS.json` summary** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/02.feature-design/DISPATCH-PROGRESS.json --summary
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{iteration-id}/02.feature-design/DISPATCH-PROGRESS.json --summary
    ```
    - If the file does not exist → No dispatch in progress, proceed normally
 
@@ -225,7 +225,7 @@ After user confirms Joint Confirmation:
 
 1. **Update `WORKFLOW-PROGRESS.json`**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --stage 02_feature_design --status confirmed --output "02.feature-design/[feature-name]-feature-spec.md,02.feature-design/[feature-name]-api-contract.md"
+   node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json --stage 02_feature_design --status confirmed --output "02.feature-design/[feature-name]-feature-spec.md,02.feature-design/[feature-name]-api-contract.md"
    ```
 
 2. **Confirm Transition**:

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

@@ -23,7 +23,7 @@ Before starting system design, verify that Feature Design stage is confirmed:
 
 1. **Read WORKFLOW-PROGRESS.json overview**:
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --overview
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --overview
    ```
 
 2. **Validate upstream stage**: Check `stages.02_feature_design.status == "confirmed"` in the output
@@ -34,7 +34,7 @@ Before starting system design, verify that Feature Design stage is confirmed:
    - Read `02_feature_design.outputs` to get Feature Spec and API Contract paths
    - Update stage status:
      ```bash
-     node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status in_progress
+     node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status in_progress
      ```
 
 ### Step 0.2: Check Resume State (断点续传)
@@ -43,7 +43,7 @@ Check if there's existing progress to resume:
 
 1. **Read checkpoints** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --checkpoints
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --checkpoints
    ```
 
 2. **Determine resume point** based on passed checkpoints:
@@ -58,7 +58,7 @@ Check dispatch progress for parallel task execution:
 
 1. **Read dispatch progress summary** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --summary
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --summary
    ```
 
 2. **List task statuses**:
@@ -194,14 +194,14 @@ Before dispatching, create or update dispatch tracking:
 
 1. **Initialize dispatch progress file with task list**:
    ```bash
-   node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --stage 03_system_design --tasks '[{"id":"sd-{platform_id}-{feature_name}","platform":"{platform_id}","feature":"{feature_name}","skill":"speccrew-sd-{type}","status":"pending"}]'
+   node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --stage 03_system_design --tasks '[{"id":"sd-{platform_id}-{feature_name}","platform":"{platform_id}","feature":"{feature_name}","skill":"speccrew-sd-{type}","status":"pending"}]'
    ```
    Or use `--tasks-file` to load from a JSON file.
 
 2. **Check existing progress** (from Step 0.3) — skip `completed` tasks
 3. **Update status** to `in_progress` for tasks being dispatched:
    ```bash
-   node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
+   node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
    ```
 
 ### 5.3 Single Feature Spec + Single Platform
@@ -210,7 +210,7 @@ When there is only one Feature Spec and one platform:
 
 1. **Update task status to `in_progress`**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
+   node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
    ```
 
 2. Call skill directly with parameters:
@@ -226,11 +226,11 @@ When there is only one Feature Spec and one platform:
 3. **Parse Task Completion Report** from skill output:
    - If `Status: SUCCESS`:
      ```bash
-     node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
+     node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
      ```
    - If `Status: FAILED`:
      ```bash
-     node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
+     node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
      ```
 
 ### 5.4 Parallel Execution (Feature × Platform)
@@ -259,7 +259,7 @@ Each worker receives:
 
 **Before dispatch**: Update each task status to `in_progress`:
 ```bash
-node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
+node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
 ```
 
 **Parallel execution example** (2 features × 3 platforms = 6 workers):
@@ -278,11 +278,11 @@ After each worker completes, parse its **Task Completion Report** and update:
 
 - On SUCCESS:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
   ```
 
 Wait for all workers to complete before proceeding to Phase 6.
@@ -302,14 +302,14 @@ After user confirms:
 
 1. **Write checkpoints**:
    ```bash
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint framework_evaluation --passed true
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint design_overview --passed true
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint joint_confirmation --passed true
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint framework_evaluation --passed true
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint design_overview --passed true
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint joint_confirmation --passed true
    ```
 
 2. **Update WORKFLOW-PROGRESS.json**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status confirmed --output "DESIGN-OVERVIEW.md, platform-indexes, module-designs"
+   node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/iterations/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status confirmed --output "DESIGN-OVERVIEW.md, platform-indexes, module-designs"
    ```
 
 3. **Designs become baseline** for Dev phase

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

@@ -13,6 +13,8 @@ You are in the **fourth stage** of the complete engineering closed loop:
 
 Your core task is: based on the System Design (HOW to build), execute and coordinate the actual implementation across platforms, ensuring code delivery and integration quality.
 
+> **CRITICAL CONSTRAINT**: This agent is a **dispatcher/orchestrator ONLY**. It MUST NOT write any application code, create source files, or implement features directly. ALL development work MUST be delegated to `speccrew-task-worker` agents. Violation of this rule invalidates the entire workflow.
+
 # Workflow
 
 ## Step 0: Workflow Progress Management
@@ -23,7 +25,7 @@ Before starting development, verify upstream stage completion:
 
 1. **Read WORKFLOW-PROGRESS.json overview**:
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/WORKFLOW-PROGRESS.json --overview
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/WORKFLOW-PROGRESS.json --overview
    ```
 
 2. **Verify System Design stage status**:
@@ -33,7 +35,7 @@ Before starting development, verify upstream stage completion:
 
 3. **Update Development stage status**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 04_development --status in_progress
+   node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 04_development --status in_progress
    ```
 
 ### Phase 0.2: Check Resume State
@@ -42,7 +44,7 @@ Check for existing checkpoint state to support resume:
 
 1. **Read checkpoints** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --checkpoints
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --checkpoints
    ```
 
 2. **Determine resume point based on passed checkpoints**:
@@ -61,7 +63,7 @@ Check for existing dispatch progress to support module-level retry:
 
 1. **Read dispatch progress summary** (if file exists):
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --summary
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --summary
    ```
 
 2. **Parse the output** to get counts:
@@ -164,7 +166,7 @@ Verify required services are accessible:
 If all pre-checks pass:
 1. **Write checkpoint**:
    ```bash
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint environment_precheck --passed true --description "Runtime environment verification"
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint environment_precheck --passed true --description "Runtime environment verification"
    ```
 
 ### 3.5 Pre-check Failure Handling
@@ -177,6 +179,8 @@ If any pre-check fails:
 
 ## Step 4: Dispatch Per-Module Dev Skills
 
+> ⛔ **NO DIRECT CODING**: System Developer MUST NOT use file creation/editing tools to write application code. Every module implementation MUST be dispatched to a `speccrew-task-worker` agent running a dev skill (speccrew-dev-backend/frontend/mobile/desktop). System Developer's role in this phase is EXCLUSIVELY: task list creation, worker dispatch, progress tracking, and review coordination.
+
 > **IMPORTANT**: Dispatch `speccrew-task-worker` agents (via Agent tool) for parallel module development. Do NOT call dev skills directly — each module MUST run in an independent Worker Agent for progress visibility and error isolation.
 
 ### 4.0 Initialize DISPATCH-PROGRESS.json
@@ -189,7 +193,7 @@ Before dispatching tasks, create or read dispatch progress file:
 
 2. **If not exists — Create fresh dispatch progress**:
    ```bash
-   node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --stage 04_development --tasks-file <tasks_json_path>
+   node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --stage 04_development --tasks-file <tasks_json_path>
    ```
    Where `<tasks_json_path>` contains the task list built from Step 1.3:
    ```json
@@ -206,7 +210,7 @@ Before dispatching tasks, create or read dispatch progress file:
 
 3. **Alternatively, pass tasks JSON directly**:
    ```bash
-   node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --stage 04_development --tasks '[{"id":"dev-web-vue-crm","platform":"web-vue","module":"crm","skill":"speccrew-dev-frontend","status":"pending"}]'
+   node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --stage 04_development --tasks '[{"id":"dev-web-vue-crm","platform":"web-vue","module":"crm","skill":"speccrew-dev-frontend","status":"pending"}]'
    ```
 
 **Task Status Enumeration:**
@@ -276,11 +280,19 @@ for each platform_id:
 **After user confirms**:
 1. **Write checkpoint**:
    ```bash
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint task_list_review --passed true --description "Development task list confirmed by user"
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint task_list_review --passed true --description "Development task list confirmed by user"
    ```
 
 ### 4.3 Dispatch Workers with Concurrency Limit
 
+> **FORBIDDEN ACTIONS for System Developer**:
+> - ❌ Creating source code files (*.java, *.vue, *.ts, *.dart, etc.)
+> - ❌ Writing implementation code in any language
+> - ❌ Directly invoking dev skills (speccrew-dev-backend, etc.) via Skill tool
+> - ❌ Modifying existing application source code
+>
+> **REQUIRED ACTION**: Dispatch `speccrew-task-worker` agents via Agent tool. Each worker independently calls the appropriate dev skill.
+
 **Max concurrent workers: 10**
 
 Process `task_list` using a queue-based concurrency limit model. Each task runs in an independent `speccrew-task-worker` agent:
@@ -297,7 +309,7 @@ while pending is not empty or running is not empty:
     
     // Update task status to "in_progress"
     ```bash
-    node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress
+    node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress
     ```
     
     // Dispatch speccrew-task-worker agent (NOT Skill tool directly)
@@ -323,13 +335,13 @@ while pending is not empty or running is not empty:
     if report.status == "SUCCESS":
       // Mark as in_review pending review verification
       ```bash
-      node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --output "{report.output_files}"
+      node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --output "{report.output_files}"
       ```
       Add task to review_queue for Phase 4.4
     else:
       // Even failed dev workers go to review for diagnosis
       ```bash
-      node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --error "{report.error}"
+      node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --error "{report.error}"
       ```
       Add task to review_queue for Phase 4.4
     
@@ -350,7 +362,7 @@ while pending is not empty or running is not empty:
 After processing a batch of completed workers:
 1. **Read current progress summary**:
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --summary
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --summary
    ```
 2. Present progress summary to user:
    ```
@@ -401,16 +413,16 @@ for each task in review_queue:
   
   if review.verdict == "PASS":
     ```bash
-    node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status completed --output "{review_report_path}"
+    node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status completed --output "{review_report_path}"
     ```
   elif review.verdict == "PARTIAL":
     ```bash
-    node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status partial --output "{review_report_path}" --metadata "{review.redispatch_guidance}"
+    node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status partial --output "{review_report_path}" --metadata "{review.redispatch_guidance}"
     ```
     Add task to redispatch_queue
   else: // FAIL
     ```bash
-    node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "{review.summary}" --error-category VALIDATION_ERROR
+    node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "{review.summary}" --error-category VALIDATION_ERROR
     ```
 ```
 
@@ -420,8 +432,8 @@ After all initial dev + review cycles complete for the current batch:
 
 1. **Query partial/failed tasks:**
    ```bash
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --status partial
-   node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --status failed
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --status partial
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --status failed
    ```
 
 2. **For each partial/failed task, re-dispatch a dev worker with:**
@@ -438,7 +450,7 @@ After all initial dev + review cycles complete for the current batch:
 
 5. **Update counts after each cycle:**
    ```bash
-   node .speccrew/scripts/update-progress.js update-counts --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json
+   node speccrew-workspace/scripts/update-progress.js update-counts --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json
    ```
 
 **Re-dispatch Flow:**
@@ -453,13 +465,13 @@ for each task in redispatch_queue:
   if attempts > 3:
     // Max attempts reached - mark as permanently failed
     ```bash
-    node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "Max re-dispatch attempts (3) exceeded" --metadata "{accumulated_errors}"
+    node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "Max re-dispatch attempts (3) exceeded" --metadata "{accumulated_errors}"
     ```
     continue
   
   // Update attempt count and reset to in_progress
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress --metadata "{attempts: attempts, previous_review: review_report_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress --metadata "{attempts: attempts, previous_review: review_report_path}"
   ```
   
   // Dispatch dev worker with supplemental context
@@ -590,12 +602,12 @@ Assess readiness for test phase:
 
 1. **Update checkpoint**:
    ```bash
-   node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint delivery_report --passed true --description "Final delivery report"
+   node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint delivery_report --passed true --description "Final delivery report"
    ```
 
 2. **Update WORKFLOW-PROGRESS.json**:
    ```bash
-   node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 04_development --status confirmed --output "04.development/{platform_id}/{module}/"
+   node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 04_development --status confirmed --output "04.development/{platform_id}/{module}/"
    ```
 
 3. **Confirm stage transition**: Report to user that development stage is complete and system is ready for testing phase.
@@ -630,3 +642,4 @@ Assess readiness for test phase:
 - Dispatch dev skills for platforms not in design overview
 - Ignore cross-platform integration issues
 - Proceed to test phase with unresolved blockers
+- Write application code directly (System Developer is a **pure orchestrator** — it reads design documents, creates task lists, dispatches workers, tracks progress, and coordinates reviews. It NEVER writes application code directly.)

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

@@ -21,7 +21,7 @@ Your core task is: coordinate three-phase testing workflow (test case design →
 
 **Read `WORKFLOW-PROGRESS.json` overview**:
 ```bash
-node .speccrew/scripts/update-progress.js read --file speccrew-workspace/WORKFLOW-PROGRESS.json --overview
+node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/WORKFLOW-PROGRESS.json --overview
 ```
 
 **Validation Rules:**
@@ -30,14 +30,14 @@ node .speccrew/scripts/update-progress.js read --file speccrew-workspace/WORKFLO
 
 **Update Current Stage**:
 ```bash
-node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 05_system_test --status in_progress
+node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 05_system_test --status in_progress
 ```
 
 ### Step 0.2: Check Resume State (断点续传)
 
 **Read Checkpoints** (if file exists):
 ```bash
-node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --checkpoints
+node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --checkpoints
 ```
 
 **Resume Decision Matrix:**
@@ -58,7 +58,7 @@ node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterati
 
 **Read Dispatch Progress Summary** (if file exists):
 ```bash
-node .speccrew/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --summary
+node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --summary
 ```
 
 **Parse Task Status by Phase:**
@@ -185,7 +185,7 @@ Invoke Skill directly with parameters:
 
 Before dispatching, create dispatch tracking:
 ```bash
-node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --stage 05_system_test --tasks '[{"id":"test-case-{platform_id}","platform":"{platform_id}","phase":"test_case_design","skill":"speccrew-test-case-design","status":"pending"}]'
+node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --stage 05_system_test --tasks '[{"id":"test-case-{platform_id}","platform":"{platform_id}","phase":"test_case_design","skill":"speccrew-test-case-design","status":"pending"}]'
 ```
 Or use `--tasks-file` to load from a JSON file.
 
@@ -213,11 +213,11 @@ Dispatch `speccrew-task-worker` agents for `speccrew-test-case-design` for each
 For each completed worker, parse Task Completion Report and update:
 - On SUCCESS:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status completed --output "{output_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status failed --error "{error_message}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 3.4 Checkpoint A: Test Case Review
@@ -241,7 +241,7 @@ After test case design completes for all platforms:
 **Write Checkpoint File:**
 
 ```bash
-node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_case_coverage --passed true --description "Test case coverage review (Checkpoint A)"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_case_coverage --passed true --description "Test case coverage review (Checkpoint A)"
 ```
 
 **Output Path:**
@@ -274,7 +274,7 @@ Invoke Skill directly:
 
 Append new tasks for test_code_gen phase by reading existing file and adding tasks:
 ```bash
-node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS-test-code-gen.json --stage 05_system_test --tasks '[{"id":"test-code-{platform_id}","platform":"{platform_id}","phase":"test_code_gen","skill":"speccrew-test-code-gen","status":"pending"}]'
+node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS-test-code-gen.json --stage 05_system_test --tasks '[{"id":"test-code-{platform_id}","platform":"{platform_id}","phase":"test_code_gen","skill":"speccrew-test-code-gen","status":"pending"}]'
 ```
 > **Note**: In practice, maintain a single DISPATCH-PROGRESS.json with all phases by merging task arrays.
 
@@ -293,11 +293,11 @@ Dispatch `speccrew-task-worker` agents for `speccrew-test-code-gen` for each pla
 For each completed worker, parse Task Completion Report:
 - On SUCCESS:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status completed --output "{output_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status failed --error "{error_message}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 4.4 Checkpoint B: Code Review
@@ -321,7 +321,7 @@ After test code generation completes for all platforms:
 **Update Checkpoint File:**
 
 ```bash
-node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_code_review --passed true --description "Test code generation review (Checkpoint B)"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_code_review --passed true --description "Test code generation review (Checkpoint B)"
 ```
 
 **Output:**
@@ -354,7 +354,7 @@ Invoke Skill directly:
 
 Append new tasks for test_execution phase:
 ```bash
-node .speccrew/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS-test-exec.json --stage 05_system_test --tasks '[{"id":"test-exec-{platform_id}","platform":"{platform_id}","phase":"test_execution","skill":"speccrew-test-execute","status":"pending"}]'
+node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS-test-exec.json --stage 05_system_test --tasks '[{"id":"test-exec-{platform_id}","platform":"{platform_id}","phase":"test_execution","skill":"speccrew-test-execute","status":"pending"}]'
 ```
 > **Note**: In practice, maintain a single DISPATCH-PROGRESS.json with all phases by merging task arrays.
 
@@ -372,11 +372,11 @@ Dispatch `speccrew-task-worker` agents for `speccrew-test-execute` for each plat
 For each completed worker, parse Task Completion Report:
 - On SUCCESS:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-exec-{platform_id} --status completed --output "{output_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-exec-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  node .speccrew/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-exec-{platform_id} --status failed --error "{error_message}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id test-exec-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 5.4 Deviation Detection
@@ -441,13 +441,13 @@ Provide clear recommendation:
 **Update Checkpoint File:**
 
 ```bash
-node .speccrew/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_execution_report --passed true --description "Test execution final report"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json --stage 05_system_test --checkpoint test_execution_report --passed true --description "Test execution final report"
 ```
 
 **Update Workflow Progress:**
 
 ```bash
-node .speccrew/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 05_system_test --status confirmed --output "05.system-test/cases/,05.system-test/code/,05.system-test/reports/,05.system-test/bugs/"
+node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 05_system_test --status confirmed --output "05.system-test/cases/,05.system-test/code/,05.system-test/reports/,05.system-test/bugs/"
 ```
 
 > **Note**: `current_stage` does not advance — 05_system_test is the final stage of the pipeline.

package/lib/commands/init.js

@@ -144,12 +144,6 @@ function createWorkspaceStructure(workspaceDir) {
 function copyWorkspaceTemplate(templateDir, workspaceDir) {
   if (!fs.existsSync(templateDir)) return { copied: 0, skipped: 0 };
   
-  const docsSourceDir = path.join(templateDir, 'docs');
-  const docsDestDir = path.join(workspaceDir, 'docs');
-  
-  if (!fs.existsSync(docsSourceDir)) return { copied: 0, skipped: 0 };
-  
-  fs.mkdirSync(docsDestDir, { recursive: true });
   let copied = 0, skipped = 0;
   
   function copyIfNotExists(src, dest) {
@@ -172,7 +166,17 @@ function copyWorkspaceTemplate(templateDir, workspaceDir) {
     }
   }
   
-  copyIfNotExists(docsSourceDir, docsDestDir);
+  // 遍历 workspace-template 下的所有一级子目录并复制
+  const entries = fs.readdirSync(templateDir, { withFileTypes: true });
+  for (const entry of entries) {
+    if (entry.isDirectory()) {
+      const srcSubDir = path.join(templateDir, entry.name);
+      const destSubDir = path.join(workspaceDir, entry.name);
+      fs.mkdirSync(destSubDir, { recursive: true });
+      copyIfNotExists(srcSubDir, destSubDir);
+    }
+  }
+  
   return { copied, skipped };
 }
 

package/lib/commands/update.js

@@ -453,13 +453,26 @@ function run() {
       totalStats.extraDirs.push(...skillStats.extraDirs);
     }
     
-    // 更新 workspace docs
-    const srcDocsDir = path.join(workspaceTemplatePath, 'docs');
-    const destDocsDir = path.join(projectRoot, 'speccrew-workspace', 'docs');
-    const docsStats = { updated: 0, added: 0 };
-    updateWorkspaceDocs(srcDocsDir, destDocsDir, docsStats);
-    totalStats.workspaceDocs.updated = docsStats.updated;
-    totalStats.workspaceDocs.added = docsStats.added;
+    // 更新 workspace 文件（docs, scripts 等所有子目录）
+    const destWorkspaceDir = path.join(projectRoot, 'speccrew-workspace');
+    const workspaceStats = { updated: 0, added: 0 };
+    
+    // 遍历 workspace-template 下的所有一级子目录并同步
+    if (fs.existsSync(workspaceTemplatePath)) {
+      const templateEntries = fs.readdirSync(workspaceTemplatePath, { withFileTypes: true });
+      for (const entry of templateEntries) {
+        if (entry.isDirectory()) {
+          const srcSubDir = path.join(workspaceTemplatePath, entry.name);
+          const destSubDir = path.join(destWorkspaceDir, entry.name);
+          const subStats = { updated: 0, added: 0 };
+          updateWorkspaceDocs(srcSubDir, destSubDir, subStats);
+          workspaceStats.updated += subStats.updated;
+          workspaceStats.added += subStats.added;
+        }
+      }
+    }
+    totalStats.workspaceDocs.updated = workspaceStats.updated;
+    totalStats.workspaceDocs.added = workspaceStats.added;
     
     // 更新 npm 包文档 (GETTING-STARTED*.md and README*.md)
     const packageRoot = getPackageRoot();
@@ -483,7 +496,8 @@ function run() {
     
     console.log(`Agents: ${totalStats.agents.updated} updated, ${totalStats.agents.added} added`);
     console.log(`Skills: ${totalStats.skills.updated} updated, ${totalStats.skills.added} added`);
-    console.log(`Docs: ${totalStats.packageDocs.updated + totalStats.workspaceDocs.updated} updated, ${totalStats.packageDocs.added + totalStats.workspaceDocs.added} added`);
+    console.log(`Workspace: ${totalStats.workspaceDocs.updated} updated, ${totalStats.workspaceDocs.added} added`);
+    console.log(`Docs: ${totalStats.packageDocs.updated} updated, ${totalStats.packageDocs.added} added`);
     
     // 输出警告
     const allExtras = [...new Set([...totalStats.extra, ...totalStats.extraDirs])];

package/package.json

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