speccrew 0.1.11 → 0.2.0

package/.speccrew/skills/speccrew-fd-api-contract/SKILL.md

@@ -99,6 +99,76 @@ Please confirm the following key points:
 After confirmation, you can start frontend and backend Designer Agents separately.
 ```
 
+## Step 6: Update Progress Files
+
+After user confirms Joint Confirmation:
+
+### 6.1 Update Checkpoints File
+
+Write/Update `.checkpoints.json`:
+
+- Path: `speccrew-workspace/iterations/{iteration-id}/02.feature-design/.checkpoints.json`
+- Content:
+  ```json
+  {
+    "stage": "02_feature_design",
+    "checkpoints": {
+      "function_decomposition": {
+        "passed": true,
+        "confirmed_at": "..."
+      },
+      "feature_spec_review": {
+        "passed": true,
+        "confirmed_at": "..."
+      },
+      "api_contract_joint": {
+        "passed": true,
+        "confirmed_at": "{current_timestamp}",
+        "description": "API contract joint confirmation passed"
+      }
+    }
+  }
+  ```
+
+- Preserve existing checkpoint statuses when updating
+- Log: "✅ Checkpoint (api_contract_joint) passed and recorded"
+
+### 6.2 Update Workflow Progress
+
+Update `WORKFLOW-PROGRESS.json` to finalize the stage:
+
+- Path: `speccrew-workspace/iterations/{iteration-id}/WORKFLOW-PROGRESS.json`
+- Update:
+  ```json
+  {
+    "current_stage": "03_system_design",
+    "stages": {
+      "02_feature_design": {
+        "status": "confirmed",
+        "completed_at": "{current_timestamp}",
+        "confirmed_at": "{current_timestamp}",
+        "outputs": [
+          "02.feature-design/[feature-name]-feature-spec.md",
+          "02.feature-design/[feature-name]-api-contract.md"
+        ]
+      }
+    }
+  }
+  ```
+
+- Set `02_feature_design.status` to `confirmed`
+- Set `current_stage` to `03_system_design`
+- Record all output file paths
+- Log: "✅ Stage 02_feature_design confirmed. Ready for System Design phase."
+
+### 6.3 Backward Compatibility
+
+If `WORKFLOW-PROGRESS.json` does not exist:
+- Log: "⚠️ No workflow progress file found. Skipping workflow update."
+- Still update `.checkpoints.json` if the directory exists
+
+---
+
 # Checklist
 
 - [ ] All APIs mentioned in feature spec have defined contracts

package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md

@@ -98,6 +98,38 @@ For each function, identify:
 
 Ask: "Here is the function breakdown with [EXISTING]/[MODIFIED]/[NEW] markers. Does this align with your understanding of the requirements?"
 
+### Checkpoint A Progress Update
+
+After user confirms the function breakdown:
+
+1. **Write/Update `.checkpoints.json`**:
+   - Path: `speccrew-workspace/iterations/{iteration-id}/02.feature-design/.checkpoints.json`
+   - Content:
+     ```json
+     {
+       "stage": "02_feature_design",
+       "checkpoints": {
+         "function_decomposition": {
+           "passed": true,
+           "confirmed_at": "{current_timestamp}",
+           "description": "Function decomposition confirmed"
+         },
+         "feature_spec_review": {
+           "passed": false,
+           "confirmed_at": null
+         },
+         "api_contract_joint": {
+           "passed": false,
+           "confirmed_at": null
+         }
+       }
+     }
+     ```
+
+2. If the file already exists, merge with existing content (preserve other checkpoints)
+
+3. Log: "✅ Checkpoint A (function_decomposition) passed and recorded"
+
 ## Step 4: Determine Output Structure
 
 Based on PRD structure, determine feature spec output structure:
@@ -398,6 +430,38 @@ Data Entities: {count} new, {count} modified
 4. Are all business rules and constraints captured?
 5. **[Master-Sub]** Is the module breakdown appropriate?
 
+### Checkpoint B Progress Update
+
+After user confirms the complete feature spec:
+
+1. **Update `.checkpoints.json`**:
+   - Path: `speccrew-workspace/iterations/{iteration-id}/02.feature-design/.checkpoints.json`
+   - Update content:
+     ```json
+     {
+       "stage": "02_feature_design",
+       "checkpoints": {
+         "function_decomposition": {
+           "passed": true,
+           "confirmed_at": "..."
+         },
+         "feature_spec_review": {
+           "passed": true,
+           "confirmed_at": "{current_timestamp}",
+           "description": "Feature specification confirmed"
+         },
+         "api_contract_joint": {
+           "passed": false,
+           "confirmed_at": null
+         }
+       }
+     }
+     ```
+
+2. Preserve `function_decomposition` checkpoint status when updating
+
+3. Log: "✅ Checkpoint B (feature_spec_review) passed and recorded"
+
 ## Step 10: Write Files
 
 ### 10.1 Determine Output Paths
@@ -473,6 +537,100 @@ Key requirements:
 
 After feature spec documents are complete, call `speccrew-fd-api-contract/SKILL.md` to generate API contract document.
 
+### 10.5 Multi-Platform Dispatch Progress Management
+
+**For multi-platform feature design (multiple frontend platforms):**
+
+#### 10.5.1 Pre-Dispatch: Check Resume State
+
+Before dispatching to multiple platforms:
+
+1. **Read existing `DISPATCH-PROGRESS.json`**:
+   - Path: `speccrew-workspace/iterations/{iteration-id}/02.feature-design/DISPATCH-PROGRESS.json`
+   - If exists, analyze task status:
+     ```json
+     {
+       "stage": "02_feature_design",
+       "total": 3,
+       "completed": 2,
+       "failed": 0,
+       "pending": 1,
+       "tasks": [
+         {
+           "id": "fd-web-vue",
+           "platform": "web-vue",
+           "skill": "speccrew-fd-feature-design",
+           "status": "completed",
+           "started_at": "...",
+           "completed_at": "...",
+           "output": "02.feature-design/[feature]-web-vue-feature-spec.md",
+           "error": null
+         }
+       ]
+     }
+     ```
+
+2. **Resume Strategy**:
+   - Skip tasks with `status == "completed"`
+   - Re-execute tasks with `status == "failed"`
+   - Execute tasks with `status == "pending"`
+
+#### 10.5.2 Initialize/Update Dispatch Progress
+
+Create or update `DISPATCH-PROGRESS.json` before starting dispatch:
+
+```json
+{
+  "stage": "02_feature_design",
+  "total": {count},
+  "completed": 0,
+  "failed": 0,
+  "pending": {count},
+  "tasks": [
+    {
+      "id": "fd-{platform}",
+      "platform": "{platform}",
+      "skill": "speccrew-fd-feature-design",
+      "status": "pending",
+      "started_at": null,
+      "completed_at": null,
+      "output": null,
+      "error": null
+    }
+  ]
+}
+```
+
+#### 10.5.3 Update Task Status on Completion
+
+After each worker completes:
+
+1. **Read current `DISPATCH-PROGRESS.json`**
+
+2. **Update the corresponding task entry**:
+   - On success:
+     ```json
+     {
+       "status": "completed",
+       "completed_at": "{timestamp}",
+       "output": "{output_file_path}"
+     }
+     ```
+   - On failure:
+     ```json
+     {
+       "status": "failed",
+       "completed_at": "{timestamp}",
+       "error": "{error_message}"
+     }
+     ```
+
+3. **Update summary counters** (`completed`, `failed`, `pending`)
+
+4. **Write updated `DISPATCH-PROGRESS.json`**
+
+5. Log progress: "📊 Dispatch progress: {completed}/{total} completed, {failed} failed, {pending} pending"
+
 # Key Rules
 
 | Rule | Description |

package/.speccrew/skills/speccrew-pm-requirement-analysis/SKILL.md

@@ -442,6 +442,69 @@ Please confirm the following key points:
 
 After confirmation, you can start the Solution Agent for solution planning.
 
+## Step 13: Write Progress Files
+
+After user confirms the PRD, write progress tracking files:
+
+### 13a Write Checkpoint File
+
+Write or update the checkpoint file at:
+```
+speccrew-workspace/iterations/{iteration}/01.product-requirement/.checkpoints.json
+```
+
+Content:
+```json
+{
+  "stage": "01_prd",
+  "checkpoints": {
+    "prd_review": {
+      "passed": true,
+      "confirmed_at": "<current-ISO-timestamp>",
+      "description": "PRD review and confirmation"
+    }
+  }
+}
+```
+
+### 13b Update Workflow Progress
+
+Read and update the WORKFLOW-PROGRESS.json file:
+
+1. **Read**: `speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json`
+2. **Update the following fields**:
+   - `current_stage` = "02_feature_design"
+   - `01_prd.status` = "confirmed"
+   - `01_prd.completed_at` = `<current-ISO-timestamp>`
+   - `01_prd.confirmed_at` = `<current-ISO-timestamp>`
+   - `01_prd.outputs` = `["01.product-requirement/{feature-name}-prd.md"]`
+
+**Example updated stage entry**:
+```json
+{
+  "01_prd": {
+    "status": "confirmed",
+    "started_at": "2026-04-08T10:00:00Z",
+    "completed_at": "2026-04-08T11:30:00Z",
+    "confirmed_at": "2026-04-08T11:35:00Z",
+    "outputs": [
+      "01.product-requirement/user-management-prd.md"
+    ]
+  }
+}
+```
+
+### 13c Handle Missing Progress File
+
+If WORKFLOW-PROGRESS.json does not exist (backward compatibility):
+- Create the file with initial structure
+- Set `01_prd` to confirmed state directly
+- Other stages remain as `pending`
+
+**Status Flow**: `pending` → `in_progress` → `completed` → `confirmed`
+
+---
+
 # Knowledge Loading Strategy
 
 1. **First**: Read `system-overview.md` for system context
@@ -473,3 +536,5 @@ After confirmation, you can start the Solution Agent for solution planning.
 - [ ] **[If modifying existing features]** All changes marked with [EXISTING]/[MODIFIED]/[NEW]
 - [ ] Files written to correct paths
 - [ ] Summary shown to user and confirmation requested
+- [ ] **[After confirmation]** Checkpoint file written to `01.product-requirement/.checkpoints.json`
+- [ ] **[After confirmation]** WORKFLOW-PROGRESS.json updated with confirmed status and outputs

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

@@ -191,6 +191,44 @@ Files Generated:
 - {list all file paths}
 ```
 
+## Step 7: Task Completion Report
+
+After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
+
+### On Success
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**:
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/INDEX.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module1}-design.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module2}-design.md
+- **Summary**: Backend system design completed for {feature_name} on {platform_id} with {count} module designs
+```
+
+### On Failure
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**: []
+- **Error**: {description of what went wrong}
+- **Error Category**: DEPENDENCY_MISSING | VALIDATION_ERROR | BLOCKED
+- **Recovery Hint**: {suggestion for how to resolve or retry}
+```
+
+**Error Categories:**
+- `DEPENDENCY_MISSING`: Required input file or knowledge document not found
+- `VALIDATION_ERROR`: Input validation failed (e.g., invalid Feature Spec format)
+- `BLOCKED`: Blocked by external dependency or prerequisite not met
+
 # Key Rules
 
 | Rule | Description |

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

@@ -208,6 +208,44 @@ Concerns/Trade-offs:
 4. Are all API calls from API Contract covered?
 5. Is the native integration approach suitable?
 
+## Step 7: Task Completion Report
+
+After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
+
+### On Success
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**:
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/INDEX.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module1}-design.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module2}-design.md
+- **Summary**: Desktop system design completed for {feature_name} on {platform_id} with {count} module designs
+```
+
+### On Failure
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**: []
+- **Error**: {description of what went wrong}
+- **Error Category**: DEPENDENCY_MISSING | VALIDATION_ERROR | BLOCKED
+- **Recovery Hint**: {suggestion for how to resolve or retry}
+```
+
+**Error Categories:**
+- `DEPENDENCY_MISSING`: Required input file or knowledge document not found
+- `VALIDATION_ERROR`: Input validation failed (e.g., invalid Feature Spec format)
+- `BLOCKED`: Blocked by external dependency or prerequisite not met
+
 # Key Rules
 
 | Rule | Description |

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

@@ -196,6 +196,44 @@ Concerns/Trade-offs:
 3. Do the pseudo-code patterns match project conventions?
 4. Are all API calls from API Contract covered?
 
+## Step 7: Task Completion Report
+
+After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
+
+### On Success
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**:
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/INDEX.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module1}-design.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module2}-design.md
+- **Summary**: Frontend system design completed for {feature_name} on {platform_id} with {count} module designs
+```
+
+### On Failure
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**: []
+- **Error**: {description of what went wrong}
+- **Error Category**: DEPENDENCY_MISSING | VALIDATION_ERROR | BLOCKED
+- **Recovery Hint**: {suggestion for how to resolve or retry}
+```
+
+**Error Categories:**
+- `DEPENDENCY_MISSING`: Required input file or knowledge document not found
+- `VALIDATION_ERROR`: Input validation failed (e.g., invalid Feature Spec format)
+- `BLOCKED`: Blocked by external dependency or prerequisite not met
+
 # Key Rules
 
 | Rule | Description |

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

@@ -204,6 +204,44 @@ Concerns/Trade-offs:
 4. Are all API calls from API Contract covered?
 5. Are platform-specific features (permissions, native integration) properly handled?
 
+## Step 7: Task Completion Report
+
+After completing all steps, output a structured completion report for the System Designer Agent to parse and update DISPATCH-PROGRESS.json:
+
+### On Success
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**:
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/INDEX.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module1}-design.md
+  - speccrew-workspace/iterations/{iter}/03.system-design/{platform_id}/{module2}-design.md
+- **Summary**: Mobile system design completed for {feature_name} on {platform_id} with {count} module designs
+```
+
+### On Failure
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: {task_id from context}
+- **Platform**: {platform_id}
+- **Feature**: {feature_name}
+- **Output Files**: []
+- **Error**: {description of what went wrong}
+- **Error Category**: DEPENDENCY_MISSING | VALIDATION_ERROR | BLOCKED
+- **Recovery Hint**: {suggestion for how to resolve or retry}
+```
+
+**Error Categories:**
+- `DEPENDENCY_MISSING`: Required input file or knowledge document not found
+- `VALIDATION_ERROR`: Input validation failed (e.g., invalid Feature Spec format)
+- `BLOCKED`: Blocked by external dependency or prerequisite not met
+
 # Key Rules
 
 | Rule | Description |

package/.speccrew/skills/speccrew-test-case-design/SKILL.md

@@ -302,3 +302,36 @@ Fill each section with test case data using `search_replace`.
 - [ ] Preconditions are clearly stated for each test case
 - [ ] Steps are detailed enough for execution without ambiguity
 - [ ] Document written to correct output path
+
+---
+
+# Task Completion Report
+
+Upon completion (success or failure), output the following report format:
+
+## Success Report
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: <from dispatch context, e.g., "test-case-web-vue">
+- **Platform**: <platform_id, e.g., "web-vue">
+- **Phase**: test_case_design
+- **Output Files**:
+  - `speccrew-workspace/iterations/{iteration}/05.system-test/cases/{platform_id}/[feature]-test-cases.md`
+- **Summary**: Test case design completed with {count} test cases covering {dimensions} dimensions
+```
+
+## Failure Report
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: <from dispatch context>
+- **Platform**: <platform_id>
+- **Phase**: test_case_design
+- **Output Files**: None
+- **Summary**: Test case design failed during {step}
+- **Error**: <detailed error description>
+- **Error Category**: DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED
+- **Partial Outputs**: <list of partially generated files or "None">
+- **Recovery Hint**: <suggestion for recovery, e.g., "Check feature spec document exists at specified path">
+```

package/.speccrew/skills/speccrew-test-code-gen/SKILL.md

@@ -344,3 +344,37 @@ Fill each section with code plan data from Step 4.
 - [ ] Shared fixtures and helpers are extracted properly
 - [ ] Arrange-Act-Assert structure maintained in tests
 - [ ] Code plan document written to correct path
+
+---
+
+# Task Completion Report
+
+Upon completion (success or failure), output the following report format:
+
+## Success Report
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: <from dispatch context, e.g., "test-code-web-vue">
+- **Platform**: <platform_id, e.g., "web-vue">
+- **Phase**: test_code_gen
+- **Output Files**:
+  - `speccrew-workspace/iterations/{iteration}/05.system-test/code/{platform_id}/[feature]-test-code-plan.md`
+  - <list of generated test source files>
+- **Summary**: Test code generation completed with {file_count} files covering {case_count} test cases
+```
+
+## Failure Report
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: <from dispatch context>
+- **Platform**: <platform_id>
+- **Phase**: test_code_gen
+- **Output Files**: <list of partial outputs or "None">
+- **Summary**: Test code generation failed during {step}
+- **Error**: <detailed error description>
+- **Error Category**: DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED
+- **Partial Outputs**: <list of partially generated files or "None">
+- **Recovery Hint**: <suggestion for recovery, e.g., "Verify test case document format is valid">
+```

package/.speccrew/skills/speccrew-test-execute/SKILL.md

@@ -291,3 +291,37 @@ Each bug report must include:
 - [ ] Bug severity is classified (Critical/High/Medium/Low)
 - [ ] All bug reports written to correct output path
 - [ ] Test report written to correct output path
+
+---
+
+# Task Completion Report
+
+Upon completion (success or failure), output the following report format:
+
+## Success Report
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: <from dispatch context, e.g., "test-exec-web-vue">
+- **Platform**: <platform_id, e.g., "web-vue">
+- **Phase**: test_execution
+- **Output Files**:
+  - `speccrew-workspace/iterations/{iteration}/05.system-test/reports/[feature]-test-report.md`
+  - `speccrew-workspace/iterations/{iteration}/05.system-test/bugs/[feature]-bug-{seq}.md` (if any failures)
+- **Summary**: Test execution completed with {passed}/{total} passed, {failed} failed, {skipped} skipped
+```
+
+## Failure Report
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: <from dispatch context>
+- **Platform**: <platform_id>
+- **Phase**: test_execution
+- **Output Files**: <list of partial outputs or "None">
+- **Summary**: Test execution failed during {step}
+- **Error**: <detailed error description>
+- **Error Category**: DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR | RUNTIME_ERROR | BLOCKED
+- **Partial Outputs**: <list of partially generated files or "None">
+- **Recovery Hint**: <suggestion for recovery, e.g., "Check test dependencies are installed and test configuration is valid">
+```