speccrew 0.5.13 → 0.5.15

package/.speccrew/skills/{speccrew-test-execute → speccrew-test-runner}/SKILL.md

@@ -1,42 +1,72 @@
 ---
-name: speccrew-test-execute
-description: Executes generated test code, collects results, performs deviation detection against expected outcomes, and generates comprehensive test reports and individual bug reports for failed test cases.
-tools: Read, Write, Glob, Grep, Terminal
+name: speccrew-test-runner
+description: "SpecCrew Test Runner. Executes test code, parses results, and detects deviations between expected and actual outcomes. Reads test code files and system design to run platform-specific test suites."
+tools: Read, Write, Bash, Glob, Grep
 ---
 
 # Trigger Scenarios
 
 - When speccrew-test-manager dispatches test execution after test code is confirmed
-- When user explicitly requests test execution and reporting
-- When user mentions "run tests", "execute tests", "generate test report"
+- When speccrew-test-reporter needs raw execution results to generate reports
+- When user explicitly requests "run tests", "execute tests", "run test suite"
+
+# Role Positioning
+
+**Primary Role**: Test Execution Engine
+
+**Responsibilities**:
+- Read and validate test code files
+- Perform environment pre-checks (runtime, dependencies, test framework)
+- Execute test commands for various platforms and frameworks
+- Parse test framework output into structured data
+- Detect deviations between expected and actual results
+- Output structured execution results for downstream consumers
+
+**Upstream Dependencies**: speccrew-test-manager, speccrew-test-code-generator
+**Downstream Consumers**: speccrew-test-reporter
 
 # Workflow
 
 ## Absolute Constraints
 
-> **These rules apply to ALL document generation steps. Violation = task failure.**
+> **These rules apply to ALL execution steps. Violation = task failure.**
+
+1. **MUST: Environment First** — Always verify environment before running tests. Never skip pre-checks.
+
+2. **MUST: Complete Output Capture** — Capture both stdout and stderr for diagnostics.
+
+3. **MUST: TC ID Traceability** — Every test result must be traced back to its TC ID.
+
+4. **MUST NOT: Generate Reports** — This skill does NOT generate human-readable reports or bug documents. Only structured execution results.
 
-1. **FORBIDDEN: `create_file` for documents** — NEVER use `create_file` to write test reports or bug reports. Documents MUST be created by copying the template then filling sections with `search_replace`.
+5. **MUST: Structured Output** — Output MUST be valid structured data (JSON/Markdown) that speccrew-test-reporter can consume.
 
-2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
+## Input Parameters
 
-3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections.
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `test_code_plan_path` | Yes | Path to test code plan document with test file mappings |
+| `test_cases_path` | Yes | Path to test cases document with expected results |
+| `platform_id` | Yes | Target platform (frontend/backend/desktop/mobile) |
+| `output_dir` | Yes | Directory for execution results output |
+| `feature_name` | Yes | Feature name for output file naming |
 
 ## Step 1: Read Inputs
 
 Read the following documents in order:
 
-1. **Test Cases Document**: `test_cases_path`
-   - Contains test case definitions with TC IDs, descriptions, and expected results
-   - Used for deviation detection against actual results
-
-2. **Test Code Plan**: `test_code_plan_path`
+1. **Test Code Plan**: `test_code_plan_path`
    - Contains mapping between TC IDs and test file locations
    - Identifies platform_id and corresponding test framework
+   - Lists all test files to be executed
 
-3. **Platform Configuration**:
-   - Confirm platform_id (frontend/backend/desktop/mobile)
-   - Identify test framework (jest/vitest/pytest/junit/etc.)
+2. **Test Cases Document**: `test_cases_path`
+   - Contains test case definitions with TC IDs, descriptions, and expected results
+   - Used for deviation detection against actual results
+
+3. **Test Code Files**: Read each test file listed in the code plan
+   - Extract TC ID comments for traceability mapping
+   - Verify test file syntax and structure
 
 **Input Validation**:
 - Verify all required paths are provided and files exist
@@ -46,7 +76,17 @@ Read the following documents in order:
 
 Before executing tests, verify the environment is ready:
 
-### 2.1 Check Test Dependencies
+### 2.1 Check Runtime Availability
+
+| Platform | Runtime Check |
+|----------|---------------|
+| Frontend | `node --version` |
+| Backend (Node) | `node --version` |
+| Backend (Python) | `python --version` or `python3 --version` |
+| Desktop | Platform-specific runtime check |
+| Mobile | Platform-specific runtime check |
+
+### 2.2 Check Test Dependencies
 
 | Platform | Dependency Check Command |
 |----------|--------------------------|
@@ -65,7 +105,7 @@ Environment Error: Missing test dependencies
 Please install dependencies before proceeding.
 ```
 
-### 2.2 Check Test Configuration Files
+### 2.3 Check Test Configuration Files
 
 Verify test configuration files exist:
 
@@ -76,7 +116,7 @@ Verify test configuration files exist:
 | Pytest | `pytest.ini`, `pyproject.toml`, or `setup.cfg` |
 | JUnit | `junit.xml` or build tool configuration |
 
-### 2.3 Check Service Dependencies
+### 2.4 Check Service Dependencies
 
 Determine if the system under test requires:
 - Database service running
@@ -85,7 +125,7 @@ Determine if the system under test requires:
 
 **Checkpoint A**: If any environment check fails, report specific missing items and stop execution.
 
-✋ **STOP IF FAILED**: IF any pre-check fails THEN:
+**STOP IF FAILED**: IF any pre-check fails THEN:
 1. Stop workflow immediately
 2. Report all failures to user
 3. Do NOT proceed to test execution
@@ -142,13 +182,16 @@ Parse test framework output to extract:
 | Skipped | Number of skipped tests |
 | Duration | Total execution time |
 
-### 4.2 Extract Failed Test Details
+### 4.2 Extract Test Details
 
-For each failed test, extract:
+For each test, extract:
 - **Test Function Name**: Full test name/suite
-- **Error Message**: Primary error description
-- **Stack Trace**: Call stack leading to failure
+- **TC ID**: Associated test case ID from comments
+- **Status**: PASS / FAIL / ERROR / SKIP
+- **Error Message**: Primary error description (if failed)
+- **Stack Trace**: Call stack leading to failure (if failed)
 - **Assertion Details**: Expected vs actual values (if available)
+- **Duration**: Individual test execution time
 
 ### 4.3 Map Tests to TC IDs
 
@@ -176,39 +219,40 @@ For each test case:
 
 | Type | Code | Description | Severity |
 |------|------|-------------|----------|
+| PASS | PASS | Test passed as expected | - |
 | FAIL | FAIL | Test assertion failed - actual result differs from expected | High |
 | ERROR | ERROR | Runtime error - code threw exception or crashed | Critical |
 | SKIP | SKIP | Test was skipped - preconditions not met | Medium |
 | FLAKY | FLAKY | Intermittent failure - non-deterministic behavior | High |
 
-### 5.3 Root Cause Analysis
+### 5.3 Root Cause Analysis (Basic)
 
-For each deviation, analyze:
+For each deviation, perform initial analysis:
 - **Assertion Failure**: Which specific assertion failed and why
 - **Runtime Error**: Exception type and location
 - **Skip Reason**: Why test could not execute
 - **Flaky Pattern**: Conditions causing intermittent failure
 
-> 📋 **Output Requirement**: These root cause analysis results MUST be included in Step 6 Report under the "Recommendations" section. Each root cause should map to its corresponding test case ID for traceability.
+> **Note**: Detailed root cause analysis with impact assessment is performed by speccrew-test-reporter.
 
-## Step 6: Generate Test Report
+## Step 6: Generate Execution Results
 
 ### 6.1 Read Template
 
-Read template: `speccrew-test-execute/templates/TEST-REPORT-TEMPLATE.md`
+Read template: `templates/TEST-EXECUTION-RESULT-TEMPLATE.md`
 
-### 6.2 Copy Template to Report Path
+### 6.2 Copy Template to Output Path
 
 1. **Read template** from Step 6.1
 2. **Replace top-level placeholders** (feature name, platform, execution date, etc.)
-3. **Create the document** using `create_file` at: `{output_dir}/{feature}-test-report.md`
+3. **Create the document** using `create_file` at: `{output_dir}/{feature}-test-execution-results.md`
 4. **Verify**: Document has complete section structure
 
 ### 6.3 Fill Each Section Using search_replace
 
 Fill each section with test execution data.
 
-> ⚠️ **CRITICAL CONSTRAINTS:**
+> **CRITICAL CONSTRAINTS:**
 > - **FORBIDDEN: `create_file` to rewrite the entire document**
 > - **MUST use `search_replace` to fill each section individually**
 > - **All section titles MUST be preserved**
@@ -217,66 +261,61 @@ Fill each section with test execution data.
 
 | Section | Content |
 |---------|---------|
-| **Execution Summary** | Feature name and platform, test framework and version, execution date and duration, overall pass rate |
-| **Results Overview** | Counts and percentages for all result types, visual pass/fail indication |
-| **Results by Test Dimension** | Breakdown by test type (happy path, boundary, exception, etc.), pass rate per dimension |
-| **Failed Test Details** | Table of all failed tests, links to corresponding bug reports |
-| **Coverage Status** | Requirement-to-test-case mapping, status per requirement |
+| **Execution Summary** | Feature name, platform, test framework, execution date, duration, overall pass rate |
+| **Results Overview** | Counts and percentages for all result types |
+| **Test Results Detail** | Table with TC ID, test name, status, duration, error message |
+| **Deviation Analysis** | List of all FAIL/ERROR/SKIP deviations with classification |
 | **Environment Information** | OS, runtime, framework versions, key dependencies |
-| **Recommendations** | Priority fixes needed, suggested next steps |
-
-## Step 7: Generate Bug Reports
-
-### 7.1 Read Template
-
-Read template: `speccrew-test-execute/templates/BUG-REPORT-TEMPLATE.md`
-
-### 7.2 Copy Template for Each Bug Report
-
-For each FAIL type failure:
-1. **Read template** from Step 7.1: `templates/BUG-REPORT-TEMPLATE.md`
-2. **Replace top-level placeholders** (Bug ID, feature name, TC ID)
-3. **Create document** using `create_file` at: `{output_dir}/bugs/{feature}-bug-{seq}.md`
-
-### 7.3 Fill Each Bug Report Using search_replace
-
-For each bug report created in 7.2, fill sections using `search_replace`:
-
-> ⚠️ **CRITICAL CONSTRAINTS:**
-> - **FORBIDDEN: `create_file` to rewrite the entire document**
-> - **MUST use `search_replace` to fill each section individually**
-
-**Section Filling Guide:**
-
-1. **Assign Bug ID**: `BUG-{feature}-{seq}` (sequential numbering)
-
-2. **Determine Severity**:
-   | Criteria | Severity |
-   |----------|----------|
-   | Blocks core functionality, no workaround | Critical |
-   | Major feature broken, workaround exists | High |
-   | Minor feature issue, cosmetic problem | Medium |
-   | Enhancement, minor improvement | Low |
-
-3. **Fill Bug Report Content**:
-   - Bug title reflecting the failure
-   - Related TC ID for traceability
-   - Clear reproduction steps
-   - Expected result from test case
-   - Actual result from execution
-   - Relevant error log excerpt
-   - Suggested fix direction
-
-### 7.4 Bug Report Quality Checklist
-
-Each bug report must include:
-- [ ] Unique Bug ID
-- [ ] Related TC ID
-- [ ] Severity classification
-- [ ] Clear reproduction steps
-- [ ] Expected vs actual result
-- [ ] Relevant log excerpt
-- [ ] Suggested fix direction
+| **Raw Output** | Captured stdout/stderr excerpts for debugging |
+
+## Output
+
+### Output Files
+
+| File | Path | Description |
+|------|------|-------------|
+| Execution Results | `{output_dir}/{feature}-test-execution-results.md` | Structured test execution data |
+
+### Output Format Contract
+
+The execution results document serves as the **input contract** for speccrew-test-reporter:
+
+```yaml
+execution_summary:
+  feature_name: string
+  platform_id: string
+  framework: string
+  execution_date: ISO8601
+  duration_ms: number
+  total_tests: number
+  passed: number
+  failed: number
+  errors: number
+  skipped: number
+  pass_rate: percentage
+
+test_results:
+  - tc_id: string
+    test_name: string
+    status: PASS|FAIL|ERROR|SKIP
+    duration_ms: number
+    error_message: string|null
+    stack_trace: string|null
+    expected_result: string
+    actual_result: string
+
+deviations:
+  - tc_id: string
+    type: FAIL|ERROR|SKIP|FLAKY
+    severity: Critical|High|Medium|Low
+    description: string
+
+environment:
+  os: string
+  runtime_version: string
+  framework_version: string
+  dependencies: list
+```
 
 # Key Rules
 
@@ -284,21 +323,20 @@ Each bug report must include:
 |------|-------------|
 | **Environment First** | Always verify environment before running tests |
 | **Complete Output Capture** | Capture both stdout and stderr for diagnostics |
-| **TC ID Traceability** | Every failed test must be traced back to its TC ID |
-| **One Bug Per File** | Each bug gets its own report file for tracking |
-| **Severity Classification** | Always classify bug severity for prioritization |
-| **Actionable Reports** | Bug reports must include suggested fix direction |
+| **TC ID Traceability** | Every test result must be traced back to its TC ID |
+| **No Report Generation** | This skill does NOT generate human-readable reports |
+| **Structured Output Only** | Output must be structured data for downstream consumption |
+| **Runner → Reporter Contract** | Output format must match speccrew-test-reporter input expectations |
 
 # Checklist
 
 - [ ] Environment pre-check passed before execution
 - [ ] All test files from code plan were executed
+- [ ] Test results are correctly parsed from framework output
 - [ ] Failed tests are correctly traced back to TC IDs
-- [ ] Test report includes pass rate and failure details
-- [ ] Each FAIL has a corresponding bug report with reproduction steps
-- [ ] Bug severity is classified (Critical/High/Medium/Low)
-- [ ] All bug reports written to correct output path
-- [ ] Test report written to correct output path
+- [ ] Deviation classification completed for all non-PASS results
+- [ ] Execution results written to correct output path
+- [ ] Output format follows contract for speccrew-test-reporter
 
 ---
 
@@ -310,13 +348,13 @@ Upon completion (success or failure), output the following report format:
 ```
 ## Task Completion Report
 - **Status**: SUCCESS
-- **Task ID**: <from dispatch context, e.g., "test-exec-web-vue">
+- **Task ID**: <from dispatch context, e.g., "test-runner-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)
+  - `{output_dir}/{feature}-test-execution-results.md`
 - **Summary**: Test execution completed with {passed}/{total} passed, {failed} failed, {skipped} skipped
+- **Next Step**: Dispatch to speccrew-test-reporter for report generation
 ```
 
 ## Failure Report

package/.speccrew/skills/speccrew-test-runner/templates/TEST-EXECUTION-RESULT-TEMPLATE.md

@@ -0,0 +1,80 @@
+# Test Execution Results: {Feature Name}
+
+> **Document Type**: Structured Execution Results  
+> **Consumer**: speccrew-test-reporter  
+> **Format Version**: 1.0
+
+---
+
+## 1. Execution Summary
+
+| Item | Value |
+|------|-------|
+| Feature Name | {feature_name} |
+| Platform | {platform_id} |
+| Test Framework | {framework} |
+| Execution Date | {date} |
+| Total Duration | {duration} |
+| Executor | speccrew-test-runner |
+
+## 2. Results Overview
+
+| Metric | Count | Percentage |
+|--------|-------|------------|
+| Total | {total} | 100% |
+| Passed | {passed} | {pass_rate}% |
+| Failed | {failed} | {fail_rate}% |
+| Error | {error} | {error_rate}% |
+| Skipped | {skipped} | {skip_rate}% |
+
+## 3. Test Results Detail
+
+| TC ID | Test Name | Status | Duration | Error Message |
+|-------|-----------|--------|----------|---------------|
+| {tc_id} | {test_name} | PASS/FAIL/ERROR/SKIP | {duration} | {message_or_empty} |
+
+## 4. Deviation Analysis
+
+### 4.1 Failed Tests (FAIL)
+
+| TC ID | Test Name | Severity | Description |
+|-------|-----------|----------|-------------|
+| {tc_id} | {test_name} | High | {description} |
+
+### 4.2 Runtime Errors (ERROR)
+
+| TC ID | Test Name | Severity | Description |
+|-------|-----------|----------|-------------|
+| {tc_id} | {test_name} | Critical | {description} |
+
+### 4.3 Skipped Tests (SKIP)
+
+| TC ID | Test Name | Severity | Description |
+|-------|-----------|----------|-------------|
+| {tc_id} | {test_name} | Medium | {description} |
+
+## 5. Environment Information
+
+| Item | Value |
+|------|-------|
+| OS | {os} |
+| Runtime | {runtime_version} |
+| Test Framework | {framework_version} |
+| Dependencies | {key_dependencies} |
+
+## 6. Raw Output Excerpts
+
+### 6.1 Standard Output (stdout)
+```
+{stdout_excerpt}
+```
+
+### 6.2 Standard Error (stderr)
+```
+{stderr_excerpt}
+```
+
+---
+
+**Results Generated:** {timestamp}  
+**Next Action:** Dispatch to speccrew-test-reporter for report generation

package/lib/utils.js

@@ -111,6 +111,7 @@ function removeDirRecursive(dirPath) {
 const DEPRECATED_SKILLS = [
   'speccrew-dev-desktop',   // replaced by speccrew-dev-desktop-electron + speccrew-dev-desktop-tauri
   'speccrew-dev-review',    // replaced by speccrew-dev-review-backend/frontend/mobile/desktop
+  'speccrew-test-execute',  // replaced by speccrew-test-runner + speccrew-test-reporter
 ];
 
 function cleanDeprecatedSkills(destDir, deprecatedList) {

package/package.json

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