speccrew 0.6.46 → 0.6.48

package/.speccrew/skills/speccrew-knowledge-bizs-api-graph-xml/SKILL.md

@@ -137,7 +137,7 @@ This skill operates in **strict sequential execution mode**:
     </block>
 
     <block type="event" id="E1" action="log" level="info" desc="Log step 1 completion">
-Step 1 Status: COMPLETED - Read ${api_analysis_path}, Found ${endpoints.length} endpoints
+      <field name="message">Step 1 Status: COMPLETED - Read ${api_analysis_path}, Found ${endpoints.length} endpoints</field>
     </block>
   </sequence>
 
@@ -212,7 +212,7 @@ Step 1 Status: COMPLETED - Read ${api_analysis_path}, Found ${endpoints.length}
     </block>
 
     <block type="event" id="E2" action="log" level="info" desc="Log step 2 completion">
-Step 2 Status: COMPLETED - Extracted graph nodes (${apiNodes.length} APIs, ${serviceNodes.length} services, ${tableNodes.length} tables, ${dtoNodes.length} DTOs)
+      <field name="message">Step 2 Status: COMPLETED - Extracted graph nodes (${apiNodes.length} APIs, ${serviceNodes.length} services, ${tableNodes.length} tables, ${dtoNodes.length} DTOs)</field>
     </block>
   </sequence>
 
@@ -291,7 +291,7 @@ Step 2 Status: COMPLETED - Extracted graph nodes (${apiNodes.length} APIs, ${ser
     </block>
 
     <block type="event" id="E3" action="log" level="info" desc="Log step 3 completion">
-Step 3 Status: COMPLETED - Extracted graph edges (${operatesEdges.length + invokesEdges.length + referencesEdges.length + dependsOnEdges.length + mapsToEdges.length} total)
+      <field name="message">Step 3 Status: COMPLETED - Extracted graph edges (${operatesEdges.length + invokesEdges.length + referencesEdges.length + dependsOnEdges.length + mapsToEdges.length} total)</field>
     </block>
   </sequence>
 
@@ -315,7 +315,7 @@ Step 3 Status: COMPLETED - Extracted graph edges (${operatesEdges.length + invok
     </block>
 
     <block type="event" id="E4" action="log" level="info" desc="Log step 4 completion">
-Step 4 Status: COMPLETED - Graph JSON written to ${output_dir}/${markerFilename}.graph.json
+      <field name="message">Step 4 Status: COMPLETED - Graph JSON written to ${output_dir}/${markerFilename}.graph.json</field>
     </block>
   </sequence>
 
@@ -331,7 +331,7 @@ Step 4 Status: COMPLETED - Graph JSON written to ${output_dir}/${markerFilename}
     </block>
 
     <block type="event" id="E5" action="log" level="info" desc="Log step 5 completion">
-Step 5 Status: COMPLETED - Graph completion marker written to ${output_dir}/${markerFilename}.graph-done.json
+      <field name="message">Step 5 Status: COMPLETED - Graph completion marker written to ${output_dir}/${markerFilename}.graph-done.json</field>
     </block>
   </sequence>
 
@@ -340,12 +340,12 @@ Step 5 Status: COMPLETED - Graph completion marker written to ${output_dir}/${ma
     <block type="gateway" id="G6" mode="exclusive" desc="Determine result status">
       <branch test="${success} == true" name="Success">
         <block type="event" id="E6a" action="log" level="info" desc="Log success">
-Step 6 Status: COMPLETED - Graph construction success: Generated graph data with ${node_count} nodes and ${edge_count} edges
+          <field name="message">Step 6 Status: COMPLETED - Graph construction success: Generated graph data with ${node_count} nodes and ${edge_count} edges</field>
         </block>
       </branch>
       <branch test="${success} == false" name="Failure">
         <block type="event" id="E6b" action="log" level="error" desc="Log failure">
-Step 6 Status: COMPLETED - Graph construction failed: ${error_message}
+          <field name="message">Step 6 Status: COMPLETED - Graph construction failed: ${error_message}</field>
         </block>
       </branch>
     </block>

package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md

@@ -99,7 +99,6 @@ Stage 4: System Summary
 ## XML Workflow Definition
 
 <workflow id="bizs-dispatch-main" status="pending" version="1.0" desc="bizs knowledge base generation 5-stage pipeline">
-  > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `docs/rules/xml-workflow-spec.md`
 
   <!-- ============================================================
        Input Parameters Definition
@@ -187,7 +186,7 @@ Stage 4: System Summary
         <field name="message">Skipping empty directory: ${module.name}</field>
       </block>
       <block type="event" id="S0-E1" action="log" level="info" desc="Log backend module">
-Discovered backend module: ${module.name} → Platform type: backend-${module.business_name}
+        <field name="message">Discovered backend module: ${module.name} → Platform type: backend-${module.business_name}</field>
       </block>
     </block>
 
@@ -200,7 +199,7 @@ Discovered backend module: ${module.name} → Platform type: backend-${module.bu
         <field name="message">Skipping non-frontend directory: ${frontend.name}</field>
       </block>
       <block type="event" id="S0-E2" action="log" level="info" desc="Log frontend platform">
-Discovered frontend platform: ${frontend.name} → Tech stack: Vue/React/UniApp
+        <field name="message">Discovered frontend platform: ${frontend.name} → Tech stack: Vue/React/UniApp</field>
       </block>
     </block>
 
@@ -229,10 +228,14 @@ Detected ${platforms.length} platforms:
 Continue with knowledge base generation?
       </field>
       <on-confirm>
-        <block type="event" action="log" level="info" desc="User confirmed">User confirmed platform list, continuing</block>
+        <block type="event" action="log" level="info" desc="User confirmed">
+                  <field name="message">User confirmed platform list, continuing</field>
+                </block>
       </on-confirm>
       <on-cancel>
-        <block type="event" action="log" level="warn" desc="User cancelled">User cancelled, terminating workflow</block>
+        <block type="event" action="log" level="warn" desc="User cancelled">
+                  <field name="message">User cancelled, terminating workflow</field>
+                </block>
         <field name="workflow.status" value="cancelled"/>
       </on-cancel>
     </block>
@@ -244,7 +247,7 @@ Continue with knowledge base generation?
     </block>
 
     <block type="event" id="S0-E4" action="log" level="info" desc="Report detected platform list">
-Detected ${platforms.length} platforms: ${platforms.names}
+    <field name="message">Detected ${platforms.length} platforms: ${platforms.names}</field>
     </block>
   </sequence>
 
@@ -314,7 +317,7 @@ Detected ${platforms.length} platforms: ${platforms.names}
     </block>
 
     <block type="event" id="S1b-E1" action="log" level="info" desc="Report Feature inventory statistics">
-Feature inventory initialized. ${feature_count} features across ${platform_count} platforms.
+    <field name="message">Feature inventory initialized. ${feature_count} features across ${platform_count} platforms.</field>
     </block>
   </sequence>
 
@@ -344,11 +347,11 @@ Feature inventory initialized. ${feature_count} features across ${platform_count
 
         <!-- Step 2: Report merge result -->
         <block type="event" id="S1c-E1" action="log" level="info" desc="Report merge result">
-Feature merge complete:
+        <field name="message">Feature merge complete:
 - Added: ${merge_result.added}
 - Removed: ${merge_result.removed}
 - Changed: ${merge_result.changed} (reset for re-analysis)
-- Unchanged: ${merge_result.unchanged} (analysis state preserved)
+- Unchanged: ${merge_result.unchanged} (analysis state preserved)</field>
         </block>
 
         <!-- Step 3: Mark stale Features -->
@@ -362,7 +365,7 @@ Feature merge complete:
       </branch>
       <branch default="true" name="Full mode">
         <block type="event" id="S1c-E2" action="log" level="info" desc="Full mode skip merge">
-Full mode, skipping Feature merge step
+        <field name="message">Full mode, skipping Feature merge step</field>
         </block>
       </branch>
     </block>
@@ -418,7 +421,7 @@ Full mode, skipping Feature merge step
       <block type="gateway" id="S2-G0" mode="exclusive" desc="Determine batch response">
         <branch test="${batch_response.action} == 'done'" name="All Features processed">
           <block type="event" id="S2-E-Done" action="log" level="info" desc="All Features processed">
-All Features analyzed, exiting Stage 2 loop
+          <field name="message">All Features analyzed, exiting Stage 2 loop</field>
           </block>
           <field name="stage2_complete" value="true"/>
         </branch>
@@ -426,7 +429,7 @@ All Features analyzed, exiting Stage 2 loop
           
           <!-- Step 2: Prepare analysis task specifications -->
           <block type="event" id="S2-E-Batch" action="log" level="info" desc="Report current batch">
-Processing batch: ${batch_response.batch.length} Features
+          <field name="message">Processing batch: ${batch_response.batch.length} Features</field>
           </block>
 
           <!-- Step 2: Dispatch Worker for each Feature -->
@@ -508,7 +511,7 @@ Requirements:
 
           <!-- Step 2.5: Graph Worker Task Preparation -->
           <block type="event" id="S2-E-Graph" action="log" level="info" desc="Prepare Graph Worker tasks">
-Preparing Graph data generation for completed Features
+          <field name="message">Preparing Graph data generation for completed Features</field>
           </block>
 
           <!-- Step 2.5: Dispatch Graph Worker -->
@@ -589,7 +592,7 @@ Requirements:
           </block>
 
           <block type="event" id="S2-E-Result" action="log" level="info" desc="Report batch processing result">
-Batch processing complete: ${batch_result.success} succeeded, ${batch_result.failed} failed
+          <field name="message">Batch processing complete: ${batch_result.success} succeeded, ${batch_result.failed} failed</field>
           </block>
         </branch>
       </block>
@@ -601,7 +604,7 @@ Batch processing complete: ${batch_result.success} succeeded, ${batch_result.fai
     </block>
 
     <block type="event" id="S2-E-Final" action="log" level="info" desc="Stage 2 complete">
-Stage 2 Milestone: Feature analysis complete. ${analyzed_count} features analyzed, ${failed_count} failed. ${graph_count} graph data files generated.
+    <field name="message">Stage 2 Milestone: Feature analysis complete. ${analyzed_count} features analyzed, ${failed_count} failed. ${graph_count} graph data files generated.</field>
     </block>
   </sequence>
 
@@ -665,7 +668,7 @@ Requirements:
     </block>
 
     <block type="event" id="S3-E1" action="log" level="info" desc="Stage 3 complete">
-Stage 3 Milestone: Module summaries complete. ${module_count} modules summarized.
+    <field name="message">Stage 3 Milestone: Module summaries complete. ${module_count} modules summarized.</field>
     </block>
   </sequence>
 
@@ -710,14 +713,14 @@ Requirements:
         </branch>
         <branch default="true" name="Non-UI platform">
           <block type="event" id="S35-E1" action="log" level="info" desc="Backend platform skip style extraction">
-Backend platform ${platform.platformId} skipping UI style extraction
+          <field name="message">Backend platform ${platform.platformId} skipping UI style extraction</field>
           </block>
         </branch>
       </block>
     </block>
 
     <block type="event" id="S35-E2" action="log" level="info" desc="Stage 3.5 complete">
-Stage 3.5 Milestone: UI style patterns extracted. ${pattern_count} patterns extracted from ${frontend_platform_count} platforms.
+    <field name="message">Stage 3.5 Milestone: UI style patterns extracted. ${pattern_count} patterns extracted from ${frontend_platform_count} platforms.</field>
     </block>
   </sequence>
 
@@ -767,7 +770,7 @@ Requirements:
     </block>
 
     <block type="event" id="S4-E1" action="log" level="info" desc="Stage 4 complete">
-Stage 4 Milestone: System overview generated. All stages complete. Pipeline finished successfully.
+    <field name="message">Stage 4 Milestone: System overview generated. All stages complete. Pipeline finished successfully.</field>
     </block>
   </sequence>
 
@@ -780,7 +783,7 @@ Stage 4 Milestone: System overview generated. All stages complete. Pipeline fini
     </try>
     <catch on="worker_failed">
       <block type="event" id="EH1-E1" action="log" level="warn" desc="Worker failed, log error and continue">
-Worker ${error.worker} failed: ${error.message}
+      <field name="message">Worker ${error.worker} failed: ${error.message}</field>
       </block>
       <block type="task" id="EH1-B1" action="run-script" desc="Update failed status">
         <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/update-feature-status.js"</field>
@@ -794,15 +797,15 @@ Worker ${error.worker} failed: ${error.message}
     </catch>
     <catch on="script_error">
       <block type="event" id="EH1-E2" action="log" level="error" desc="Script execution failed">
-Script ${error.script} execution failed: ${error.message}
+      <field name="message">Script ${error.script} execution failed: ${error.message}</field>
       </block>
     </catch>
     <catch on="stage_abort">
       <block type="event" id="EH1-E3" action="log" level="error" desc="Stage aborted">
-Stage ${error.stage} execution aborted: ${error.message}
+      <field name="message">Stage ${error.stage} execution aborted: ${error.message}</field>
       </block>
       <block type="event" id="EH1-E4" action="log" level="warn" desc="High failure rate">
-Failure rate exceeds 50%, terminating entire pipeline
+      <field name="message">Failure rate exceeds 50%, terminating entire pipeline</field>
       </block>
     </catch>
   </block>
@@ -824,41 +827,11 @@ Failure rate exceeds 50%, terminating entire pipeline
 
 ---
 
-## Input/Output Specification (Supplementary)
-
-### Input Parameters
-
-| Variable | Description | Default |
-|----------|-------------|---------|
-| `source_path` | Source code path (can be a subdirectory; auto-detects platform root by traversing upward) | project root |
-| `language` | User's language code (e.g., "zh", "en") | **REQUIRED** |
-| `sync_mode` | `"full"` or `"incremental"` | `"full"` |
-| `base_commit` | (incremental only) Git base commit hash | — |
-| `head_commit` | (incremental only) Git HEAD commit hash | `HEAD` |
-| `changed_files` | (incremental only) Pre-computed changed file list | — |
-| `max_concurrent_workers` | Maximum parallel Worker Agents | `5` |
-| `workspace_path` | **(required)** Absolute path to speccrew-workspace directory | — |
-| `sync_state_bizs_dir` | **(required)** Absolute path to `knowledges/base/sync-state/knowledge-bizs/` | — |
-| `ide_skills_dir` | **(required)** Absolute path to IDE skills directory (e.g., `.qoder/skills`, `.cursor/skills`) | — |
-| `configs_dir` | **(required)** Absolute path to `docs/configs/` directory | — |
-| `graph_root` | Graph data output root path (absolute path preferred) | `{workspace_path}/knowledges/bizs/graph` |
-| `completed_dir` | **(required)** Marker file output directory for Worker results (absolute path required) | — |
-
-> **MANDATORY**: All path parameters MUST be absolute paths provided by the caller. DO NOT use ListDir to search for script locations. DO NOT construct paths by guessing or relative path resolution.
-
-### Output Files
-
-- Entry directories: `{sync_state_bizs_dir}/entry-dirs-{platform}.json`
-- Feature inventory: `{sync_state_bizs_dir}/features-{platform}.json`
-- Feature docs: `{workspace_path}/knowledges/bizs/{platform}/{module}/features/*.md`
-- Module overviews: `{workspace_path}/knowledges/bizs/{platform}/{module}/*-overview.md`
-- UI style patterns: `{workspace_path}/knowledges/techs/{platform_id}/ui-style-patterns/` (page-types/, components/, layouts/)
-- System overview: `{workspace_path}/knowledges/bizs/system-overview.md`
-- Graph data: `{workspace_path}/knowledges/bizs/graph/`
+## Appendix: Reference
 
----
+### Skill Routing Table (Stage 2)
 
-## Skill Routing Table (Stage 2)
+> **Note**: Detailed routing logic is defined in XML Stage 2 gateway (S2-G1).
 
 | platformType | skill_name | Description |
 |--------------|------------|-------------|
@@ -867,11 +840,9 @@ Failure rate exceeds 50%, terminating entire pipeline
 | `desktop` | `speccrew-knowledge-bizs-ui-analyze-xml` | Desktop apps (Electron/WPF) |
 | `backend` | `speccrew-knowledge-bizs-api-analyze-xml` | Backend APIs (Java/Python/Node.js) |
 
-> **CRITICAL**: Use this routing table to select the correct skill for each feature.
-
 ---
 
-## Platform Types
+### Platform Types
 
 | Platform Type | Platform Subtype | Description |
 |---------------|------------------|-------------|
@@ -882,9 +853,9 @@ Failure rate exceeds 50%, terminating entire pipeline
 
 ---
 
-## Worker Completion Marker Format
+### Worker Completion Marker Format
 
-### Marker File Naming Convention
+#### Marker File Naming Convention
 
 **Pattern**: `{module}-{subpath}-{fileName}.{type}.json`
 
@@ -903,7 +874,7 @@ Failure rate exceeds 50%, terminating entire pipeline
 | `user/admin/UserController.java` | `user-admin-UserController.done.json` |
 | `order/api/v2/OrderService.java` | `order-api-v2-OrderService.done.json` |
 
-### .done.json Required Fields
+#### .done.json Required Fields
 
 ```json
 {
@@ -921,9 +892,9 @@ Failure rate exceeds 50%, terminating entire pipeline
 
 ---
 
-## Batch Processing Details
+### Batch Processing Details
 
-### get-batch Script Output Format
+#### get-batch Script Output Format
 
 ```json
 {
@@ -944,7 +915,7 @@ Failure rate exceeds 50%, terminating entire pipeline
 }
 ```
 
-### process-results Script Behavior
+#### process-results Script Behavior
 
 - Scans `.done.json` files → updates feature status to `completed` in features-*.json
 - Scans `.graph-done.json` files → confirms graph data generation complete
@@ -953,128 +924,14 @@ Failure rate exceeds 50%, terminating entire pipeline
 
 ---
 
-## Stateless Design (Context Recovery)
-
-Dispatch adopts a fully stateless file-driven design. If context compression or interruption occurs during execution:
-
-- No need to memorize any batch state or Worker output
-- Re-execute loop: `get-batch` will automatically recover from file state, skipping completed and in-progress features
-- `process-results` will process all uncleaned marker files
-- The entire flow is safely re-entrant
-
----
-
-## Large-Scale Scenario Guidance
-
-When modules contain **more than 20 Features**:
+### Stateless Design
 
-- **Single Agent Limit**: A single Worker Agent can reliably process ~20 features per session due to context window constraints. Beyond this, context degradation may cause incomplete document generation.
-- **Multi-Worker Strategy**: For modules with >20 features, the calling Agent should dispatch multiple Worker Agents in parallel, each handling a non-overlapping subset of features.
-- **Resume Support**: The `get-next-batch` script naturally supports resume across sessions — it skips features that already have `.done` files.
-- **Validation After Completion**: After all features are marked `analyzed=true`, run `process-batch-results` with `--validateDocs --syncStatePath` to verify document completeness.
+Dispatch adopts a fully stateless file-driven design. Re-execute loop to recover: `get-batch` auto-recovers from file state; `process-results` handles uncleaned markers. The entire flow is safely re-entrant.
 
 ---
 
-## Error Handling Strategy
-
-| Stage | Failure Scenario | Handling | Retry |
-|-------|-----------------|----------|-------|
-| Stage 0 | Platform detection fails | Abort pipeline, report error | No retry |
-| Stage 1a | Entry directory recognition fails | Abort pipeline, report platform details | No retry |
-| Stage 1b | Script execution fails | Abort pipeline, report error | No retry |
-| Stage 1c | Feature merge fails | Abort pipeline, do not proceed to Stage 2 until resolved | No retry |
-| Stage 2 | Single Worker fails | Mark feature as `failed`, continue other Workers | No auto-retry |
-| Stage 2 | Failure rate > 50% | Abort pipeline, report all failures | — |
-| Stage 3 | Single Worker fails | Skip that module, continue others | Retry once |
-| Stage 3.5 | Pattern extraction fails | Continue pipeline, report warning | — |
-| Stage 4 | Worker fails | Abort, preserve all generated content | Retry once |
-
-**Failed Feature Handling**: Features marked as `failed` via `update-feature-status` script retain their error details in `features-{platform}.json` for manual inspection or re-run.
-
----
-
-## Task Completion Report Format
-
-Upon completing all stages, output the following structured report:
-
-```json
-{
-  "status": "success | partial | failed",
-  "skill": "speccrew-knowledge-bizs-dispatch-xml",
-  "stages_completed": ["stage_0", "stage_1a", "stage_1b", "stage_1c", "stage_2", "stage_3", "stage_3.5", "stage_4"],
-  "stages_failed": [],
-  "output_summary": {
-    "platforms_processed": ["web-vue", "backend-system"],
-    "features_analyzed": 32,
-    "modules_summarized": 8,
-    "ui_patterns_extracted": 15,
-    "system_overview_generated": true
-  },
-  "output_files": [
-    "knowledges/bizs/{platform}/{module}/features/*.md",
-    "knowledges/bizs/{platform}/{module}/*-overview.md",
-    "knowledges/techs/{platform_id}/ui-style-patterns/",
-    "knowledges/bizs/system-overview.md",
-    "knowledges/bizs/graph/"
-  ],
-  "errors": [],
-  "next_steps": ["Initialize techs knowledge base"]
-}
-```
-
----
-
-## Return Value Structure
-
-After all 5 stages complete, return a summary object to the caller:
-
-```json
-{
-  "status": "completed",
-  "pipeline": "bizs",
-  "stages": {
-    "stage0": { "status": "completed", "platforms": 2 },
-    "stage1a": { "status": "completed", "platforms": 2, "modules": 12 },
-    "stage1b": { "status": "completed", "platforms": 2, "features": 32 },
-    "stage1c": { "status": "completed", "mode": "full" },
-    "stage2": { "status": "completed", "analyzed": 32, "failed": 0, "graphWritten": 32 },
-    "stage3": { "status": "completed", "modules": 8, "failed": 0 },
-    "stage3_5": { "status": "completed", "platforms": 2, "patterns": 15 },
-    "stage4": { "status": "completed" }
-  },
-  "output": {
-    "system_overview": "{workspace_path}/knowledges/bizs/system-overview.md",
-    "graph_root": "{workspace_path}/knowledges/bizs/graph/"
-  }
-}
-```
-
----
-
-## CONTINUOUS EXECUTION RULES
-
-This skill MUST execute all stages continuously without unnecessary interruptions.
-
-### FORBIDDEN Interruptions
-
-1. DO NOT ask user "Should I continue?" after completing a stage
-2. DO NOT suggest "Let me split this into batches" or "Let's do this in parts"
-3. DO NOT pause to list what you plan to do next — just do it
-4. DO NOT ask for confirmation before generating output files
-5. DO NOT warn about "large number of files" — proceed with generation
-6. DO NOT offer "Should I proceed with the remaining items?"
-7. DO NOT present options like "Full execution / Sample execution / Pause"
-
-### When to Pause (ONLY these cases)
+### Large-Scale Scenario Guidance
 
-1. Explicit `<event action="confirm">` blocks in the workflow (e.g., Stage 0 platform confirmation)
-2. Ambiguous requirements that genuinely need clarification
-3. Unrecoverable errors that prevent further progress (failure rate > 50%)
-4. Security-sensitive operations (e.g., deleting existing files)
+For modules with >20 features: dispatch multiple Worker Agents in parallel (each handles a subset). Use `get-next-batch` for resume support across sessions. Run `process-batch-results --validateDocs` after completion to verify.
 
-### Batch Execution Behavior
 
-- When multiple features need processing, process ALL of them sequentially without asking
-- Use marker files (.done.json) to track progress, enabling resumption if interrupted by context limits
-- If context window is approaching limit, save progress to checkpoint and inform user how to resume
-- NEVER voluntarily stop mid-batch to ask if user wants to continue

package/.speccrew/skills/speccrew-knowledge-bizs-identify-entries-xml/SKILL.md

@@ -166,7 +166,9 @@ For each platform, generates:
         <branch test="${validation_result.status} == 'failed'">
           <block type="error-handler" id="EH1" desc="Handle validation failure">
             <catch error-type="validation_failed">
-              <block type="event" id="E1" action="log" level="warn" desc="Log validation failure">Entry directory recognition failed for platform ${platform.platformId}</block>
+              <block type="event" id="E1" action="log" level="warn" desc="Log validation failure">
+                <field name="message">Entry directory recognition failed for platform ${platform.platformId}</field>
+              </block>
               <block type="task" id="B7" action="analyze" desc="Re-analyze the directory tree due to validation failure">
                 <field name="input" value="${directory_tree}"/>
                 <field name="output" var="re_analyzed_entries"/>
@@ -175,7 +177,9 @@ For each platform, generates:
           </block>
         </branch>
         <branch test="${validation_result.status} == 'passed'">
-          <block type="event" id="E2" action="log" level="info" desc="Log validation success">Platform ${platform.platformId} entry-dirs validation passed</block>
+          <block type="event" id="E2" action="log" level="info" desc="Log validation success">
+            <field name="message">Platform ${platform.platformId} entry-dirs validation passed</field>
+          </block>
         </branch>
       </block>
 

package/.speccrew/skills/speccrew-knowledge-bizs-ui-analyze-xml/SKILL.md

@@ -133,7 +133,7 @@ Analyze one specific UI feature from source code, extract business functionality
     <block type="gateway" id="G0" mode="exclusive" desc="Check analyzed status">
       <branch test="${analyzed} == true" name="Already analyzed">
         <block type="event" id="E0a" action="log" level="info" desc="Skip already analyzed feature">
-Step 0 Status: SKIPPED (already analyzed)
+          <field name="message">Step 0 Status: SKIPPED (already analyzed)</field>
         </block>
         <block type="output" id="O0a" desc="Skip output">
           <field name="status" value="skipped"/>
@@ -145,7 +145,7 @@ Step 0 Status: SKIPPED (already analyzed)
       </branch>
       <branch test="${analyzed} == false" name="Proceed with analysis">
         <block type="event" id="E0b" action="log" level="info" desc="Proceed with analysis">
-Step 0 Status: PROCEEDING (analysis required)
+          <field name="message">Step 0 Status: PROCEEDING (analysis required)</field>
         </block>
       </branch>
     </block>
@@ -183,7 +183,7 @@ Step 0 Status: PROCEEDING (analysis required)
       <field name="verify" value="${templateContent} != null AND ${templateContent} != ''"/>
     </block>
     <block type="event" id="E1" action="log" level="info" desc="Log template read">
-Step 1 Status: COMPLETED - Read template for ${platform_type}/${platform_subtype}
+      <field name="message">Step 1 Status: COMPLETED - Read template for ${platform_type}/${platform_subtype}</field>
     </block>
   </sequence>
 
@@ -211,7 +211,7 @@ Step 1 Status: COMPLETED - Read template for ${platform_type}/${platform_subtype
       <field name="verify" value="${sourceContent} != null"/>
     </block>
     <block type="event" id="E2" action="log" level="info" desc="Log source analysis">
-Step 2 Status: COMPLETED - Read ${sourcePath}, Analyzed ${componentCount} components, ${eventCount} events
+      <field name="message">Step 2 Status: COMPLETED - Read ${sourcePath}, Analyzed ${componentCount} components, ${eventCount} events</field>
     </block>
   </sequence>
 
@@ -251,7 +251,7 @@ Step 2 Status: COMPLETED - Read ${sourcePath}, Analyzed ${componentCount} compon
       <field name="verify" value="${flows.length} > 0 OR ${wireframes.length} > 0"/>
     </block>
     <block type="event" id="E3" action="log" level="info" desc="Log feature extraction">
-Step 3 Status: COMPLETED - Extracted ${wireframes.length} wireframes, ${flows.length} business flows
+      <field name="message">Step 3 Status: COMPLETED - Extracted ${wireframes.length} wireframes, ${flows.length} business flows</field>
     </block>
   </sequence>
 
@@ -277,7 +277,7 @@ Step 3 Status: COMPLETED - Extracted ${wireframes.length} wireframes, ${flows.le
     </block>
 
     <block type="event" id="E4" action="log" level="info" desc="Log reference search">
-Step 4 Status: COMPLETED - Found ${referencingPages.length} referencing pages
+      <field name="message">Step 4 Status: COMPLETED - Found ${referencingPages.length} referencing pages</field>
     </block>
   </sequence>
 
@@ -301,7 +301,7 @@ Step 4 Status: COMPLETED - Found ${referencingPages.length} referencing pages
       <field name="verify" value="file.exists(${documentPath})"/>
     </block>
     <block type="event" id="E5a" action="log" level="info" desc="Log template copy">
-Step 5a Status: COMPLETED - Template copied to ${documentPath}
+      <field name="message">Step 5a Status: COMPLETED - Template copied to ${documentPath}</field>
     </block>
   </sequence>
 
@@ -367,14 +367,14 @@ Step 5a Status: COMPLETED - Template copied to ${documentPath}
       <field name="verify" value="all.sections.filled"/>
     </block>
     <block type="event" id="E5b" action="log" level="info" desc="Log section filling">
-Step 5b Status: COMPLETED - All sections filled using search_replace
+      <field name="message">Step 5b Status: COMPLETED - All sections filled using search_replace</field>
     </block>
   </sequence>
 
   <!-- ==================== STEP 6: REPORT RESULTS ==================== -->
   <sequence id="S6" name="Step 6: Report Results" status="pending" desc="Report analysis results">
     <block type="event" id="E6" action="log" level="info" desc="Log final status">
-Step 6 Status: COMPLETED - Analysis success: Successfully analyzed ${fileName} feature from ${sourcePath}
+      <field name="message">Step 6 Status: COMPLETED - Analysis success: Successfully analyzed ${fileName} feature from ${sourcePath}</field>
     </block>
   </sequence>
 
@@ -395,28 +395,28 @@ Step 6 Status: COMPLETED - Analysis success: Successfully analyzed ${fileName} f
     </try>
     <catch error-type="file-not-found">
       <block type="event" id="EH1-E1" action="log" level="error" desc="File not found error">
-Source file not found: ${sourcePath}
+        <field name="message">Source file not found: ${sourcePath}</field>
       </block>
       <field name="status" value="failed"/>
       <field name="message" value="Source file not found: ${sourcePath}"/>
     </catch>
     <catch error-type="template-error">
       <block type="event" id="EH1-E2" action="log" level="error" desc="Template error">
-Template processing error
+        <field name="message">Template processing error</field>
       </block>
       <field name="status" value="failed"/>
       <field name="message" value="Failed to process template"/>
     </catch>
     <catch error-type="validation-error">
       <block type="event" id="EH1-E3" action="log" level="error" desc="Validation error">
-Validation failed: ${error.message}
+        <field name="message">Validation failed: ${error.message}</field>
       </block>
       <field name="status" value="partial"/>
       <field name="message" value="Analysis completed with validation errors"/>
     </catch>
     <finally>
       <block type="event" id="EH1-E4" action="log" level="info" desc="Workflow completed">
-Workflow execution completed
+        <field name="message">Workflow execution completed</field>
       </block>
     </finally>
   </block>