speccrew 0.6.46 → 0.6.48

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

@@ -102,7 +102,7 @@ This skill automatically adapts to the user's input language. All documentation
     </block>
 
     <block type="event" id="E1" action="log" level="info" desc="Log Step 1 completion">
-Step 1 Status: COMPLETED - Read ${sourcePath}, found ${apiImports.count} APIs, ${componentUsage.count} components, ${navigationPatterns.count} navigations
+      <field name="message">Step 1 Status: COMPLETED - Read ${sourcePath}, found ${apiImports.count} APIs, ${componentUsage.count} components, ${navigationPatterns.count} navigations</field>
     </block>
 
     <block type="checkpoint" id="CP1" name="step-1-read-source" desc="Source file read complete">
@@ -143,7 +143,7 @@ Step 1 Status: COMPLETED - Read ${sourcePath}, found ${apiImports.count} APIs, $
     </block>
 
     <block type="event" id="E2" action="log" level="info" desc="Log Step 2 completion">
-Step 2 Status: COMPLETED - Constructed ${nodeCount} nodes
+      <field name="message">Step 2 Status: COMPLETED - Constructed ${nodeCount} nodes</field>
     </block>
 
     <block type="checkpoint" id="CP2" name="step-2-construct-nodes" desc="Graph nodes constructed">
@@ -193,7 +193,7 @@ Step 2 Status: COMPLETED - Constructed ${nodeCount} nodes
     </block>
 
     <block type="event" id="E3" action="log" level="info" desc="Log Step 3 completion">
-Step 3 Status: COMPLETED - Constructed ${edgeCount} edges (${apiEdges.count} API calls, ${navEdges.count} navigations, ${useEdges.count} component uses)
+      <field name="message">Step 3 Status: COMPLETED - Constructed ${edgeCount} edges (${apiEdges.count} API calls, ${navEdges.count} navigations, ${useEdges.count} component uses)</field>
     </block>
 
     <block type="checkpoint" id="CP3" name="step-3-construct-edges" desc="Graph edges constructed">
@@ -232,7 +232,7 @@ Step 3 Status: COMPLETED - Constructed ${edgeCount} edges (${apiEdges.count} API
     </block>
 
     <block type="event" id="E4" action="log" level="info" desc="Log Step 4 completion">
-Step 4 Status: COMPLETED - Graph JSON written to ${completed_dir}/${markerFilename}.graph.json
+      <field name="message">Step 4 Status: COMPLETED - Graph JSON written to ${completed_dir}/${markerFilename}.graph.json</field>
     </block>
 
     <block type="checkpoint" id="CP4" name="step-4-write-graph-json" desc="Graph JSON written">
@@ -265,7 +265,7 @@ Step 4 Status: COMPLETED - Graph JSON written to ${completed_dir}/${markerFilena
     </block>
 
     <block type="event" id="E5" action="log" level="info" desc="Log Step 5 completion">
-Step 5 Status: COMPLETED - Graph completion marker written to ${completed_dir}/${markerFilename}.graph-done.json
+      <field name="message">Step 5 Status: COMPLETED - Graph completion marker written to ${completed_dir}/${markerFilename}.graph-done.json</field>
     </block>
 
     <block type="checkpoint" id="CP5" name="step-5-write-marker" desc="Completion marker written">

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

@@ -115,7 +115,9 @@ Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature
        ============================================================ -->
   <block type="gateway" id="G1" mode="exclusive" desc="Check platform type for UI pattern extraction">
     <branch test="${platform_type} NOT IN ['web', 'mobile', 'desktop']" name="Backend platform">
-      <block type="event" id="E1" action="log" level="info" desc="Log skip reason">Skipping skill: backend platforms do not have UI patterns</block>
+      <block type="event" id="E1" action="log" level="info" desc="Log skip reason">
+        <field name="message">Skipping skill: backend platforms do not have UI patterns</field>
+      </block>
       <block type="task" id="B1" action="analyze" desc="Return skip status">
         <field name="status" value="skipped"/>
         <field name="reason" value="Backend platform does not have UI patterns"/>
@@ -210,7 +212,9 @@ Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature
                ============================================================ -->
           <block type="gateway" id="G3" mode="exclusive" desc="Check if patterns were identified">
             <branch test="${identified_patterns.length} == 0" name="No patterns">
-              <block type="event" id="E2" action="log" level="warn" desc="Log no patterns">No patterns identified from feature documents</block>
+              <block type="event" id="E2" action="log" level="warn" desc="Log no patterns">
+                <field name="message">No patterns identified from feature documents</field>
+              </block>
               <block type="task" id="B8" action="analyze" desc="Return empty result">
                 <field name="status" value="completed"/>
                 <field name="platform_id" value="${platform_id}"/>
@@ -299,7 +303,9 @@ Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature
 
         </branch>
         <branch test="${completed_features.length} == 0" name="No completed features">
-          <block type="event" id="E3" action="log" level="warn" desc="Log no features">No completed features found - returning empty result</block>
+          <block type="event" id="E3" action="log" level="warn" desc="Log no features">
+            <field name="message">No completed features found - returning empty result</field>
+          </block>
           <block type="task" id="B15" action="analyze" desc="Return empty summary">
             <field name="status" value="completed"/>
             <field name="platform_id" value="${platform_id}"/>

package/.speccrew/skills/speccrew-knowledge-module-summarize-xml/SKILL.md

@@ -108,7 +108,7 @@ flowchart TD
     <block type="gateway" id="G1" mode="exclusive" desc="Check if features exist">
       <branch test="${feature_files.length} == 0" name="No features">
         <block type="event" id="E1a" action="log" level="warning" desc="No features warning">
-No feature documents found for module ${module_name}
+          <field name="message">No feature documents found for module ${module_name}</field>
         </block>
         <block type="task" id="B1e" action="write-file" desc="Generate minimal overview">
           <field name="path" value="${module_path}/${module_name}-overview.md"/>
@@ -116,12 +116,12 @@ No feature documents found for module ${module_name}
         </block>
         <field name="status" value="partial"/>
         <block type="event" id="E1b" action="signal" desc="Signal complete">
-workflow_complete
+          <field name="message">workflow_complete</field>
         </block>
       </branch>
       <branch test="${feature_files.length} > 0" name="Features found">
         <block type="event" id="E1c" action="log" level="info" desc="Features found">
-Found ${feature_files.length} feature documents
+          <field name="message">Found ${feature_files.length} feature documents</field>
         </block>
       </branch>
     </block>
@@ -308,13 +308,13 @@ Found ${feature_files.length} feature documents
       </try>
       <catch error-type="write_error">
         <block type="event" id="EH1-E1" action="log" level="error" desc="Write error">
-Failed to write overview document: ${write_error.message}
+          <field name="message">Failed to write overview document: ${write_error.message}</field>
         </block>
         <field name="status" value="failed"/>
       </catch>
       <finally>
         <block type="event" id="EH1-E2" action="log" level="info" desc="Write completed">
-Document write operation completed
+          <field name="message">Document write operation completed</field>
         </block>
       </finally>
     </block>
@@ -351,14 +351,14 @@ Document write operation completed
 
     <!-- Event: Log completion -->
     <block type="event" id="E6" action="log" level="info" desc="Log completion">
-Module summarization completed:
+      <field name="message">Module summarization completed:
 - Module: ${module_name}
 - Features Processed: ${feature_files.length}
 - Entities Extracted: ${unique_entities.length}
 - Dependencies Identified: ${dependencies.length}
 - Business Rules Summarized: ${business_rules.length}
 - Output: ${module_name}-overview.md (complete)
-- Status: success
+- Status: success</field>
     </block>
   </sequence>
 

package/.speccrew/skills/speccrew-knowledge-system-summarize-xml/SKILL.md

@@ -97,7 +97,7 @@ flowchart TD
 
   <!-- Prerequisites Verification -->
   <block type="event" id="E1" action="log" level="info" desc="Log workflow start">
-Starting system summarization workflow
+    <field name="message">Starting system summarization workflow</field>
   </block>
 
   <!-- Step 0: Read System Overview Template -->
@@ -123,7 +123,7 @@ Starting system summarization workflow
   <block type="gateway" id="G1" mode="exclusive" desc="Check if modules discovered">
     <branch test="${module_files.length} == 0" name="No modules">
       <block type="event" id="E2" action="log" level="warning" desc="Log no modules found">
-No module overview files found in ${modules_path}
+        <field name="message">No module overview files found in ${modules_path}</field>
       </block>
       <block type="task" id="B2" action="run-script" desc="Generate skeleton document">
         <field name="script" value="generate-skeleton.js"/>
@@ -144,7 +144,7 @@ No module overview files found in ${modules_path}
     </branch>
     <branch test="${module_files.length} > 0" name="Modules found">
       <block type="event" id="E4" action="log" level="info" desc="Log modules discovered">
-Discovered ${module_files.length} module overview files
+        <field name="message">Discovered ${module_files.length} module overview files</field>
       </block>
     </branch>
   </block>
@@ -355,7 +355,7 @@ Discovered ${module_files.length} module overview files
         <field name="output" var="timestamp"/>
       </block>
       <block type="event" id="E5" action="log" level="warning" desc="Log fallback">
-Using system fallback timestamp
+        <field name="message">Using system fallback timestamp</field>
       </block>
     </branch>
   </block>
@@ -464,7 +464,7 @@ Using system fallback timestamp
     </try>
     <catch error-type="write_error">
       <block type="event" id="E6" action="log" level="error" desc="Log write error">
-Failed to write system overview: ${write_error.message}
+        <field name="message">Failed to write system overview: ${write_error.message}</field>
       </block>
       <block type="output" id="O-err" desc="Error output">
         <field name="status" value="failed"/>
@@ -472,7 +472,7 @@ Failed to write system overview: ${write_error.message}
     </catch>
     <finally>
       <block type="event" id="E7" action="log" level="info" desc="Log write complete">
-Document write operation completed
+        <field name="message">Document write operation completed</field>
       </block>
     </finally>
   </block>
@@ -513,14 +513,14 @@ Document write operation completed
 
   <!-- Event: Log completion -->
   <block type="event" id="E8" action="log" level="info" desc="Log completion summary">
-    System summarization completed:
+    <field name="message">System summarization completed:
     - Modules Processed: ${module_count}
     - Entities Aggregated: ${metrics.entity_count}
     - APIs Counted: ${metrics.api_count}
     - Dependencies Mapped: ${all_dependencies.length}
     - Business Flows Identified: ${flow_count}
     - Output: system-overview.md (complete)
-    - Status: success
+    - Status: success</field>
   </block>
 
   <!-- Output Block: Define workflow outputs -->

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

@@ -191,10 +191,10 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
 
     <!-- Step 2: Prepare Task Plan for techs-init -->
     <block type="event" id="S1-E1" action="log" level="info" desc="Prepare techs-init task plan">
-Stage 1: Preparing task plan for speccrew-knowledge-techs-init-xml
+    <field name="message">Stage 1: Preparing task plan for speccrew-knowledge-techs-init-xml
 - Source path: ${source_path}
 - Output path: ${sync_state_techs_dir}
-- Language: ${language}
+- Language: ${language}</field>
     </block>
 
     <!-- Step 3: Prepare task specification -->
@@ -210,9 +210,9 @@ Stage 1: Preparing task plan for speccrew-knowledge-techs-init-xml
 
     <!-- Step 4: Monitor completion -->
     <block type="event" id="S1-E2" action="log" level="info" desc="Stage 1 task prepared">
-Stage 1 task plan prepared. Waiting for calling Agent to dispatch.
+    <field name="message">Stage 1 task plan prepared. Waiting for calling Agent to dispatch.
 Task: speccrew-knowledge-techs-init-xml
-Output: ${sync_state_techs_dir}/techs-manifest.json
+Output: ${sync_state_techs_dir}/techs-manifest.json</field>
     </block>
 
     <!-- Step 5: Read manifest after completion -->
@@ -233,7 +233,7 @@ Output: ${sync_state_techs_dir}/techs-manifest.json
     </block>
 
     <block type="event" id="S1-E3" action="log" level="info" desc="Report detected platforms">
-Stage 1 complete. Detected ${techs_manifest.platforms.length} platforms: ${techs_manifest.platforms.map(p => p.platform_id).join(', ')}
+    <field name="message">Stage 1 complete. Detected ${techs_manifest.platforms.length} platforms: ${techs_manifest.platforms.map(p => p.platform_id).join(', ')}</field>
     </block>
   </sequence>
 
@@ -284,7 +284,7 @@ if (platform) {
 
     <!-- Step 2: Prepare Conventions Worker Task Plans (ALL Platforms) -->
     <block type="event" id="S2-E1" action="log" level="info" desc="Prepare conventions worker tasks">
-Preparing conventions worker task plans for ${techs_manifest.platforms.length} platforms...
+    <field name="message">Preparing conventions worker task plans for ${techs_manifest.platforms.length} platforms...</field>
     </block>
 
     <block type="loop" id="S2-L2" over="${techs_manifest.platforms}" as="platform" desc="Prepare conventions worker task for each platform">
@@ -307,7 +307,7 @@ Preparing conventions worker task plans for ${techs_manifest.platforms.length} p
 
     <!-- Step 3: Prepare UI-Style Worker Task Plans (Frontend Platforms ONLY) -->
     <block type="event" id="S2-E2" action="log" level="info" desc="Prepare UI-style worker tasks">
-Preparing UI-style worker task plans for frontend platforms...
+    <field name="message">Preparing UI-style worker task plans for frontend platforms...</field>
     </block>
 
     <block type="loop" id="S2-L3" over="${techs_manifest.platforms}" as="platform" desc="Prepare UI-style worker task for frontend platforms">
@@ -331,7 +331,7 @@ Preparing UI-style worker task plans for frontend platforms...
 
     <!-- Step 4: Dispatch ALL Workers in PARALLEL -->
     <block type="event" id="S2-E3" action="log" level="info" desc="Dispatch all workers">
-Dispatching ALL workers in PARALLEL. The calling Agent should dispatch all prepared tasks simultaneously.
+    <field name="message">Dispatching ALL workers in PARALLEL. The calling Agent should dispatch all prepared tasks simultaneously.</field>
     </block>
 
     <!-- Step 5: Monitor Completion Markers -->
@@ -410,7 +410,7 @@ Dispatching ALL workers in PARALLEL. The calling Agent should dispatch all prepa
     </block>
 
     <block type="event" id="S2-E4" action="log" level="info" desc="Stage 2 complete">
-Stage 2 complete. All platform workers finished.
+    <field name="message">Stage 2 complete. All platform workers finished.</field>
     </block>
   </sequence>
 
@@ -427,7 +427,7 @@ Stage 2 complete. All platform workers finished.
 
     <!-- Step A: Scan Completion Markers -->
     <block type="event" id="S2_5-E1" action="log" level="info" desc="Step A: Scan completion markers">
-Stage 2.5 Step A: Scanning completion markers...
+    <field name="message">Stage 2.5 Step A: Scanning completion markers...</field>
     </block>
 
     <block type="loop" id="S2_5-L1" over="${techs_manifest.platforms}" as="platform" desc="Scan markers for each platform">
@@ -453,7 +453,7 @@ console.log(JSON.stringify(markers));
 
     <!-- Step B: Verify Output Integrity -->
     <block type="event" id="S2_5-E2" action="log" level="info" desc="Step B: Verify output integrity">
-Stage 2.5 Step B: Verifying output integrity...
+    <field name="message">Stage 2.5 Step B: Verifying output integrity...</field>
     </block>
 
     <block type="loop" id="S2_5-L2" over="${techs_manifest.platforms}" as="platform" desc="Verify documents for each platform">
@@ -497,7 +497,7 @@ console.log(JSON.stringify(results));
 
     <!-- Step C: Update Progress Status -->
     <block type="event" id="S2_5-E3" action="log" level="info" desc="Step C: Update progress status">
-Stage 2.5 Step C: Updating progress status...
+    <field name="message">Stage 2.5 Step C: Updating progress status...</field>
     </block>
 
     <block type="task" id="S2_5-B3" action="run-script" status="pending" desc="Generate stage2-status.json">
@@ -531,7 +531,7 @@ console.log('stage2-status.json written');
     </block>
 
     <block type="event" id="S2_5-E4" action="log" level="info" desc="Stage 2.5 complete">
-Stage 2.5 complete. Verification results written to stage2-status.json.
+    <field name="message">Stage 2.5 complete. Verification results written to stage2-status.json.</field>
     </block>
   </sequence>
 
@@ -554,10 +554,10 @@ Stage 2.5 complete. Verification results written to stage2-status.json.
 
     <!-- Step 2: Prepare Task Plan for techs-index -->
     <block type="event" id="S3-E1" action="log" level="info" desc="Prepare techs-index task plan">
-Stage 3: Preparing task plan for speccrew-knowledge-techs-index-xml
+    <field name="message">Stage 3: Preparing task plan for speccrew-knowledge-techs-index-xml
 - Manifest: ${sync_state_techs_dir}/techs-manifest.json
 - Output: ${workspace_path}/knowledges/techs/
-- Language: ${language}
+- Language: ${language}</field>
     </block>
 
     <!-- Step 3: Prepare task specification -->
@@ -574,9 +574,9 @@ Stage 3: Preparing task plan for speccrew-knowledge-techs-index-xml
 
     <!-- Step 4: Monitor completion -->
     <block type="event" id="S3-E2" action="log" level="info" desc="Stage 3 task prepared">
-Stage 3 task plan prepared. Waiting for calling Agent to dispatch.
+    <field name="message">Stage 3 task plan prepared. Waiting for calling Agent to dispatch.
 Task: speccrew-knowledge-techs-index-xml
-Output: ${workspace_path}/knowledges/techs/INDEX.md
+Output: ${workspace_path}/knowledges/techs/INDEX.md</field>
     </block>
 
     <!-- Step 5: Generate stage3-status.json -->
@@ -605,7 +605,7 @@ console.log('stage3-status.json written');
     </block>
 
     <block type="event" id="S3-E3" action="log" level="info" desc="Stage 3 complete">
-Stage 3 complete. Root INDEX.md generated.
+    <field name="message">Stage 3 complete. Root INDEX.md generated.</field>
     </block>
   </sequence>
 
@@ -624,11 +624,13 @@ Stage 3 complete. Root INDEX.md generated.
 
 ---
 
-## Worker Completion Marker Format
+## Appendix: Reference
+
+### Worker Completion Marker Format
 
 Each Worker MUST create a completion marker file after generating documents.
 
-### Conventions Worker Done File
+#### Conventions Worker Done File
 
 **File**: `{completed_dir}/{platform_id}.done-conventions.json`
 
@@ -648,7 +650,7 @@ Each Worker MUST create a completion marker file after generating documents.
 }
 ```
 
-### UI-Style Worker Done File
+#### UI-Style Worker Done File
 
 **File**: `{completed_dir}/{platform_id}.done-ui-style.json`
 
@@ -673,7 +675,7 @@ Each Worker MUST create a completion marker file after generating documents.
 
 If a Worker encounters a fatal error, it should still attempt to create the done file with `status: "failed"` and include error details in an `"error"` field.
 
-### Quality Worker Done File
+#### Quality Worker Done File
 
 **File**: `{completed_dir}/{platform_id}.quality-done.json`
 
@@ -691,7 +693,7 @@ If a Worker encounters a fatal error, it should still attempt to create the done
 
 ---
 
-## Platform Status Tracking Fields
+### Platform Status Tracking Fields
 
 Each platform entry in techs-manifest.json includes status tracking fields for monitoring the analysis pipeline progress:
 
@@ -735,7 +737,7 @@ pending → processing → completed
 
 ---
 
-## Output per Platform
+### Output per Platform
 
 ```
 speccrew-workspace/knowledges/techs/{platform_id}/
@@ -773,9 +775,9 @@ speccrew-workspace/knowledges/techs/{platform_id}/
 
 ---
 
-## Error Handling
+### Error Handling
 
-### Error Handling Strategy
+#### Error Handling Strategy
 
 ```
 ON Worker Failure:
@@ -788,7 +790,7 @@ ON Worker Failure:
      - IF some platforms succeeded → CONTINUE to Stage 3 with successful platforms only
 ```
 
-### Stage-Level Failure Handling
+#### Stage-Level Failure Handling
 
 | Stage | Failure Handling |
 |-------|-----------------|
@@ -797,7 +799,7 @@ ON Worker Failure:
 | Stage 2.5 | Continue pipeline, report warnings |
 | Stage 3 | Abort if Stage 2 had critical failures |
 
-### Worker Failure Details
+#### Worker Failure Details
 
 **When a Worker Agent fails:**
 - **No automatic retry**: Worker failures are recorded as-is
@@ -807,7 +809,7 @@ ON Worker Failure:
 
 ---
 
-## Checklist
+### Checklist
 
 - [ ] Stage 1: Platform manifest generated with techs-manifest.json
 - [ ] Stage 2: All platforms processed in parallel
@@ -815,89 +817,9 @@ ON Worker Failure:
 - [ ] Stage 3: Root INDEX.md generated with Agent mapping
 - [ ] Stage 3: `stage3-status.json` generated with index info
 
-### Document Completeness Verification
+#### Document Completeness Verification
 - [ ] Each platform directory contains required documents: INDEX.md, tech-stack.md, architecture.md, conventions-design.md, conventions-dev.md, conventions-unit-test.md, conventions-system-test.md, conventions-build.md
 - [ ] `conventions-data.md` exists only for appropriate platforms (backend required, others optional)
 - [ ] All documents include file reference blocks (pure Markdown format for VS Code preview compatibility)
 - [ ] All documents include AI-TAG and AI-CONTEXT comments
 - [ ] techs/INDEX.md links only to existing documents
-
----
-
-## Task Completion Report Format
-
-Upon completing all stages, output the following structured report:
-
-```json
-{
-  "status": "success | partial | failed",
-  "skill": "speccrew-knowledge-techs-dispatch-xml",
-  "stages_completed": ["stage_1", "stage_2", "stage_2_5", "stage_3"],
-  "stages_failed": [],
-  "output_summary": {
-    "platforms_processed": ["frontend", "backend"],
-    "docs_generated_per_platform": {"frontend": 5, "backend": 4},
-    "root_index_generated": true,
-    "cross_platform_check_passed": true
-  },
-  "output_files": [
-    "knowledges/techs/{platform}/README.md",
-    "knowledges/techs/{platform}/conventions.md",
-    "knowledges/techs/README.md"
-  ],
-  "errors": [],
-  "next_steps": ["Review generated tech documentation"]
-}
-```
-
----
-
-## Return Value Structure
-
-After all 3 stages complete, return a summary object to the caller:
-
-```json
-{
-  "status": "completed",
-  "pipeline": "techs",
-  "stages": {
-    "stage1": { "status": "completed", "platforms": 3 },
-    "stage2": { "status": "completed", "completed": 3, "failed": 0 },
-    "stage3": { "status": "completed" }
-  },
-  "output": {
-    "index": "speccrew-workspace/knowledges/techs/INDEX.md",
-    "manifest": "speccrew-workspace/knowledges/base/sync-state/knowledge-techs/techs-manifest.json"
-  }
-}
-```
-
----
-
-## 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)
-
-1. Explicit `<event action="confirm">` blocks in the workflow (e.g., platform confirmation if needed)
-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)
-
-### Batch Execution Behavior
-
-- When multiple platforms need processing, process ALL of them 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-techs-generate-quality-xml/SKILL.md

@@ -177,7 +177,7 @@ Worker Agent (speccrew-task-worker)
   </block>
 
   <block type="event" id="E2" action="log" level="info" desc="Completeness check result">
-Completeness check: ${completeness_result.documents_found}/${completeness_result.documents_expected} documents, ${completeness_result.sections_passed}/${completeness_result.sections_checked} sections
+    <field name="message">Completeness check: ${completeness_result.documents_found}/${completeness_result.documents_expected} documents, ${completeness_result.sections_passed}/${completeness_result.sections_checked} sections</field>
   </block>
 
   <block type="checkpoint" id="CP2" name="completeness_checked" desc="Completeness check complete">
@@ -227,7 +227,7 @@ Completeness check: ${completeness_result.documents_found}/${completeness_result
   </block>
 
   <block type="event" id="E3" action="log" level="info" desc="Cross-validation result">
-Cross-validation: ${cross_validation_result.version_checks.passed}/${cross_validation_result.version_checks.total} version checks, ${cross_validation_result.reference_checks.passed}/${cross_validation_result.reference_checks.total} reference checks
+    <field name="message">Cross-validation: ${cross_validation_result.version_checks.passed}/${cross_validation_result.version_checks.total} version checks, ${cross_validation_result.reference_checks.passed}/${cross_validation_result.reference_checks.total} reference checks</field>
   </block>
 
   <block type="checkpoint" id="CP3" name="cross_validation_complete" desc="Cross-validation complete">
@@ -277,7 +277,7 @@ Cross-validation: ${cross_validation_result.version_checks.passed}/${cross_valid
   </block>
 
   <block type="event" id="E4" action="log" level="info" desc="Consistency check result">
-Consistency: ${consistency_result.status} - ${consistency_result.issues.length} issues found
+    <field name="message">Consistency: ${consistency_result.status} - ${consistency_result.issues.length} issues found</field>
   </block>
 
   <block type="checkpoint" id="CP4" name="consistency_checked" desc="Consistency check complete">
@@ -330,7 +330,7 @@ Consistency: ${consistency_result.status} - ${consistency_result.issues.length}
   </block>
 
   <block type="event" id="E5" action="log" level="info" desc="Source traceability result">
-Source Traceability: ${traceability_result.documents_with_cite_block}/${traceability_result.documents_total} documents with cite blocks, ${traceability_result.absolute_paths_found} absolute paths, ${traceability_result.file_protocol_found} file:// protocols
+    <field name="message">Source Traceability: ${traceability_result.documents_with_cite_block}/${traceability_result.documents_total} documents with cite blocks, ${traceability_result.absolute_paths_found} absolute paths, ${traceability_result.file_protocol_found} file:// protocols</field>
   </block>
 
   <block type="checkpoint" id="CP5" name="traceability_checked" desc="Source traceability check complete">
@@ -376,7 +376,7 @@ Source Traceability: ${traceability_result.documents_with_cite_block}/${traceabi
   </block>
 
   <block type="event" id="E6" action="log" level="info" desc="Mermaid compatibility result">
-Mermaid Compatibility: ${mermaid_result.diagrams_passed}/${mermaid_result.diagrams_checked} diagrams passed, ${mermaid_result.issues.length} issues found
+    <field name="message">Mermaid Compatibility: ${mermaid_result.diagrams_passed}/${mermaid_result.diagrams_checked} diagrams passed, ${mermaid_result.issues.length} issues found</field>
   </block>
 
   <block type="checkpoint" id="CP6" name="mermaid_checked" desc="Mermaid compatibility check complete">
@@ -474,7 +474,7 @@ Mermaid Compatibility: ${mermaid_result.diagrams_passed}/${mermaid_result.diagra
   </block>
 
   <block type="event" id="E8" action="log" level="info" desc="Quality check complete">
-Quality check complete for {platform_id}
+    <field name="message">Quality check complete for {platform_id}
 - Total Checks: ${quality_report.summary.total_checks}
 - Passed: ${quality_report.summary.passed}
 - Warnings: ${quality_report.summary.warnings}
@@ -486,7 +486,7 @@ Quality check complete for {platform_id}
 - Cross-Validation: ${quality_report.cross_validation.status}
 - Consistency: ${quality_report.consistency.status}
 - Source Traceability: ${quality_report.source_traceability.status}
-- Mermaid Compatibility: ${quality_report.mermaid_compatibility.status}
+- Mermaid Compatibility: ${quality_report.mermaid_compatibility.status}</field>
   </block>
 
   <!-- ============================================================
@@ -515,7 +515,7 @@ Quality check complete for {platform_id}
     </try>
     <catch on="platform_dir_not_found">
       <block type="event" id="EH1-E1" action="log" level="error" desc="Platform directory not found">
-Platform directory not found: {platform_dir}
+        <field name="message">Platform directory not found: {platform_dir}</field>
       </block>
       <block type="output" id="EH1-O1">
         <field name="status" value="failed"/>
@@ -524,20 +524,20 @@ Platform directory not found: {platform_dir}
     </catch>
     <catch on="required_document_missing">
       <block type="event" id="EH1-E2" action="log" level="warn" desc="Required document missing">
-Required document missing: {missing_document}
+        <field name="message">Required document missing: {missing_document}</field>
       </block>
       <field name="continue" value="true"/>
       <field name="record_in" value="completeness.documents_missing"/>
     </catch>
     <catch on="analysis_report_missing">
       <block type="event" id="EH1-E3" action="log" level="warn" desc="Analysis report missing">
-Analysis report missing, skipping cross-validation with source
+        <field name="message">Analysis report missing, skipping cross-validation with source</field>
       </block>
       <field name="continue" value="true"/>
     </catch>
     <catch on="mermaid_parsing_error">
       <block type="event" id="EH1-E4" action="log" level="warn" desc="Mermaid parsing error">
-Mermaid parsing error in {diagram_location}
+        <field name="message">Mermaid parsing error in {diagram_location}</field>
       </block>
       <field name="continue" value="true"/>
       <field name="record_in" value="mermaid_compatibility.issues"/>