speccrew 0.6.69 → 0.7.0

package/.speccrew/skills/{speccrew-knowledge-bizs-ui-analyze-xml/SKILL.md → speccrew-knowledge-bizs-ui-analyze/workflow.agentflow.xml}

@@ -1,85 +1,4 @@
----
-name: speccrew-knowledge-bizs-ui-analyze-xml
-description: Analyze a single UI feature from source code to extract business functionality and generate feature documentation using XML Block workflow. Used by Worker Agent in parallel execution during knowledge base initialization Stage 2. Each worker analyzes one feature (e.g., one Vue/React page component).
-tools: Read, Write, Edit, Glob, Grep, Bash
----
-
-# UI Feature Analysis - Single Feature (XML Block Workflow)
-
-> **CRITICAL CONSTRAINT**: DO NOT create temporary scripts, batch files, or workaround code files (`.py`, `.bat`, `.sh`, `.ps1`, etc.) under any circumstances. If execution encounters errors, STOP and report the exact error. Fixes must be applied to the Skill definition or source scripts — not patched at runtime.
-
-Analyze one specific UI feature from source code, extract business functionality, and generate feature documentation. This skill operates at feature granularity - one worker per feature file.
-
-## Trigger Scenarios
-
-- "Analyze feature {fileName} from source code"
-- "Extract UI functionality from feature {fileName}"
-- "Generate documentation for feature {fileName}"
-- "Analyze UI feature from features.json"
-
-## Input Variables
-
-| Variable | Type | Description | Example |
-|----------|------|-------------|---------|
-| `{{feature}}` | object | Complete feature object from features.json | - |
-| `{{fileName}}` | string | Feature file name | `"index"`, `"UserForm"` |
-| `{{sourcePath}}` | string | Relative path to source file | `"frontend-web/src/views/system/user/index.vue"` |
-| `{{documentPath}}` | string | Target path for generated document | `"speccrew-workspace/knowledges/bizs/web-vue/src/views/system/user/index.md"` |
-| `{{module}}` | string | Business module name (from feature.module) | `"system"`, `"trade"`, `"_root"` |
-| `{{analyzed}}` | boolean | Analysis status flag | `true` / `false` |
-| `{{platform_type}}` | string | Platform type | `"web"`, `"mobile"` |
-| `{{platform_subtype}}` | string | Platform subtype | `"vue"`, `"react"` |
-| `{{tech_stack}}` | array | Platform tech stack | `["vue", "typescript"]` |
-| `{{language}}` | string | **REQUIRED** - Target language for generated content | `"zh"`, `"en"` |
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `{{language}}` parameter.
-
-- `{{language}} == "zh"` → Generate all content in 中文
-- `{{language}} == "en"` → Generate all content in English
-- Other languages → Use the specified language
-
-**All output content (feature names, descriptions, business rules) must be in the target language only.**
-
-## Output Variables
-
-| Variable | Type | Description |
-|----------|------|-------------|
-| `{{status}}` | string | Analysis status: `"success"`, `"partial"`, or `"failed"` |
-| `{{feature_name}}` | string | Name of the analyzed feature |
-| `{{generated_file}}` | string | Path to the generated documentation file |
-| `{{message}}` | string | Summary message for status update |
-
-## Output
-
-**Generated Files (MANDATORY - Task is NOT complete until all files are written):**
-1. `{{documentPath}}` - Feature documentation file
-
-**Return Value (JSON format):**
-```json
-{
-  "status": "success|partial|failed",
-  "feature": {
-    "fileName": "index",
-    "sourcePath": "frontend-web/src/views/system/user/index.vue"
-  },
-  "platformType": "web",
-  "module": "system",
-  "featureName": "user-management",
-  "generatedFile": "speccrew-workspace/knowledges/bizs/web-vue/src/views/system/user/index.md",
-  "message": "Successfully analyzed user-management feature from index.vue"
-}
-```
-
-> **Note**: Graph data (.graph.json) is handled by `speccrew-knowledge-bizs-ui-graph` Skill. This Skill generates feature documentation AND writes `.done.json` completion marker.
-
-## Workflow
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="UTF-8"?>
 <workflow id="ui-feature-analysis" version="1.0" status="pending" desc="UI feature analysis workflow">
 
   <!-- ==================== INPUT PARAMETERS ==================== -->
@@ -121,13 +40,13 @@ Analyze one specific UI feature from source code, extract business functionality
   </block>
 
   <!-- ==================== GLOBAL CONTINUOUS EXECUTION RULES ==================== -->
-  <block type="rule" id="GLOBAL-R1" level="forbidden" desc="Continuous execution constraints — NEVER violate">
+  <block type="rule" id="GLOBAL-R1" level="forbidden" desc="Continuous execution constraints 鈥?NEVER violate">
     <field name="text">DO NOT ask user "Should I continue?" or "How would you like to proceed?" during execution</field>
-    <field name="text">DO NOT offer options like "Full execution / Partial / Stop" — always execute ALL tasks to completion</field>
-    <field name="text">DO NOT suggest "Due to context window limits, let me pause" — complete current task, use checkpoint for resumption</field>
-    <field name="text">DO NOT estimate workload and suggest breaking it into phases — execute ALL items in sequence</field>
-    <field name="text">DO NOT warn about "large number of files" or "this may take a while" — proceed with generation</field>
-    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume — do NOT ask user for guidance</field>
+    <field name="text">DO NOT offer options like "Full execution / Partial / Stop" 鈥?always execute ALL tasks to completion</field>
+    <field name="text">DO NOT suggest "Due to context window limits, let me pause" 鈥?complete current task, use checkpoint for resumption</field>
+    <field name="text">DO NOT estimate workload and suggest breaking it into phases 鈥?execute ALL items in sequence</field>
+    <field name="text">DO NOT warn about "large number of files" or "this may take a while" 鈥?proceed with generation</field>
+    <field name="text">Context window management: if approaching limit, save progress to checkpoint file and resume 鈥?do NOT ask user for guidance</field>
   </block>
 
   <!-- ==================== STEP 0: CHECK ANALYSIS STATUS ==================== -->
@@ -329,7 +248,7 @@ Analyze one specific UI feature from source code, extract business functionality
     <field name="text">Step 1: Copy template skeleton to target path</field>
     <field name="text">Step 2: For each identified UI component/area, insert a new numbered sub-section (e.g., 2.1, 2.2, 2.3...) into the document</field>
     <field name="text">Step 3: Fill each sub-section with the specific component details (wireframe, interactions, events)</field>
-    <field name="text">NEVER rely on fixed template sections alone — the number of sections MUST match the number of identified UI components</field>
+    <field name="text">NEVER rely on fixed template sections alone 鈥?the number of sections MUST match the number of identified UI components</field>
   </block>
   
   <!-- Loop: Dynamically generate a section for each UI component -->
@@ -508,42 +427,3 @@ Analyze one specific UI feature from source code, extract business functionality
 </workflow>
 ```
 
-## Constraints
-
-1. **DO NOT analyze files outside the specified `{{sourcePath}}`**
-2. **DO NOT generate separate documents for embedded components**
-3. **All content MUST be in the language specified by `{{language}}`**
-4. **Use `search_replace` for section filling, NEVER rewrite entire document**
-5. **Mermaid diagrams MUST follow the rules in `mermaid-rule.md`**
-6. **All links MUST use relative paths, NEVER `file://` protocol**
-
-## Task Completion Report
-
-When the task is complete, report the following:
-
-**Status:** `success` | `partial` | `failed`
-
-**Summary:**
-- Feature analyzed: `{{feature_name}}`
-- Document generated: `{{documentPath}}`
-- Platform: `{{platform_type}}/{{platform_subtype}}`
-- Module: `{{module}}`
-
-**Files Generated:**
-- `{{documentPath}}` - Feature documentation
-- `completed_dir/markerName.done.json` - Completion marker
-
-**Note:** Graph data (.graph.json) is handled by `speccrew-knowledge-bizs-ui-graph` Skill. The `.done.json` completion marker is written by this Skill in Step 7.
-
-## Checklist
-
-- [ ] Template file selected based on `{{platform_type}}`
-- [ ] Template content read successfully
-- [ ] Source file read and analyzed
-- [ ] Business features extracted with wireframes
-- [ ] Referencing pages found
-- [ ] Template copied to document path
-- [ ] All sections filled using search_replace
-- [ ] All content in target language (`{{language}}`)
-- [ ] Results reported in JSON format
-- [ ] Done marker file written to completed_dir