speccrew 0.6.69 → 0.7.1

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

@@ -1,53 +1,4 @@
----
-name: speccrew-knowledge-bizs-ui-graph-xml
-description: Constructs knowledge graph data (nodes, edges, relationships) from UI analysis results using XML workflow blocks. Generates graph JSON files and completion markers for the bizs knowledge pipeline.
-tools: Read, Write, Glob, Grep, Bash
----
-
-# UI Knowledge Graph Constructor (XML Workflow)
-
-> **CRITICAL CONSTRAINT**: DO NOT create temporary scripts, batch files, or workaround code files (`.py`, `.bat`, `.sh`, `.ps1`, etc.) under any circumstances.
-
-Construct knowledge graph data (nodes, edges, relationships) from UI feature analysis results and write completion marker files for the bizs knowledge pipeline.
-
-## Language Adaptation
-
-This skill automatically adapts to the user's input language. All documentation and output will be generated in the same language as the user's query.
-
-## Trigger Scenarios
-
-- "Construct graph data for UI feature {fileName}"
-- "Generate graph nodes and edges from UI analysis"
-- "Write completion markers for feature {fileName}"
-
-## 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 | Path to generated documentation | `"speccrew-workspace/knowledges/bizs/..."` |
-| `{{module}}` | string | Business module name | `"system"`, `"trade"`, `"_root"` |
-| `{{platform_type}}` | string | Platform type | `"web"`, `"mobile"` |
-| `{{platform_subtype}}` | string | Platform subtype | `"vue"`, `"react"` |
-| `{{completed_dir}}` | string | Marker files output directory | `"speccrew-workspace/knowledges/base/sync-state/knowledge-bizs/completed"` |
-| `{{sourceFile}}` | string | Source features JSON file name | `"features-web-vue.json"` |
-| `{{status}}` | string | Analysis status from UI analysis | `"success"`, `"partial"`, `"failed"` |
-| `{{analysisNotes}}` | string | Analysis notes from UI analysis | `"Successfully analyzed..."` |
-
-## Output
-
-**Generated Files (MANDATORY):**
-1. `{{completed_dir}}/{module}-{subpath}-{fileName}.graph.json` - Graph data with nodes and edges
-2. `{{completed_dir}}/{module}-{subpath}-{fileName}.graph-done.json` - Graph 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-knowledge-graph-construction" version="1.0" status="pending" desc="Construct graph data from UI analysis results">
 
   <!-- ============================================================
@@ -70,13 +21,13 @@ This skill automatically adapts to the user's input language. All documentation
   <!-- ============================================================
        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>
 
   <!-- ============================================================
@@ -302,146 +253,3 @@ This skill automatically adapts to the user's input language. All documentation
   </block>
 
 </workflow>
-```
-
-## Node Structure Reference
-
-```json
-{
-  "id": "page-{module}-{feature-name}",
-  "type": "page",
-  "name": "<display name>",
-  "module": "{{module}}",
-  "sourcePath": "{{sourcePath}}",
-  "documentPath": "{{documentPath}}",
-  "description": "...",
-  "tags": [...],
-  "keywords": [...],
-  "context": {
-    "route": "...",
-    "components": [...],
-    "platform": "{{platform_type}}-{{platform_subtype}}"
-  }
-}
-```
-
-## Edge Structure Reference
-
-```json
-{
-  "source": "page-{module}-{name}",
-  "target": "api-{module}-{api-name}",
-  "type": "calls",
-  "metadata": {
-    "trigger": "onClick|onMounted|onSubmit|...",
-    "method": "getUserList",
-    "context": "Page initialization - load user list"
-  }
-}
-```
-
-## Node ID Naming Convention
-
-```
-{type}-{module}-{name}
-
-Examples:
-  page-system-user-list
-  page-system-user-detail
-  component-system-user-form
-  component-shared-delete-confirm
-```
-
-## Marker File Naming Convention
-
-```
-{completed_dir}/{module}-{subpath}-{fileName}.graph.json
-```
-
-**Naming Rule Explanation:**
-
-The marker filename MUST follow the composite naming pattern `{module}-{subpath}-{fileName}` to prevent conflicts between same-named source files.
-
-**How to Extract Each Component from `{{sourcePath}}`:**
-
-1. **module**: Use `{{module}}` input variable directly (e.g., `system`, `trade`, `bpm`)
-
-2. **subpath**: Extract the middle path between the platform source root and the file name:
-   - Remove the top-level directory prefix (e.g., `yudao-ui/yudao-ui-admin-vue3/src/views/`)
-   - Remove the file name at the end
-   - Replace path separators (`/`) with hyphens (`-`)
-   - If the file is at the module root directory, subpath will be empty → omit from filename
-
-3. **fileName**: Use `{{fileName}}` input variable (file name WITHOUT extension)
-
-**Examples:**
-
-| sourcePath | module | subpath | fileName | Marker Filename |
-|------------|--------|---------|----------|-----------------|
-| `yudao-ui/.../system/notify/message/index.vue` | `system` | `notify-message` | `index` | `system-notify-message-index.graph.json` |
-| `yudao-ui/.../system/user/index.vue` | `system` | `user` | `index` | `system-user-index.graph.json` |
-| `yudao-ui/.../bpm/process-instance/index.vue` | `bpm` | `process-instance` | `index` | `bpm-process-instance-index.graph.json` |
-
-**Special Case - Empty subpath:**
-- If the file is directly in the module root directory: `{module}-{fileName}.graph.json`
-- Example: `yudao-ui/.../system/index.vue` → `system-index.graph.json`
-
-## Edge Types Reference
-
-| Edge Type | Direction | When to Create |
-|-----------|-----------|----------------|
-| `calls` | page → api | Page calls an API endpoint |
-| `navigates-to` | page → page | Page navigates to another page |
-| `uses` | page → component | Page uses a shared/local component |
-
-## API Coverage Verification Checklist
-
-- [ ] List ALL imported API functions from the source file
-- [ ] For each imported API, verify there is a corresponding `calls` edge
-- [ ] Check event handlers for API calls
-- [ ] Check lifecycle hooks for initialization API calls
-- [ ] Check status toggles, action buttons for special operation APIs
-- [ ] Verify no imported API is left unmapped
-
-## Pre-write Verification Checklist
-
-### Graph JSON Verification:
-- [ ] Filename follows `{module}-{subpath}-{fileName}.graph.json` pattern
-- [ ] JSON is valid (no trailing commas, all strings quoted)
-- [ ] Root-level `module` field is present
-- [ ] `nodes` and `edges` are arrays
-- [ ] ALL imported API functions are represented as `calls` edges
-
-### Completion Marker Verification:
-- [ ] Filename follows `{module}-{subpath}-{fileName}.graph-done.json` pattern
-- [ ] JSON is valid
-- [ ] `fileName` does NOT contain file extension
-- [ ] `sourceFile` matches `features-{platform}.json` pattern
-- [ ] `module` field is present and non-empty
-- [ ] `documentPath` is `"N/A"` when no document exists (not empty string)
-- [ ] `nodeCount` and `edgeCount` match actual graph data
-
-## Constraints
-
-1. **100% API coverage** - ALL imported API functions MUST be represented as `calls` edges
-2. **Valid JSON format** - Both `.graph.json` and `.graph-done.json` MUST be valid JSON
-3. **Root-level module field** - `.graph.json` MUST include `module` at root level
-4. **Correct filename pattern** - Use `{module}-{subpath}-{fileName}` composite naming
-5. **No file extension in fileName** - The `fileName` field in `.graph-done.json` MUST NOT include extension
-6. **documentPath as N/A** - Use `"N/A"` when no document exists, never empty string
-
-## Task Completion Report
-
-When the task is complete, report the following:
-
-**Status:** `success` | `partial` | `failed`
-
-**Summary:**
-- Feature: `{{fileName}}`
-- Module: `{{module}}`
-- Nodes constructed: `{{nodeCount}}`
-- Edges constructed: `{{edgeCount}}`
-
-**Files Generated:**
-- `{{completed_dir}}/{marker-filename}.graph.json`
-- `{{completed_dir}}/{marker-filename}.graph-done.json`