speccrew 0.7.12 → 0.7.14

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

@@ -16,167 +16,6 @@ tools: Read, Write, Glob, Grep
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<workflow id="test-case-design-main" status="pending" version="1.0" desc="Design structured test cases from Feature Spec and API Contract documents">
-
-  <!-- Input Parameters -->
-  <block type="input" id="I1" desc="Workflow input parameters">
-    <field name="feature_spec_path" required="true" type="string" desc="Path to feature specification document"/>
-    <field name="api_contract_path" required="false" type="string" desc="Path to API contract document"/>
-    <field name="system_design_path" required="false" type="string" desc="Path to system design document"/>
-    <field name="output_dir" required="true" type="string" desc="Directory for test case design output"/>
-    <field name="feature_name" required="true" type="string" desc="Feature name for output file naming"/>
-    <field name="platform_id" required="true" type="string" desc="Target platform identifier"/>
-    <field name="module" required="true" type="string" desc="Module abbreviation (3-4 letters)"/>
-  </block>
-
-  <!-- Global Constraints -->
-  <block type="rule" id="R1" level="forbidden" desc="Document generation constraints">
-    <field name="text">NEVER use create_file to write the test case design document directly</field>
-    <field name="text">MUST copy template first, then fill sections with search_replace</field>
-    <field name="text">NEVER replace entire document content in a single operation</field>
-  </block>
-
-  <block type="rule" id="R2" level="mandatory" desc="Template-first workflow">
-    <field name="text">Copy template MUST execute before filling sections</field>
-    <field name="text">All section titles MUST be preserved</field>
-  </block>
-
-  <!-- Main Processing Sequence -->
-  <sequence id="S1" name="Test Case Design" status="pending" desc="Design test cases from feature specifications">
-
-    <!-- Step 1: Read Feature Spec -->
-    <block type="task" id="B1" action="read-file" desc="Read feature specification document">
-      <field name="path" value="${feature_spec_path}"/>
-      <field name="output" var="feature_spec"/>
-    </block>
-
-    <!-- Step 2: Read API Contract (if provided) -->
-    <block type="gateway" id="G1" mode="exclusive" desc="Check if API contract path is provided">
-      <branch test="${api_contract_path} != null AND ${api_contract_path} != ''">
-        <block type="task" id="B2" action="read-file" desc="Read API contract document">
-          <field name="path" value="${api_contract_path}"/>
-          <field name="output" var="api_contract"/>
-        </block>
-      </branch>
-      <branch default="true" name="No API Contract">
-        <block type="event" id="E1" action="log" level="info" desc="Log API contract skip">
-          <field name="message">API contract path not provided, skipping API contract analysis</field>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Step 3: Read System Design (if provided) -->
-    <block type="gateway" id="G2" mode="exclusive" desc="Check if system design path is provided">
-      <branch test="${system_design_path} != null AND ${system_design_path} != ''">
-        <block type="task" id="B3" action="read-file" desc="Read system design document">
-          <field name="path" value="${system_design_path}"/>
-          <field name="output" var="system_design"/>
-        </block>
-      </branch>
-      <branch default="true" name="No System Design">
-        <block type="event" id="E2" action="log" level="info" desc="Log system design skip">
-          <field name="message">System design path not provided, skipping system design analysis</field>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Step 4: Read Testing Conventions (optional) -->
-    <block type="task" id="B4" action="read-file" desc="Read testing conventions if available">
-      <field name="path" value="speccrew-workspace/knowledges/techs/${platform_id}/conventions-system-test.md"/>
-      <field name="optional" value="true"/>
-      <field name="output" var="testing_conventions"/>
-    </block>
-
-    <!-- Step 5: Analyze Test Dimensions -->
-    <block type="task" id="B5" action="analyze" desc="Analyze test dimensions for comprehensive coverage">
-      <field name="analysis_dimensions">
-        - Functional Positive Tests (Happy Path)
-        - Boundary Value Tests
-        - Exception/Error Handling Tests
-        - Business Rule Constraint Tests
-        - Permission/Security Tests
-        - Data Validation Tests
-        - State Transition Tests (if applicable)
-      </field>
-      <field name="output" var="test_dimensions_analysis"/>
-    </block>
-
-    <!-- Step 6: Generate Test Case Matrix -->
-    <block type="task" id="B6" action="generate" desc="Generate structured test case matrix">
-      <field name="module" value="${module}"/>
-      <field name="naming_convention">TC-{MODULE}-{SEQ}</field>
-      <field name="priority_mapping">
-        - P0 (Critical) → P0-Critical
-        - P1 (Important) → P1-High
-        - P2 (Standard) → P2-Medium
-        - P3 (Minor) → P3-Low
-      </field>
-      <field name="output" var="test_case_matrix"/>
-    </block>
-
-    <!-- Step 7: Coverage Self-Check -->
-    <block type="task" id="B7" action="analyze" desc="Perform coverage self-check against acceptance criteria">
-      <field name="validation_rules">
-        - Each acceptance criterion has corresponding test case(s)
-        - Test case fully validates the criterion
-        - Coverage status marked for each requirement
-      </field>
-      <field name="output" var="coverage_check"/>
-    </block>
-
-    <!-- Step 8: Read Template -->
-    <block type="task" id="B8" action="read-file" desc="Read test case design template">
-      <field name="path" value="speccrew-test-case-design/templates/TEST-CASE-DESIGN-TEMPLATE.md"/>
-      <field name="output" var="template_content"/>
-    </block>
-
-    <!-- Step 9: Create Output Document -->
-    <block type="task" id="B9" action="write-file" desc="Create test case design document from template">
-      <field name="path" value="${output_dir}/${feature_name}-test-case-design.md"/>
-      <field name="template" value="${template_content}"/>
-      <field name="output" var="document_created"/>
-    </block>
-
-    <!-- Step 10: Fill Document Sections -->
-    <block type="task" id="B10" action="edit-file" desc="Fill Test Overview section">
-      <field name="path" value="${output_dir}/${feature_name}-test-case-design.md"/>
-      <field name="section">Test Overview</field>
-    </block>
-
-    <block type="task" id="B11" action="edit-file" desc="Fill Test Case Matrix section">
-      <field name="path" value="${output_dir}/${feature_name}-test-case-design.md"/>
-      <field name="section">Test Case Matrix</field>
-    </block>
-
-    <block type="task" id="B12" action="edit-file" desc="Fill Test Data Definition section">
-      <field name="path" value="${output_dir}/${feature_name}-test-case-design.md"/>
-      <field name="section">Test Data Definition</field>
-    </block>
-
-    <block type="task" id="B13" action="edit-file" desc="Fill Coverage Traceability section">
-      <field name="path" value="${output_dir}/${feature_name}-test-case-design.md"/>
-      <field name="section">Coverage Traceability</field>
-    </block>
-
-    <!-- Checkpoint -->
-    <block type="checkpoint" id="CP1" name="document-complete" desc="Verify test case design document is complete">
-      <field name="file" value="${output_dir}/${feature_name}-test-case-design.md"/>
-    </block>
-
-  </sequence>
-
-  <!-- Output Results -->
-  <block type="output" id="O1" desc="Workflow output results">
-    <field name="test_case_design_path" value="${output_dir}/${feature_name}-test-case-design.md" type="string" desc="Path to generated test case design document"/>
-    <field name="test_case_count" type="number" desc="Total number of test cases designed"/>
-    <field name="coverage_status" type="string" desc="Coverage status (full/partial)"/>
-  </block>
-
-</workflow>
-```
-
 # Key Rules
 
 | Rule | Description |

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

@@ -16,206 +16,6 @@ tools: Read, Write, Glob, Grep
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<workflow id="test-code-gen-main" status="pending" version="1.0" desc="Generate executable test code from confirmed test case documents">
-
-  <!-- Input Parameters -->
-  <block type="input" id="I1" desc="Workflow input parameters">
-    <field name="test_cases_path" required="true" type="string" desc="Path to test cases document"/>
-    <field name="system_design_path" required="false" type="string" desc="Path to system design document"/>
-    <field name="output_dir" required="true" type="string" desc="Directory for test code output"/>
-    <field name="feature_name" required="true" type="string" desc="Feature name for output file naming"/>
-    <field name="platform_id" required="true" type="string" desc="Target platform identifier"/>
-    <field name="module" required="true" type="string" desc="Module name for file organization"/>
-  </block>
-
-  <!-- Global Constraints -->
-  <block type="rule" id="R1" level="forbidden" desc="Document generation constraints">
-    <field name="text">NEVER use create_file to write the test code plan document directly</field>
-    <field name="text">MUST copy template first, then fill sections with search_replace for plan document</field>
-    <field name="text">NEVER replace entire document content in a single operation</field>
-  </block>
-
-  <block type="rule" id="R2" level="mandatory" desc="Template-first workflow for plan document">
-    <field name="text">Copy template MUST execute before filling sections for code plan document</field>
-    <field name="text">Test source code files are written directly (NOT template-filled)</field>
-  </block>
-
-  <block type="rule" id="R3" level="mandatory" desc="TC ID traceability">
-    <field name="text">Every test function MUST have a TC ID comment</field>
-    <field name="text">Format: // TC-{MODULE}-{SEQ}: {description}</field>
-  </block>
-
-  <!-- Main Processing Sequence -->
-  <sequence id="S1" name="Test Code Generation" status="pending" desc="Generate test code from test cases">
-
-    <!-- Step 1: Read Test Cases -->
-    <block type="task" id="B1" action="read-file" desc="Read confirmed test case document">
-      <field name="path" value="${test_cases_path}"/>
-      <field name="output" var="test_cases"/>
-    </block>
-
-    <!-- Step 2: Read Technical Conventions -->
-    <block type="task" id="B2" action="read-file" desc="Read platform testing conventions">
-      <field name="path" value="speccrew-workspace/knowledges/techs/${platform_id}/conventions-system-test.md"/>
-      <field name="optional" value="true"/>
-      <field name="output" var="system_test_conventions"/>
-    </block>
-
-    <!-- Fallback: Read unit test conventions -->
-    <block type="gateway" id="G1" mode="exclusive" desc="Check if system test conventions found">
-      <branch test="${system_test_conventions} == null">
-        <block type="task" id="B3" action="read-file" desc="Read unit test conventions as fallback">
-          <field name="path" value="speccrew-workspace/knowledges/techs/${platform_id}/conventions-unit-test.md"/>
-          <field name="optional" value="true"/>
-          <field name="output" var="unit_test_conventions"/>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Step 3: Read System Design (if provided) -->
-    <block type="gateway" id="G2" mode="exclusive" desc="Check if system design path is provided">
-      <branch test="${system_design_path} != null AND ${system_design_path} != ''">
-        <block type="task" id="B4" action="read-file" desc="Read system design document">
-          <field name="path" value="${system_design_path}"/>
-          <field name="output" var="system_design"/>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Step 4: Generate Code Plan -->
-    <block type="task" id="B5" action="analyze" desc="Determine file grouping strategy">
-      <field name="grouping_rules">
-        - IF test cases share same module/component THEN group into single test file
-        - IF test cases are independent THEN one test file per test case
-        - Maximum test cases per file: 10
-        - Naming convention: {module-name}.test.{ext} or {module-name}.spec.{ext}
-      </field>
-      <field name="output" var="file_grouping_strategy"/>
-    </block>
-
-    <block type="task" id="B6" action="analyze" desc="Plan test file structure">
-      <field name="analysis_focus">
-        - Files per module
-        - Single vs multiple files
-        - Integration test separation
-      </field>
-      <field name="output" var="test_file_structure"/>
-    </block>
-
-    <block type="task" id="B7" action="analyze" desc="Plan shared resources">
-      <field name="resource_types">
-        - Fixtures: Common test data
-        - Helpers: Reusable test utilities
-        - Mocks: Shared mock definitions
-      </field>
-      <field name="output" var="shared_resources_plan"/>
-    </block>
-
-    <block type="task" id="B8" action="analyze" desc="Plan mock/stub strategy">
-      <field name="dependency_types">
-        - Database: Mock repository/DAO or use test database
-        - External API: Mock HTTP client or use stub server
-        - File System: Mock file operations or use temp directory
-        - Message Queue: Mock producer/consumer
-        - Cache: Mock cache client or use in-memory cache
-      </field>
-      <field name="output" var="mock_strategy"/>
-    </block>
-
-    <block type="task" id="B9" action="analyze" desc="Create file-to-testcase mapping">
-      <field name="output" var="file_case_mapping"/>
-    </block>
-
-    <!-- Step 5: Checkpoint - Present Code Plan for Confirmation -->
-    <block type="task" id="B10" action="generate" desc="Generate code plan summary">
-      <field name="output" var="code_plan_summary"/>
-    </block>
-
-    <block type="event" id="E1" action="confirm" title="Confirm Test Code Plan" type="yesno" desc="Wait for user confirmation before generating code">
-      <field name="preview" value="${code_plan_summary}"/>
-      <on-confirm>
-        <field name="confirmed" value="true"/>
-      </on-confirm>
-      <on-cancel>
-        <field name="workflow.status" value="cancelled"/>
-      </on-cancel>
-    </block>
-
-    <!-- Step 6: Generate Test Code -->
-    <block type="task" id="B11" action="generate" desc="Generate fixtures">
-      <field name="output_dir" value="${output_dir}/__fixtures__"/>
-      <field name="output" var="fixtures_generated"/>
-    </block>
-
-    <block type="task" id="B12" action="generate" desc="Generate helpers">
-      <field name="output_dir" value="${output_dir}/__helpers__"/>
-      <field name="output" var="helpers_generated"/>
-    </block>
-
-    <block type="task" id="B13" action="generate" desc="Generate mocks">
-      <field name="output_dir" value="${output_dir}/__mocks__"/>
-      <field name="output" var="mocks_generated"/>
-    </block>
-
-    <block type="loop" id="L1" over="${file_case_mapping.files}" as="file_mapping" desc="Generate test files">
-      <block type="task" id="B14" action="generate" desc="Generate test file ${file_mapping.file_name}">
-        <field name="tc_annotation_format">// TC-{MODULE}-{SEQ}: {description}</field>
-        <field name="test_structure">Arrange-Act-Assert</field>
-        <field name="output_path" value="${output_dir}/${file_mapping.file_name}"/>
-      </block>
-    </block>
-
-    <!-- Step 7: Write Code Plan Document -->
-    <block type="task" id="B15" action="read-file" desc="Read test code plan template">
-      <field name="path" value="speccrew-test-code-gen/templates/TEST-CODE-PLAN-TEMPLATE.md"/>
-      <field name="output" var="plan_template"/>
-    </block>
-
-    <block type="task" id="B16" action="write-file" desc="Create test code plan document">
-      <field name="path" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-      <field name="template" value="${plan_template}"/>
-      <field name="output" var="plan_document_created"/>
-    </block>
-
-    <block type="task" id="B17" action="edit-file" desc="Fill File-to-TestCase Mapping section">
-      <field name="path" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-      <field name="section">File-to-TestCase Mapping</field>
-    </block>
-
-    <block type="task" id="B18" action="edit-file" desc="Fill Mock Strategy section">
-      <field name="path" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-      <field name="section">Mock Strategy</field>
-    </block>
-
-    <block type="task" id="B19" action="edit-file" desc="Fill Shared Resources section">
-      <field name="path" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-      <field name="section">Shared Resources</field>
-    </block>
-
-    <block type="task" id="B20" action="edit-file" desc="Fill Test File Structure section">
-      <field name="path" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-      <field name="section">Test File Structure</field>
-    </block>
-
-    <!-- Checkpoint -->
-    <block type="checkpoint" id="CP1" name="code-generation-complete" desc="Verify test code generation complete">
-      <field name="file" value="${output_dir}/${feature_name}-test-code-plan.md"/>
-    </block>
-
-  </sequence>
-
-  <!-- Output Results -->
-  <block type="output" id="O1" desc="Workflow output results">
-    <field name="test_code_plan_path" value="${output_dir}/${feature_name}-test-code-plan.md" type="string" desc="Path to test code plan document"/>
-    <field name="test_files" type="array" desc="List of generated test files"/>
-    <field name="total_test_cases" type="number" desc="Total number of test cases implemented"/>
-  </block>
-
-</workflow>
-```
-
 # Key Rules
 
 | Rule | Description |

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

@@ -31,206 +31,6 @@ tools: Read, Write, Glob, Grep
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<workflow id="test-reporter-main" status="pending" version="1.0" desc="Generate comprehensive test reports and individual bug reports from test execution results">
-
-  <!-- Input Parameters -->
-  <block type="input" id="I1" desc="Workflow input parameters">
-    <field name="execution_results_path" required="true" type="string" desc="Path to test execution results from speccrew-test-runner"/>
-    <field name="test_cases_path" required="true" type="string" desc="Path to test cases document with expected results"/>
-    <field name="output_dir" required="true" type="string" desc="Directory for report output"/>
-    <field name="feature_name" required="true" type="string" desc="Feature name for output file naming"/>
-    <field name="platform_id" required="true" type="string" desc="Target platform identifier"/>
-  </block>
-
-  <!-- Global Constraints -->
-  <block type="rule" id="R1" level="forbidden" desc="Document generation constraints">
-    <field name="text">NEVER use create_file to write test reports or bug reports directly</field>
-    <field name="text">MUST copy template first, then fill sections with search_replace</field>
-    <field name="text">NEVER replace entire document content in a single operation</field>
-  </block>
-
-  <block type="rule" id="R2" level="mandatory" desc="Template-first workflow">
-    <field name="text">Copy template MUST execute before filling sections</field>
-    <field name="text">All section titles MUST be preserved</field>
-  </block>
-
-  <block type="rule" id="R3" level="mandatory" desc="Bug report requirements">
-    <field name="text">Each failed test gets its own bug report file for independent tracking</field>
-    <field name="text">Always classify bug severity for prioritization</field>
-    <field name="text">Bug reports must include suggested fix direction</field>
-  </block>
-
-  <!-- Main Processing Sequence -->
-  <sequence id="S1" name="Test Reporting" status="pending" desc="Generate test reports and bug reports">
-
-    <!-- Step 1: Read Inputs -->
-    <block type="task" id="B1" action="read-file" desc="Read test execution results">
-      <field name="path" value="${execution_results_path}"/>
-      <field name="output" var="execution_results"/>
-    </block>
-
-    <block type="task" id="B2" action="read-file" desc="Read test cases document">
-      <field name="path" value="${test_cases_path}"/>
-      <field name="output" var="test_cases"/>
-    </block>
-
-    <!-- Step 2: Analyze Execution Results -->
-    <block type="task" id="B3" action="analyze" desc="Extract summary statistics">
-      <field name="extract_fields">
-        - total_tests
-        - passed
-        - failed
-        - errors
-        - skipped
-        - pass_rate
-        - execution_duration
-        - platform
-        - framework
-      </field>
-      <field name="output" var="summary_stats"/>
-    </block>
-
-    <block type="task" id="B4" action="analyze" desc="Identify failed tests">
-      <field name="filter_status">FAIL, ERROR, SKIP</field>
-      <field name="output" var="failed_tests"/>
-    </block>
-
-    <block type="task" id="B5" action="analyze" desc="Classify by test dimension">
-      <field name="dimensions">
-        - Happy Path
-        - Boundary Value
-        - Exception Handling
-        - Business Rules
-        - Permission/Security
-        - Data Validation
-      </field>
-      <field name="output" var="dimension_breakdown"/>
-    </block>
-
-    <!-- Step 3: Generate Test Report -->
-    <block type="task" id="B6" action="read-file" desc="Read test report template">
-      <field name="path" value="speccrew-test-reporter/templates/TEST-REPORT-TEMPLATE.md"/>
-      <field name="output" var="report_template"/>
-    </block>
-
-    <block type="task" id="B7" action="write-file" desc="Create test report document">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="template" value="${report_template}"/>
-      <field name="output" var="report_created"/>
-    </block>
-
-    <block type="task" id="B8" action="edit-file" desc="Fill Execution Summary section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Execution Summary</field>
-    </block>
-
-    <block type="task" id="B9" action="edit-file" desc="Fill Results Overview section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Results Overview</field>
-    </block>
-
-    <block type="task" id="B10" action="edit-file" desc="Fill Results by Test Dimension section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Results by Test Dimension</field>
-    </block>
-
-    <block type="task" id="B11" action="edit-file" desc="Fill Failed Test Details section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Failed Test Details</field>
-    </block>
-
-    <block type="task" id="B12" action="edit-file" desc="Fill Coverage Status section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Coverage Status</field>
-    </block>
-
-    <block type="task" id="B13" action="edit-file" desc="Fill Environment Information section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Environment Information</field>
-    </block>
-
-    <block type="task" id="B14" action="edit-file" desc="Fill Recommendations section">
-      <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-      <field name="section">Recommendations</field>
-    </block>
-
-    <!-- Step 4: Generate Bug Reports -->
-    <block type="gateway" id="G1" mode="exclusive" desc="Check if there are failed tests">
-      <branch test="${failed_tests.count} > 0">
-        <block type="task" id="B15" action="read-file" desc="Read bug report template">
-          <field name="path" value="speccrew-test-reporter/templates/BUG-REPORT-TEMPLATE.md"/>
-          <field name="output" var="bug_template"/>
-        </block>
-
-        <block type="loop" id="L1" over="${failed_tests.items}" as="failure" desc="Generate bug report for each failure">
-          <block type="task" id="B16" action="analyze" desc="Determine bug severity">
-            <field name="severity_criteria">
-              - Critical: Blocks core functionality, no workaround
-              - High: Major feature broken, workaround exists
-              - Medium: Minor feature issue, cosmetic problem
-              - Low: Enhancement, minor improvement
-            </field>
-            <field name="output" var="bug_severity"/>
-          </block>
-
-          <block type="task" id="B17" action="analyze" desc="Perform root cause analysis">
-            <field name="analysis_aspects">
-              - Error Category: Syntax, Logic, Integration, Environment, Performance
-              - Impact Assessment: What functionality is affected
-              - Likely Cause: Probable source of the issue
-              - Suggested Fix: Direction for resolution
-            </field>
-            <field name="output" var="root_cause_analysis"/>
-          </block>
-
-          <block type="task" id="B18" action="write-file" desc="Create bug report">
-            <field name="path" value="${output_dir}/bugs/${feature_name}-bug-${failure.sequence}.md"/>
-            <field name="template" value="${bug_template}"/>
-          </block>
-
-          <block type="task" id="B19" action="edit-file" desc="Fill Bug Description section"/>
-          <block type="task" id="B20" action="edit-file" desc="Fill Reproduction Steps section"/>
-          <block type="task" id="B21" action="edit-file" desc="Fill Expected vs Actual section"/>
-          <block type="task" id="B22" action="edit-file" desc="Fill Error Log section"/>
-          <block type="task" id="B23" action="edit-file" desc="Fill Root Cause Analysis section"/>
-          <block type="task" id="B24" action="edit-file" desc="Fill Suggested Fix section"/>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Step 5: Update Test Report with Bug Links -->
-    <block type="gateway" id="G2" mode="exclusive" desc="Check if bug reports were generated">
-      <branch test="${failed_tests.count} > 0">
-        <block type="task" id="B25" action="edit-file" desc="Update Failed Test Details with bug links">
-          <field name="path" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-          <field name="section">Failed Test Details</field>
-        </block>
-      </branch>
-    </block>
-
-    <!-- Checkpoint -->
-    <block type="checkpoint" id="CP1" name="reports-generated" desc="Verify test report generated">
-      <field name="file" value="${output_dir}/reports/${feature_name}-test-report.md"/>
-    </block>
-
-  </sequence>
-
-  <!-- Output Results -->
-  <block type="output" id="O1" desc="Workflow output results">
-    <field name="test_report_path" value="${output_dir}/reports/${feature_name}-test-report.md" type="string" desc="Path to generated test report"/>
-    <field name="bug_reports_dir" value="${output_dir}/bugs/" type="string" desc="Directory containing bug reports"/>
-    <field name="total_tests" type="number" desc="Total number of tests"/>
-    <field name="passed_tests" type="number" desc="Number of passed tests"/>
-    <field name="failed_tests" type="number" desc="Number of failed tests"/>
-    <field name="bug_report_count" type="number" desc="Number of bug reports generated"/>
-    <field name="pass_rate" type="string" desc="Overall pass rate percentage"/>
-  </block>
-
-</workflow>
-```
-
 ## Output
 
 ### Output Files