speccrew 0.1.11 → 0.2.0

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

@@ -15,6 +15,76 @@ Your core task is: coordinate three-phase testing workflow (test case design →
 
 # Workflow
 
+## Phase 0: Workflow Progress Management
+
+### Step 0.1: Stage Gate — Verify Upstream Completion
+
+**Read `WORKFLOW-PROGRESS.json`** from workspace root:
+```
+speccrew-workspace/WORKFLOW-PROGRESS.json
+```
+
+**Validation Rules:**
+- Verify `stages.04_development.status == "confirmed"`
+- If not confirmed → **STOP** with message: "Development stage has not been confirmed. Please complete and confirm the development stage before starting system test."
+
+**Update Current Stage:**
+- Set `stages.05_system_test.status` to `"in_progress"`
+- Record `stages.05_system_test.started_at` with current timestamp
+- Write updated `WORKFLOW-PROGRESS.json`
+
+### Step 0.2: Check Resume State (断点续传)
+
+**Read Checkpoint File** (if exists):
+```
+speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/.checkpoints.json
+```
+
+**Resume Decision Matrix:**
+
+| Checkpoint State | Action |
+|-----------------|--------|
+| `test_case_coverage.passed == true` | Skip Phase 3 (test-case-design), proceed to Phase 4 (test-code-gen) |
+| `test_code_review.passed == true` | Skip Phase 3+4, proceed to Phase 5 (test-execution) |
+| `test_execution_report.passed == true` | Stage complete — ask user if they want to redo |
+| File does not exist | Proceed normally from Phase 1 |
+
+**User Confirmation for Resume:**
+- Display detected resume point to user
+- Ask: "Resume from [phase]? Or restart from beginning?"
+- Proceed based on user choice
+
+### Step 0.3: Check Dispatch Resume (多平台断点续传)
+
+**Read Dispatch Progress** (if exists):
+```
+speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json
+```
+
+**Parse Task Status by Phase:**
+- Group tasks by `phase` field (test_case_design, test_code_gen, test_execution)
+- For each phase, identify:
+  - `completed` tasks — skip
+  - `failed` tasks — retry
+  - `pending` tasks — execute
+
+**Display Progress Summary:**
+```
+Dispatch Resume Status:
+├── test_case_design: {completed}/{total} completed, {failed} failed, {pending} pending
+├── test_code_gen: {completed}/{total} completed, {failed} failed, {pending} pending
+└── test_execution: {completed}/{total} completed, {failed} failed, {pending} pending
+```
+
+### Step 0.4: Backward Compatibility
+
+If `WORKFLOW-PROGRESS.json` does not exist:
+- Proceed with existing workflow (Phase 1 onwards)
+- Skip all progress tracking steps
+- Maintain full compatibility with legacy projects
+
+---
+
 ## Phase 1: Preparation
 
 When user requests to start testing:
@@ -93,7 +163,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 +177,40 @@ 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.
+
+> **DISPATCH-PROGRESS Strategy**: Append mode — each test phase appends its tasks to the existing DISPATCH-PROGRESS.json with a distinct `phase` field. Previous phase records are preserved for full traceability.
+
+**Initialize Dispatch Progress File:**
+
+Before dispatching, create or update `DISPATCH-PROGRESS.json`:
+```json
+{
+  "stage": "05_system_test",
+  "phase": "test_case_design",
+  "total": {platform_count},
+  "completed": 0,
+  "failed": 0,
+  "pending": {platform_count},
+  "tasks": [
+    {
+      "id": "test-case-{platform_id}",
+      "platform": "{platform_id}",
+      "phase": "test_case_design",
+      "skill": "speccrew-test-case-design",
+      "status": "pending",
+      "started_at": null,
+      "completed_at": null,
+      "output": null,
+      "error": null
+    }
+  ]
+}
+```
+
+**Dispatch Workers:**
+
+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`:
@@ -116,11 +219,19 @@ Invoke `speccrew-task-worker` agents in parallel:
     - `api_contract_path`: Path to the API contract document (if exists)
     - `platform_id`: Platform identifier
     - `output_path`: Path for the platform-specific test cases document
+    - `task_id`: `test-case-{platform_id}` (for progress tracking)
 - Parallel execution pattern:
   - Worker 1: Master Feature Spec + Platform 1 Design → Platform 1 Test Cases
   - Worker 2: Master Feature Spec + Platform 2 Design → Platform 2 Test Cases
   - Worker N: Master Feature Spec + Platform N Design → Platform N Test Cases
 
+**Update Progress on Completion:**
+
+For each completed worker, parse Task Completion Report and update `DISPATCH-PROGRESS.json`:
+- On SUCCESS: Set `status` to `"completed"`, record `completed_at`, set `output`
+- On FAILED: Set `status` to `"failed"`, record `error`, set `recovery_hint` if available
+- Recalculate `completed`, `failed`, `pending` counts
+
 ### 3.4 Checkpoint A: Test Case Review
 
 After test case design completes for all platforms:
@@ -139,6 +250,22 @@ After test case design completes for all platforms:
 - Wait for user to confirm test case coverage is adequate
 - Only proceed to code generation phase after user confirmation
 
+**Write Checkpoint File:**
+
+Create or update `.checkpoints.json`:
+```json
+{
+  "stage": "05_system_test",
+  "checkpoints": {
+    "test_case_coverage": {
+      "passed": true,
+      "confirmed_at": "{ISO8601_timestamp}",
+      "description": "Test case coverage review (Checkpoint A)"
+    }
+  }
+}
+```
+
 **Output Path:**
 - `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/cases/{platform_id}/[feature]-test-cases.md`
 
@@ -163,14 +290,51 @@ 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`
+> **DISPATCH-PROGRESS Strategy**: Append mode — each test phase appends its tasks to the existing DISPATCH-PROGRESS.json with a distinct `phase` field. Previous phase records are preserved for full traceability.
+
+**Initialize Dispatch Progress File:**
+
+Update `DISPATCH-PROGRESS.json` with new phase:
+```json
+{
+  "stage": "05_system_test",
+  "phase": "test_code_gen",
+  "total": {platform_count},
+  "completed": 0,
+  "failed": 0,
+  "pending": {platform_count},
+  "tasks": [
+    {
+      "id": "test-code-{platform_id}",
+      "platform": "{platform_id}",
+      "phase": "test_code_gen",
+      "skill": "speccrew-test-code-gen",
+      "status": "pending",
+      "started_at": null,
+      "completed_at": null,
+      "output": null,
+      "error": null
+    }
+  ]
+}
+```
+
+**Dispatch Workers:**
+
+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
     - `platform_id`: Platform identifier
     - `output_dir`: Directory for generated test code and plan
+    - `task_id`: `test-code-{platform_id}` (for progress tracking)
+
+**Update Progress on Completion:**
+
+For each completed worker, parse Task Completion Report and update `DISPATCH-PROGRESS.json`:
+- On SUCCESS: Set `status` to `"completed"`, record `completed_at`, set `output`
+- On FAILED: Set `status` to `"failed"`, record `error`
+- Recalculate `completed`, `failed`, `pending` counts
 
 ### 4.4 Checkpoint B: Code Review
 
@@ -190,6 +354,27 @@ After test code generation completes for all platforms:
 - Wait for user to confirm test code is acceptable
 - Only proceed to execution phase after user confirmation
 
+**Update Checkpoint File:**
+
+Update `.checkpoints.json`:
+```json
+{
+  "stage": "05_system_test",
+  "checkpoints": {
+    "test_case_coverage": {
+      "passed": true,
+      "confirmed_at": "{timestamp}",
+      "description": "Test case coverage review (Checkpoint A)"
+    },
+    "test_code_review": {
+      "passed": true,
+      "confirmed_at": "{ISO8601_timestamp}",
+      "description": "Test code generation review (Checkpoint B)"
+    }
+  }
+}
+```
+
 **Output:**
 - Test code: Written to project source test directories
 - Test code plan: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/code/{platform_id}/[feature]-test-code-plan.md`
@@ -214,13 +399,50 @@ Invoke Skill directly:
 
 ### 5.3 Multi-Platform Parallel Execution
 
-Invoke `speccrew-task-worker` agents in parallel:
-- Each worker receives:
-  - `skill_name`: `speccrew-test-execute`
+> **DISPATCH-PROGRESS Strategy**: Append mode — each test phase appends its tasks to the existing DISPATCH-PROGRESS.json with a distinct `phase` field. Previous phase records are preserved for full traceability.
+
+**Initialize Dispatch Progress File:**
+
+Update `DISPATCH-PROGRESS.json` with new phase:
+```json
+{
+  "stage": "05_system_test",
+  "phase": "test_execution",
+  "total": {platform_count},
+  "completed": 0,
+  "failed": 0,
+  "pending": {platform_count},
+  "tasks": [
+    {
+      "id": "test-exec-{platform_id}",
+      "platform": "{platform_id}",
+      "phase": "test_execution",
+      "skill": "speccrew-test-execute",
+      "status": "pending",
+      "started_at": null,
+      "completed_at": null,
+      "output": null,
+      "error": null
+    }
+  ]
+}
+```
+
+**Dispatch Workers:**
+
+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
     - `output_dir`: Directory for reports
+    - `task_id`: `test-exec-{platform_id}` (for progress tracking)
+
+**Update Progress on Completion:**
+
+For each completed worker, parse Task Completion Report and update `DISPATCH-PROGRESS.json`:
+- On SUCCESS: Set `status` to `"completed"`, record `completed_at`, set `output`
+- On FAILED: Set `status` to `"failed"`, record `error`
+- Recalculate `completed`, `failed`, `pending` counts
 
 ### 5.4 Deviation Detection
 
@@ -279,6 +501,60 @@ Provide clear recommendation:
 - Confirm to proceed to delivery phase, or
 - Return to development phase for bug fixes
 
+### 6.5 Finalize Progress Files
+
+**Update Checkpoint File:**
+
+Update `.checkpoints.json`:
+```json
+{
+  "stage": "05_system_test",
+  "checkpoints": {
+    "test_case_coverage": {
+      "passed": true,
+      "confirmed_at": "{timestamp}",
+      "description": "Test case coverage review (Checkpoint A)"
+    },
+    "test_code_review": {
+      "passed": true,
+      "confirmed_at": "{timestamp}",
+      "description": "Test code generation review (Checkpoint B)"
+    },
+    "test_execution_report": {
+      "passed": true,
+      "confirmed_at": "{ISO8601_timestamp}",
+      "description": "Test execution final report"
+    }
+  }
+}
+```
+
+**Update Workflow Progress:**
+
+Update `WORKFLOW-PROGRESS.json`:
+```json
+{
+  "iteration": "{iteration_name}",
+  "current_stage": "05_system_test",
+  "stages": {
+    "05_system_test": {
+      "status": "confirmed",
+      "started_at": "{timestamp}",
+      "completed_at": "{timestamp}",
+      "confirmed_at": "{ISO8601_timestamp}",
+      "outputs": [
+        "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.
+
 # Deliverables
 
 | Deliverable | Path | Notes |
@@ -299,7 +575,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):
@@ -191,6 +193,50 @@ Task Record: speccrew-workspace/iterations/{number}-{type}-{name}/04.development
 Ready for testing phase.
 ```
 
+## Task Completion Report
+
+At the end of Step 8 (or if the skill fails at any point), output a structured Task Completion Report:
+
+### Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**:
+  - {file_path_1}
+  - {file_path_2}
+  - ...
+- **Summary**: Backend module {module_name} implemented with {X} tasks completed
+```
+
+### Failure Report
+
+If the skill fails at any step:
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**: {list of partially generated files, or "None"}
+- **Summary**: {one-line description of what was attempted}
+- **Error**: {detailed error description}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED}
+- **Partial Outputs**: {list of files that were generated before failure, or "None"}
+- **Recovery Hint**: {suggestion for how to resolve and retry}
+```
+
+**Error Category Definitions**:
+- `DEPENDENCY_MISSING`: Required runtime/dependency not available
+- `BUILD_FAILURE`: Compilation error, maven/gradle build failure
+- `VALIDATION_ERROR`: Checkstyle, test failure, or validation error
+- `RUNTIME_ERROR`: Service startup failure, runtime exception
+- `BLOCKED`: Blocked by external dependency or unresolved design issue
+
 # Key Rules
 
 | Rule | Description |

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`
@@ -245,6 +246,50 @@ Technical Debt Items: {count}
 Task Record: speccrew-workspace/iterations/{number}-{type}-{name}/04.development/{platform_id}/[feature-name]-task.md
 ```
 
+## Task Completion Report
+
+At the end of Step 8 (or if the skill fails at any point), output a structured Task Completion Report:
+
+### Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**:
+  - {file_path_1}
+  - {file_path_2}
+  - ...
+- **Summary**: Desktop module {module_name} implemented with {X} tasks completed
+```
+
+### Failure Report
+
+If the skill fails at any step:
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**: {list of partially generated files, or "None"}
+- **Summary**: {one-line description of what was attempted}
+- **Error**: {detailed error description}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED}
+- **Partial Outputs**: {list of files that were generated before failure, or "None"}
+- **Recovery Hint**: {suggestion for how to resolve and retry}
+```
+
+**Error Category Definitions**:
+- `DEPENDENCY_MISSING`: Required Node.js/npm or Rust dependency not available
+- `BUILD_FAILURE`: Electron/Tauri build error, native compilation failure
+- `VALIDATION_ERROR`: ESLint, TypeScript type check, Rust clippy, or test failure
+- `RUNTIME_ERROR`: App crash on launch, runtime exception, IPC communication failure
+- `BLOCKED`: Blocked by external dependency, native module issue, or unresolved design issue
+
 **Ask user to confirm:**
 1. Are all IPC channels working correctly?
 2. Is context isolation properly configured?
@@ -267,11 +312,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 |
 |-----------|---------|---------|
@@ -210,6 +212,50 @@ Tech Debt: {count}
 Task Record: speccrew-workspace/iterations/{number}-{type}-{name}/04.development/{platform_id}/{feature-name}-tasks.md
 ```
 
+## Task Completion Report
+
+At the end of Step 6 (or if the skill fails at any point), output a structured Task Completion Report:
+
+### Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**:
+  - {file_path_1}
+  - {file_path_2}
+  - ...
+- **Summary**: Frontend module {module_name} implemented with {X} tasks completed
+```
+
+### Failure Report
+
+If the skill fails at any step:
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**: {list of partially generated files, or "None"}
+- **Summary**: {one-line description of what was attempted}
+- **Error**: {detailed error description}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED}
+- **Partial Outputs**: {list of files that were generated before failure, or "None"}
+- **Recovery Hint**: {suggestion for how to resolve and retry}
+```
+
+**Error Category Definitions**:
+- `DEPENDENCY_MISSING`: Required Node.js/npm dependency not available
+- `BUILD_FAILURE`: Vite/Webpack build error, compilation failure
+- `VALIDATION_ERROR`: ESLint, TypeScript type check, or test failure
+- `RUNTIME_ERROR`: Runtime exception in browser/dev server
+- `BLOCKED`: Blocked by external dependency or unresolved design issue
+
 # Key Rules
 
 | Rule | Description |

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
 
@@ -199,6 +200,50 @@ Mobile Development Complete:
 Ready for QA Agent acceptance testing.
 ```
 
+## Task Completion Report
+
+At the end of Step 8 (or if the skill fails at any point), output a structured Task Completion Report:
+
+### Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**:
+  - {file_path_1}
+  - {file_path_2}
+  - ...
+- **Summary**: Mobile module {module_name} implemented with {X} tasks completed
+```
+
+### Failure Report
+
+If the skill fails at any step:
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from dispatch context}
+- **Platform**: {platform_id}
+- **Module**: {module_name}
+- **Output Files**: {list of partially generated files, or "None"}
+- **Summary**: {one-line description of what was attempted}
+- **Error**: {detailed error description}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED}
+- **Partial Outputs**: {list of files that were generated before failure, or "None"}
+- **Recovery Hint**: {suggestion for how to resolve and retry}
+```
+
+**Error Category Definitions**:
+- `DEPENDENCY_MISSING`: Required Flutter/Dart or npm dependency not available
+- `BUILD_FAILURE`: Flutter build error, Gradle/Xcode compilation failure
+- `VALIDATION_ERROR`: Static analysis error (`flutter analyze`), test failure
+- `RUNTIME_ERROR`: App crash on simulator/emulator, runtime exception
+- `BLOCKED`: Blocked by external dependency, native module issue, or unresolved design issue
+
 # Key Rules
 
 | Rule | Description |
@@ -213,7 +258,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