speccrew 0.5.19 → 0.6.0

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

@@ -188,19 +188,19 @@ node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspac
 ```
 
 **Validation Rules:**
-- Verify `stages.04_development.status == "confirmed"` in the output
-- If not confirmed → **STOP** with message: "Development stage has not been confirmed. Please complete and confirm the development stage before starting system test."
+- Verify `stages.05_deployment.status == "confirmed"` in the output
+- If not confirmed → **STOP** with message: "Deployment stage has not been confirmed. Please complete and confirm the deployment stage before starting system test."
 
 **Update Current Stage**:
 ```bash
-node speccrew-workspace/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 06_system_test --status in_progress
 ```
 
 ### Step 0.2: Check Resume State (断点续传)
 
 **Read Checkpoints** (if file exists):
 ```bash
-node speccrew-workspace/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}/06.system-test/.checkpoints.json --checkpoints
 ```
 
 **Resume Decision Matrix:**
@@ -221,7 +221,7 @@ node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspac
 
 **Read Dispatch Progress Summary** (if file exists):
 ```bash
-node speccrew-workspace/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}/06.system-test/DISPATCH-PROGRESS.json --summary
 ```
 
 **Parse Task Status by Phase:**
@@ -325,7 +325,7 @@ Locate all required input documents:
 ### 1.3 Check Existing Test Artifacts
 
 Check if test artifacts already exist:
-- Check path: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/`
+- Check path: `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/`
 - Look for existing: `cases/`, `code/`, `reports/`, `bugs/` directories
 
 ### 1.4 User Confirmation
@@ -470,7 +470,7 @@ Each task entry in DISPATCH-PROGRESS.json contains:
 
 Before dispatching, create dispatch tracking:
 ```bash
-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"}]'
+node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --stage 06_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.
 
@@ -498,11 +498,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-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}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  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}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-case-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 3.4 Re-dispatch Failed Tasks
@@ -511,7 +511,7 @@ After all initial workers complete:
 
 1. **Query failed tasks:**
    ```bash
-   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --status failed
+   node speccrew-workspace/scripts/update-progress.js read --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --status failed
    ```
 
 2. **For each failed task (max 2 re-dispatches, total 3 attempts):**
@@ -520,7 +520,7 @@ After all initial workers complete:
 
 3. **After max attempts, mark permanently failed:**
    ```bash
-   node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "Max re-dispatch attempts (3) exceeded"
+   node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "Max re-dispatch attempts (3) exceeded"
    ```
 
 ### 3.5 Checkpoint A: Test Case Review
@@ -544,11 +544,11 @@ After test case design completes for all platforms:
 **Write Checkpoint File:**
 
 ```bash
-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)"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/.checkpoints.json --stage 06_system_test --checkpoint test_case_coverage --passed true --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`
+- `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/cases/{platform_id}/[feature]-test-cases.md`
 
 ## Phase 4: Test Code Generation
 
@@ -584,7 +584,7 @@ Invoke Skill directly:
 
 Append new tasks for test_code_gen phase by reading existing file and adding tasks:
 ```bash
-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"}]'
+node speccrew-workspace/scripts/update-progress.js init --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS-test-code-gen.json --stage 06_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.
 
@@ -604,11 +604,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-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}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  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}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-code-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 4.4 Review Verification (MANDATORY)
@@ -673,12 +673,12 @@ After test code generation completes for all platforms:
 **Update Checkpoint File:**
 
 ```bash
-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)"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/.checkpoints.json --stage 06_system_test --checkpoint test_code_review --passed true --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`
+- Test code plan: `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/code/{platform_id}/[feature]-test-code-plan.md`
 
 ## Phase 5: Test Execution & Bug Reporting
 
@@ -716,11 +716,11 @@ Execute tests and generate reports:
 For each completed worker, parse Task Completion Report:
 - On SUCCESS:
   ```bash
-  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-run-{platform_id} --status completed --output "{output_path}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-run-{platform_id} --status completed --output "{output_path}"
   ```
 - On FAILED:
   ```bash
-  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-run-{platform_id} --status failed --error "{error_message}"
+  node speccrew-workspace/scripts/update-progress.js update-task --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/DISPATCH-PROGRESS.json --task-id test-run-{platform_id} --status failed --error "{error_message}"
   ```
 
 ### 5.3 Stage 2: Test Reporter Dispatch
@@ -763,8 +763,8 @@ For each deviation identified:
 - Link to related feature requirement
 
 **Output Paths:**
-- Test Report: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/reports/[feature]-test-report.md`
-- Bug Reports: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/bugs/[feature]-bug-{序号}.md`
+- Test Report: `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/reports/[feature]-test-report.md`
+- Bug Reports: `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/bugs/[feature]-bug-{序号}.md`
 
 ## Phase 6: Delivery Summary
 
@@ -809,30 +809,30 @@ Provide clear recommendation:
 **Update Checkpoint File:**
 
 ```bash
-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"
+node speccrew-workspace/scripts/update-progress.js write-checkpoint --file speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/.checkpoints.json --stage 06_system_test --checkpoint test_execution_report --passed true --description "Test execution final report"
 ```
 
 **Update Workflow Progress:**
 
 ```bash
-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/"
+node speccrew-workspace/scripts/update-progress.js update-workflow --file speccrew-workspace/WORKFLOW-PROGRESS.json --stage 06_system_test --status confirmed --output "06.system-test/cases/,06.system-test/code/,06.system-test/reports/,06.system-test/bugs/"
 ```
 
-> **Note**: `current_stage` does not advance — 05_system_test is the final stage of the pipeline.
+> **Note**: `current_stage` does not advance — 06_system_test is the final stage of the pipeline.
 
 # Deliverables
 
 | Deliverable | Path | Notes |
 |-------------|------|-------|
-| Test Case Documents | `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/cases/{platform_id}/[feature]-test-cases.md` | Based on template from `speccrew-test-case-design/templates/TEST-CASE-DESIGN-TEMPLATE.md` |
-| Test Code Plan | `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/code/{platform_id}/[feature]-test-code-plan.md` | Based on template from `speccrew-test-code-gen/templates/TEST-CODE-PLAN-TEMPLATE.md` |
-| Test Execution Results | `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/results/{platform_id}/[feature]-test-execution-results.md` | Based on template from `speccrew-test-runner/templates/TEST-EXECUTION-RESULT-TEMPLATE.md` |
-| Test Report | `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/reports/[feature]-test-report.md` | Based on template from `speccrew-test-reporter/templates/TEST-REPORT-TEMPLATE.md` |
-| Bug Reports | `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/bugs/[feature]-bug-{序号}.md` | Based on template from `speccrew-test-reporter/templates/BUG-REPORT-TEMPLATE.md` |
+| Test Case Documents | `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/cases/{platform_id}/[feature]-test-cases.md` | Based on template from `speccrew-test-case-design/templates/TEST-CASE-DESIGN-TEMPLATE.md` |
+| Test Code Plan | `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/code/{platform_id}/[feature]-test-code-plan.md` | Based on template from `speccrew-test-code-gen/templates/TEST-CODE-PLAN-TEMPLATE.md` |
+| Test Execution Results | `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/results/{platform_id}/[feature]-test-execution-results.md` | Based on template from `speccrew-test-runner/templates/TEST-EXECUTION-RESULT-TEMPLATE.md` |
+| Test Report | `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/reports/[feature]-test-report.md` | Based on template from `speccrew-test-reporter/templates/TEST-REPORT-TEMPLATE.md` |
+| Bug Reports | `speccrew-workspace/iterations/{number}-{type}-{name}/06.system-test/bugs/[feature]-bug-{序号}.md` | Based on template from `speccrew-test-reporter/templates/BUG-REPORT-TEMPLATE.md` |
 
 # Pipeline Position
 
-**Upstream**: System Developer (receives `04.development/` output and source code)
+**Upstream**: Deployment (receives `05.deployment/` output and deployed system)
 
 **Downstream**: Delivery phase (produces test reports and bug reports)
 

package/.speccrew/skills/speccrew-deploy-build/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: speccrew-deploy-build
+description: Executes application build commands based on techs knowledge conventions. Runs the build, verifies success, and reports build artifacts.
+tools: Read, Bash, Glob
+---
+
+# Trigger Scenarios
+
+- User requests to build the application before deployment
+- Deploy Agent needs to verify the application compiles successfully
+- CI/CD pipeline requires a build step verification
+
+# Input Parameters
+
+| Parameter | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `platform_id` | Yes | string | Platform identifier (e.g., backend-spring, frontend-react) |
+| `build_cmd` | Yes | string | Build command from conventions-data/build (e.g., `mvn package -DskipTests`) |
+| `project_root` | Yes | string | Absolute path to the project root directory |
+| `iteration_path` | Yes | string | Current iteration directory path |
+
+# Workflow
+
+## Step 1: Pre-build Check
+
+Verify prerequisites before executing the build:
+
+1. **Verify project_root exists**
+   - Check directory exists at `project_root`
+   - If not exists → FAILED with Error Category: DEPENDENCY_MISSING
+
+2. **Verify build tool is available**
+   - Detect build tool from `build_cmd`:
+     - `mvn` → Run `mvn --version`
+     - `npm` / `pnpm` / `yarn` → Run `{tool} --version`
+     - `gradle` → Run `gradle --version`
+     - `go` → Run `go version`
+   - If tool not available → FAILED with Error Category: DEPENDENCY_MISSING
+
+3. **Check for build config files**
+   - Maven: `pom.xml` must exist in `project_root`
+   - Node.js: `package.json` must exist in `project_root`
+   - Gradle: `build.gradle` or `build.gradle.kts` must exist
+   - Go: `go.mod` must exist
+   - If config missing → FAILED with Error Category: VALIDATION_ERROR
+
+## Step 2: Execute Build
+
+Run the build command:
+
+1. **Execute build_cmd via Bash**
+   - Working directory: `project_root`
+   - Command: `build_cmd`
+   - Capture stdout and stderr
+   - Record start time before execution
+
+2. **Check exit code**
+   - Exit code 0 → Continue to Step 3
+   - Exit code non-zero → FAILED with Error Category: BUILD_FAILURE
+
+3. **Calculate build duration**
+   - Duration = end_time - start_time
+
+## Step 3: Verify Build Output
+
+Check for expected build artifacts:
+
+1. **Detect expected artifacts by platform**
+   - Spring/Maven: `target/*.jar` files
+   - Node.js: `dist/` or `build/` directory
+   - Gradle: `build/libs/*.jar`
+   - Go: Binary executable in project root or `bin/`
+
+2. **Verify artifacts exist**
+   - Use Glob to find expected artifacts
+   - If no artifacts found → FAILED with Error Category: BUILD_FAILURE
+
+3. **Record artifact paths**
+   - List all generated artifacts with full paths
+
+# Task Completion Report
+
+## Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Platform**: {platform_id}
+- **Project Root**: {project_root}
+- **Build Duration**: {duration_seconds}s
+- **Build Command**: {build_cmd}
+- **Artifact Paths**:
+  - {artifact_path_1}
+  - {artifact_path_2}
+  - ...
+- **Build Log** (last 20 lines):
+```
+{last_20_lines_of_build_output}
+```
+- **Summary**: Build completed successfully with {artifact_count} artifacts generated
+```
+
+## Failure Report
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Platform**: {platform_id}
+- **Project Root**: {project_root}
+- **Build Command**: {build_cmd}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR}
+- **Error**: {detailed error description}
+- **Build Log** (last 30 lines):
+```
+{last_30_lines_of_build_output}
+```
+- **Recovery Hint**: {suggestion for resolving the issue}
+```
+
+# Key Rules
+
+| Rule | Description |
+|------|-------------|
+| **No Hard-coded Commands** | All build commands come from input parameters |
+| **Tool Detection** | Automatically detect and verify build tool availability |
+| **Artifact Verification** | Always verify expected artifacts exist after build |
+| **Duration Tracking** | Record and report build duration |
+| **Log Capture** | Capture and report relevant build output |

package/.speccrew/skills/speccrew-deploy-migrate/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: speccrew-deploy-migrate
+description: Executes database migration scripts using the project's migration tool. Validates migration results and reports affected tables.
+tools: Read, Bash, Glob
+---
+
+# Trigger Scenarios
+
+- User requests to run database migrations before deployment
+- Deploy Agent needs to apply pending schema changes
+- CI/CD pipeline requires database migration verification
+
+# Input Parameters
+
+| Parameter | Required | Type | Description |
+|-----------|----------|------|-------------|
+| `platform_id` | Yes | string | Platform identifier |
+| `migration_cmd` | Yes | string | Migration execution command from conventions-data (e.g., `mvn flyway:migrate`) |
+| `validation_cmd` | No | string | Migration validation command (e.g., `mvn flyway:validate`) |
+| `migration_scripts` | Yes | string | JSON array of migration scripts: `[{"name":"V001__create_user.sql","path":"...","type":"CREATE TABLE"}]` |
+| `project_root` | Yes | string | Absolute path to the project root directory |
+| `iteration_path` | Yes | string | Current iteration directory path |
+
+# Workflow
+
+## Step 1: Pre-migration Check
+
+Verify prerequisites before executing migrations:
+
+1. **Verify migration script files exist**
+   - Parse `migration_scripts` JSON array
+   - For each script, verify file exists at specified `path`
+   - If any script missing → FAILED with Error Category: DEPENDENCY_MISSING
+
+2. **Verify migration tool is available**
+   - Detect tool from `migration_cmd` (e.g., `mvn`, `npm`, `npx`)
+   - Run tool version check
+   - If tool not available → FAILED with Error Category: DEPENDENCY_MISSING
+
+3. **Count total scripts to execute**
+   - Record total script count from `migration_scripts`
+   - Log: "Preparing to execute {count} migration scripts"
+
+## Step 2: Execute Migration
+
+Run the migration command:
+
+1. **Execute migration_cmd via Bash**
+   - Working directory: `project_root`
+   - Command: `migration_cmd`
+   - Capture stdout and stderr
+   - Record start time before execution
+
+2. **Check exit code**
+   - Exit code 0 → Continue to Step 3
+   - Exit code non-zero → FAILED with Error Category: BUILD_FAILURE
+
+## Step 3: Validate Migration (if validation_cmd provided)
+
+Run validation if command is provided:
+
+1. **Execute validation_cmd via Bash**
+   - Working directory: `project_root`
+   - Command: `validation_cmd`
+   - Capture output
+
+2. **Verify validation result**
+   - Exit code 0 → All migrations applied successfully
+   - Exit code non-zero → FAILED with Error Category: VALIDATION_ERROR
+
+3. **If validation fails**
+   - Report specific failure reason from output
+   - Include suggestion for manual intervention
+
+## Step 4: Report Migration Results
+
+Compile and report migration summary:
+
+1. **List scripts executed**
+   - Extract from migration output or use input `migration_scripts`
+
+2. **List tables affected**
+   - Parse `type` field from each script:
+     - CREATE TABLE → New table created
+     - ALTER TABLE → Table modified
+     - DROP TABLE → Table removed
+
+3. **Calculate execution duration**
+   - Duration = end_time - start_time
+
+# Task Completion Report
+
+## Success Report
+
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Platform**: {platform_id}
+- **Project Root**: {project_root}
+- **Migration Command**: {migration_cmd}
+- **Scripts Executed**: {count}
+  - {script_1_name}: {type} ({tables_affected})
+  - {script_2_name}: {type} ({tables_affected})
+  - ...
+- **Tables Affected**:
+  - Created: {table_list}
+  - Modified: {table_list}
+  - Dropped: {table_list}
+- **Validation Status**: {PASSED | SKIPPED}
+- **Execution Duration**: {duration_seconds}s
+- **Summary**: Database migration completed successfully
+```
+
+## Failure Report
+
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Platform**: {platform_id}
+- **Project Root**: {project_root}
+- **Migration Command**: {migration_cmd}
+- **Error Category**: {DEPENDENCY_MISSING | BUILD_FAILURE | VALIDATION_ERROR}
+- **Error**: {detailed error description}
+- **Scripts Attempted**: {count}
+- **Failed Script**: {script_name} (if applicable)
+- **Migration Output** (last 30 lines):
+```
+{last_30_lines_of_migration_output}
+```
+- **Recovery Hint**: {suggestion for resolving the issue}
+```
+
+# Key Rules
+
+| Rule | Description |
+|------|-------------|
+| **Script Verification** | Always verify migration script files exist before execution |
+| **Optional Validation** | Validation step is optional based on validation_cmd presence |
+| **JSON Parsing** | Parse migration_scripts JSON to extract script metadata |
+| **Table Tracking** | Report tables affected by each migration script |
+| **Duration Tracking** | Record and report migration execution duration |