speccrew 0.6.68 → 0.7.0

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

@@ -1,77 +1,4 @@
----
-name: speccrew-knowledge-bizs-ui-style-extract-xml
-description: Extract and aggregate UI design patterns (page types, components, layouts) from analyzed bizs feature documents using XML workflow blocks, outputting to techs ui-style-patterns directory.
-tools: Read, Write
----
-
-# Bizs UI Style Extract (XML Workflow)
-
-Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature documents using XML workflow blocks. Through cross-module clustering analysis, identify common page types, component patterns, and layout patterns, then output them to the techs knowledge base `ui-style-patterns/` subdirectory.
-
-## Language Adaptation
-
-**CRITICAL**: All generated documents must match the user's language. Detect the language from the user's input and generate content accordingly.
-
-- User writes in 中文 → Generate Chinese documents, use `language: "zh"`
-- User writes in English → Generate English documents, use `language: "en"`
-- User writes in other languages → Use appropriate language code
-
-**All generated pattern documents must be in the language specified by the `language` parameter.**
-
-## Trigger Scenarios
-
-- Called by `speccrew-knowledge-bizs-dispatch` Stage 3.5 (after Module Summarize, before System Summary)
-- "Extract UI patterns from bizs features"
-- "Aggregate UI design patterns"
-
-## Input
-
-| Variable | Description | Required |
-|----------|-------------|----------|
-| `platform_id` | Platform identifier (e.g., web-vue, mobile-uniapp), used to locate output directory | Yes |
-| `platform_type` | Platform type (web, mobile, desktop), only execute for frontend platforms | Yes |
-| `feature_docs_path` | Completed feature documents base path, e.g., `speccrew-workspace/knowledges/bizs/{platform-type}/{module}/features/` | Yes |
-| `features_manifest_path` | Path to features-{platform}.json, used to get completed feature list | Yes |
-| `module_overviews_path` | **Parent directory** containing all module overview subdirectories. Example: `knowledges/bizs/web-vue/` (this directory contains `system/system-overview.md`, `user/user-overview.md`, etc.). **NOT** a specific module directory like `knowledges/bizs/web-vue/system/`. | Yes |
-| `output_path` | Output directory, e.g., `speccrew-workspace/knowledges/techs/{platform_id}/ui-style-patterns/` | Yes |
-| `language` | User language code | Yes |
-
-## Output
-
-> **Directory Separation**: This skill outputs to `ui-style-patterns/` (NOT `ui-style/`).
-> - `ui-style/` is managed by techs pipeline (framework-level design system, existing components/pages)
-> - `ui-style-patterns/` is managed by bizs pipeline (business pattern aggregation from feature docs)
-> This separation prevents file conflicts between the two pipelines.
-
-```
-{output_path}/
-├── page-types/          # Page type pattern documents
-│   ├── {pattern-name}.md
-│   └── ...
-├── components/          # Component pattern documents
-│   ├── {pattern-name}.md
-│   └── ...
-└── layouts/             # Layout pattern documents
-    ├── {pattern-name}.md
-    └── ...
-```
-
-## Absolute Constraints
-
-> **These rules apply to ALL document generation steps. Violation = task failure.**
-
-1. **FORBIDDEN: `create_file` for pattern documents** — NEVER use `create_file` to write pattern documents. Each document MUST be created by copying the appropriate template then filling sections with `search_replace`.
-
-2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
-
-3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections for every pattern document.
-
-## 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-style-extract-main" status="pending" version="1.0" desc="Extract and aggregate UI design patterns from feature documents">
 
   <!-- ============================================================
@@ -103,13 +30,13 @@ Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature
   <!-- ============================================================
        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>
 
   <!-- ============================================================
@@ -332,74 +259,3 @@ Extract and aggregate **UI design patterns** from bizs pipeline analyzed feature
   </block>
 
 </workflow>
-```
-
-## Generation Rules
-
-1. **Pattern Quality**:
-   - Each pattern must have clear applicable scenarios
-   - Generalized ASCII wireframe (not feature-specific)
-   - At least 2 instance references (from same or different modules)
-
-2. **Template Compliance**:
-   - All sections from template must be filled
-   - Instance reference paths must be relative and valid
-
-3. **Mermaid Compliance**:
-   - Follow all rules in `mermaid-rule.md`
-   - Use basic `graph TB` or `graph LR` syntax
-   - No prohibited syntax elements
-
-4. **Language Consistency**:
-   - All content in the specified `language`
-   - Template section headers remain in English
-   - Content text matches user language
-
-## Error Handling
-
-| Scenario | Handling |
-|----------|----------|
-| No completed features | Return empty result, log warning |
-| No patterns identified | Return empty result, log message |
-| Template not found | Use default structure, log warning |
-| Feature document missing | Skip feature, continue with others |
-
-## Checklist
-
-- [ ] Step 1: Features manifest loaded, completed features identified
-- [ ] Step 2: All completed feature documents read
-- [ ] Step 3: All module overviews read
-- [ ] Step 4: Cross-module clustering analysis completed
-- [ ] Step 5: Pattern documents generated with correct templates
-- [ ] Step 5: File naming follows kebab-case convention
-- [ ] Step 5: ASCII wireframes are generalized versions
-- [ ] Step 5: Instance references use relative paths
-- [ ] Step 5: Mermaid diagrams follow mermaid-rule.md
-- [ ] Step 6: Summary returned with file list
-
-## Return
-
-After completion, return a summary object to the caller:
-
-```json
-{
-  "status": "completed",
-  "platform_id": "web-vue",
-  "patterns": {
-    "page_types": {
-      "count": 3,
-      "files": ["page-types/list-page.md", "page-types/form-page.md", "page-types/detail-page.md"]
-    },
-    "components": {
-      "count": 2,
-      "files": ["components/search-filter-bar.md", "components/modal-form.md"]
-    },
-    "layouts": {
-      "count": 1,
-      "files": ["layouts/sidebar-content.md"]
-    }
-  },
-  "total_patterns": 6,
-  "output_path": "speccrew-workspace/knowledges/techs/web-vue/ui-style-patterns/"
-}
-```

package/.speccrew/skills/speccrew-knowledge-graph-query/SKILL.md

@@ -63,130 +63,11 @@ Any Agent (speccrew-task-worker, speccrew-knowledge-dispatch, or other agents)
 }
 ```
 
-## Workflow
-
-```mermaid
-graph TB
-    Start([Start]) --> SelectAction{Action Type}
-    SelectAction -->|get-node| GetNode[Run script: get-node]
-    SelectAction -->|query-nodes| QueryNodes[Run script: query-nodes]
-    SelectAction -->|get-edges| GetEdges[Run script: get-edges]
-    SelectAction -->|search| Search[Run script: search]
-    SelectAction -->|trace-upstream| TraceUp[Run script: trace-upstream]
-    SelectAction -->|trace-downstream| TraceDown[Run script: trace-downstream]
-    GetNode --> Return[Return JSON Result]
-    QueryNodes --> Return
-    GetEdges --> Return
-    Search --> Return
-    TraceUp --> Return
-    TraceDown --> Return
-    Return --> End([End])
-```
-
----
-
-## Actions
-
-### Action: get-node
-
-Get a single node by its ID.
-
-```bash
-node "{skill_path}/scripts/graph-query.js" --action "get-node" --id "{{id}}" --graphRoot "{{graphRoot}}"
-```
-
-**Returns:** Single node object or empty if not found.
-
-### Action: query-nodes
-
-Query nodes by module and/or type.
-
-```bash
-# By module and type
-node "{skill_path}/scripts/graph-query.js" --action "query-nodes" --module "{{module}}" --type "{{type}}" --graphRoot "{{graphRoot}}"
-
-# By module only
-node "{skill_path}/scripts/graph-query.js" --action "query-nodes" --module "{{module}}" --graphRoot "{{graphRoot}}"
-
-# By type only
-node "{skill_path}/scripts/graph-query.js" --action "query-nodes" --type "{{type}}" --graphRoot "{{graphRoot}}"
-```
-
-**Returns:** Array of matching nodes.
-
-### Action: get-edges
-
-Get all edges connected to a node, filtered by direction.
-
-```bash
-node "{skill_path}/scripts/graph-query.js" --action "get-edges" --nodeId "{{id}}" --direction "{{direction}}" --graphRoot "{{graphRoot}}"
-```
-
-**Direction values:**
-- `in` — edges where this node is the `target`
-- `out` — edges where this node is the `source`
-- `both` — all edges connected to this node
-
-**Returns:** Array of matching edges.
-
-### Action: search
-
-Search nodes by keyword across name, description, tags, and keywords fields.
-
-```bash
-# Search with filters
-node "{skill_path}/scripts/graph-query.js" --action "search" --keyword "{{keyword}}" --type "{{type}}" --module "{{module}}" --graphRoot "{{graphRoot}}"
-
-# Search all
-node "{skill_path}/scripts/graph-query.js" --action "search" --keyword "{{keyword}}" --graphRoot "{{graphRoot}}"
-```
-
-**Returns:** Array of matching nodes, sorted by relevance.
-
-### Action: trace-upstream
-
-Trace all upstream dependencies of a node (what depends on / calls this node).
-
-```bash
-node "{skill_path}/scripts/graph-query.js" --action "trace-upstream" --id "{{id}}" --depth {{depth}} --graphRoot "{{graphRoot}}"
-```
-
-**Use case:** Impact analysis — "If I change this table, what APIs and pages are affected?"
-
-**Returns:** Tree structure of upstream nodes and edges.
-
-```json
-{
-  "root": { "id": "table-system-user", "type": "table" },
-  "upstream": [
-    {
-      "node": { "id": "api-system-user-list", "type": "api" },
-      "edge": { "type": "operates", "metadata": { "operation": "SELECT" } },
-      "depth": 1,
-      "upstream": [
-        {
-          "node": { "id": "page-system-user-list", "type": "page" },
-          "edge": { "type": "calls", "metadata": { "trigger": "onMounted" } },
-          "depth": 2,
-          "upstream": []
-        }
-      ]
-    }
-  ]
-}
-```
-
-### Action: trace-downstream
-
-Trace all downstream dependencies of a node (what this node depends on / calls).
-
-```bash
-node "{skill_path}/scripts/graph-query.js" --action "trace-downstream" --id "{{id}}" --depth {{depth}} --graphRoot "{{graphRoot}}"
-```
+## AgentFlow Definition
 
-**Use case:** Dependency analysis — "What does this page call? What tables does this API touch?"
+<!-- @agentflow: workflow.agentflow.xml -->
 
-**Returns:** Tree structure of downstream nodes and edges (same format as trace-upstream).
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ---
 

package/.speccrew/skills/speccrew-knowledge-graph-query/workflow.agentflow.xml

@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="knowledge-graph-query" status="pending" version="1.0" desc="Query knowledge graph to find nodes, edges, relationships">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="action" required="true" type="string" desc="Query action: get-node, query-nodes, get-edges, search, trace-upstream, trace-downstream"/>
+    <field name="id" required="false" type="string" desc="Node ID (for get-node, trace-*)"/>
+    <field name="module" required="false" type="string" desc="Filter by module (for query-nodes, search)"/>
+    <field name="type" required="false" type="string" desc="Filter by node type (for query-nodes, search)"/>
+    <field name="keyword" required="false" type="string" desc="Search keyword (for search)"/>
+    <field name="direction" required="false" type="string" desc="Edge direction: in, out, both (for get-edges)"/>
+    <field name="depth" required="false" type="number" default="2" desc="Trace depth (for trace-*)"/>
+    <field name="nodeId" required="false" type="string" desc="Node ID for get-edges"/>
+    <field name="graphRoot" required="true" type="string" desc="Path to graph root directory"/>
+    <field name="skill_path" required="true" type="string" desc="Path to this skill directory"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Query constraints">
+    <field name="text">action must be one of: get-node, query-nodes, get-edges, search, trace-upstream, trace-downstream</field>
+    <field name="text">graphRoot path must be correct (speccrew-workspace/knowledges/bizs/graph)</field>
+    <field name="text">For get-node / trace-*: id must follow {type}-{module}-{name} format</field>
+    <field name="text">For get-edges: direction must be one of in, out, both</field>
+    <field name="text">For trace-*: depth must be a positive integer (default: 2)</field>
+  </block>
+
+  <!-- ============================================================
+       Action Gateway
+       ============================================================ -->
+  <block type="gateway" id="G0" mode="exclusive" desc="Select query action">
+
+    <!-- Action: get-node -->
+    <branch test="${action} == 'get-node'" name="Get Node">
+      <block type="task" id="B1" action="run-script" desc="Get single node by ID">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "get-node" --id "${id}" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+    <!-- Action: query-nodes -->
+    <branch test="${action} == 'query-nodes'" name="Query Nodes">
+      <block type="task" id="B2" action="run-script" desc="Query nodes by module and/or type">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "query-nodes" --module "${module}" --type "${type}" --graphRoot "${graphRoot}"</field>
+        <field name="note">module and type parameters are optional filters</field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+    <!-- Action: get-edges -->
+    <branch test="${action} == 'get-edges'" name="Get Edges">
+      <block type="task" id="B3" action="run-script" desc="Get edges for node">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "get-edges" --nodeId "${nodeId}" --direction "${direction}" --graphRoot "${graphRoot}"</field>
+        <field name="rules">
+          Direction values:
+          - in: edges where this node is the target
+          - out: edges where this node is the source
+          - both: all edges connected to this node
+        </field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+    <!-- Action: search -->
+    <branch test="${action} == 'search'" name="Search">
+      <block type="task" id="B4" action="run-script" desc="Search nodes by keyword">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "search" --keyword "${keyword}" --type "${type}" --module "${module}" --graphRoot "${graphRoot}"</field>
+        <field name="note">Searches across name, description, tags, and keywords fields</field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+    <!-- Action: trace-upstream -->
+    <branch test="${action} == 'trace-upstream'" name="Trace Upstream">
+      <block type="task" id="B5" action="run-script" desc="Trace upstream dependencies">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "trace-upstream" --id "${id}" --depth ${depth} --graphRoot "${graphRoot}"</field>
+        <field name="note">Use case: Impact analysis — "If I change this table, what APIs and pages are affected?"</field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+    <!-- Action: trace-downstream -->
+    <branch test="${action} == 'trace-downstream'" name="Trace Downstream">
+      <block type="task" id="B6" action="run-script" desc="Trace downstream dependencies">
+        <field name="command">node "${skill_path}/scripts/graph-query.js" --action "trace-downstream" --id "${id}" --depth ${depth} --graphRoot "${graphRoot}"</field>
+        <field name="note">Use case: Dependency analysis — "What does this page call? What tables does this API touch?"</field>
+        <field name="output" var="query_result"/>
+      </block>
+    </branch>
+
+  </block>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="status" from="${query_result.status}" type="string" desc="Query result: success or not-found"/>
+    <field name="action" from="${action}" type="string" desc="Action performed"/>
+    <field name="resultCount" from="${query_result.resultCount}" type="number" desc="Number of results returned"/>
+    <field name="data" from="${query_result.data}" type="array" desc="Query result data"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-knowledge-graph-write/SKILL.md

@@ -55,88 +55,11 @@ Dispatch Agent (speccrew-knowledge-dispatch)
 }
 ```
 
-## Workflow
-
-```mermaid
-graph TB
-    Start([Start]) --> CheckAction{Action Type}
-    CheckAction -->|batch-write| WriteTmp[Write graphData to temp file]
-    WriteTmp --> AddNodes[Run script: add-nodes]
-    AddNodes --> AddEdges[Run script: add-edges]
-    AddEdges --> UpdateIndex[Run script: rebuild-index]
-    UpdateIndex --> UpdateMeta[Run script: update-meta]
-    UpdateMeta --> Report[Report Results]
-    CheckAction -->|init-module| InitModule[Run script: init-module]
-    InitModule --> Report
-    CheckAction -->|update-node| UpdateNode[Run script: update-node]
-    UpdateNode --> Report
-    CheckAction -->|remove-node| RemoveNode[Run script: remove-node]
-    RemoveNode --> Report
-    Report --> End([End])
-```
-
----
-
-## Actions
-
-### Action: batch-write
-
-**Primary use case.** Write all nodes and edges from a skill's `graphData` output to the graph.
-
-**Steps:**
-
-1. **Write graphData to temp file:**
-   - Create temp file at `{{graphRoot}}/temp/` with the `graphData` JSON content
-   - Temp file name: `batch-{module}-{timestamp}.json`
-
-2. **Add nodes:**
-   ```
-   node "{skill_path}/scripts/graph-write.js" --action "add-nodes" --platformId "{{platformId}}" --module "{{module}}" --file "{{tempFilePath}}" --graphRoot "{{graphRoot}}"
-   ```
-
-3. **Add edges:**
-   ```
-   node "{skill_path}/scripts/graph-write.js" --action "add-edges" --platformId "{{platformId}}" --module "{{module}}" --file "{{tempFilePath}}" --graphRoot "{{graphRoot}}"
-   ```
-
-4. **Update index and metadata** (automatic, handled by script)
-
-5. **Clean up temp file**
-
-**Deduplication Rule:**
-- Nodes with the same `id` are **replaced** (last write wins)
-- Edges with the same `source` + `target` + `type` combination are **replaced**
-
-### Action: init-module
+## AgentFlow Definition
 
-Initialize empty graph structure for a module. Used before Stage 2 analysis begins.
+<!-- @agentflow: workflow.agentflow.xml -->
 
-```
-node "{skill_path}/scripts/graph-write.js" --action "init-module" --platformId "{{platformId}}" --module "{{module}}" --graphRoot "{{graphRoot}}"
-```
-
-**Creates:**
-- `{{graphRoot}}/nodes/{{platformId}}/{{module}}.json` — empty nodes array
-- `{{graphRoot}}/edges/{{platformId}}/{{module}}.json` — empty edges array
-- Updates `{{graphRoot}}/graph-meta.json` — adds `{{platformId}}/{{module}}` to modules list
-- Creates `{{graphRoot}}/edges/{{platformId}}/cross-module.json` if not exists
-- Creates `{{graphRoot}}/indices/index.json` if not exists
-
-### Action: update-node
-
-Update an existing node's data fields.
-
-```
-node "{skill_path}/scripts/graph-write.js" --action "update-node" --platformId "{{platformId}}" --id "{{nodeId}}" --data '{{nodeDataJson}}' --graphRoot "{{graphRoot}}"
-```
-
-### Action: remove-node
-
-Remove a node and all its connected edges.
-
-```
-node "{skill_path}/scripts/graph-write.js" --action "remove-node" --platformId "{{platformId}}" --id "{{nodeId}}" --graphRoot "{{graphRoot}}"
-```
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ---
 

package/.speccrew/skills/speccrew-knowledge-graph-write/workflow.agentflow.xml

@@ -0,0 +1,152 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="knowledge-graph-write" status="pending" version="1.0" desc="Write graph data to knowledge graph storage">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="action" required="true" type="string" desc="Write action: batch-write, init-module, update-node, remove-node"/>
+    <field name="platformId" required="true" type="string" desc="Platform identifier for directory segregation"/>
+    <field name="module" required="false" type="string" desc="Target business module"/>
+    <field name="graphData" required="false" type="object" desc="Graph data from skill output (for batch-write): {nodes: [], edges: []}"/>
+    <field name="nodeId" required="false" type="string" desc="Node ID (for update-node / remove-node)"/>
+    <field name="nodeData" required="false" type="object" desc="Updated node data (for update-node)"/>
+    <field name="graphRoot" required="true" type="string" desc="Path to graph root directory"/>
+    <field name="skill_path" required="true" type="string" desc="Path to this skill directory"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Write constraints">
+    <field name="text">action must be one of: batch-write, init-module, update-node, remove-node</field>
+    <field name="text">platformId is required for all write actions</field>
+    <field name="text">graphRoot path must be correct (speccrew-workspace/knowledges/bizs/graph)</field>
+    <field name="text">For batch-write: graphData must contain valid nodes and edges arrays</field>
+    <field name="text">Index and metadata must be updated after write operations</field>
+  </block>
+
+  <!-- ============================================================
+       Action Gateway
+       ============================================================ -->
+  <block type="gateway" id="G0" mode="exclusive" desc="Select write action">
+
+    <!-- Action: batch-write -->
+    <branch test="${action} == 'batch-write'" name="Batch Write">
+      
+      <!-- Step 1: Write graphData to temp file -->
+      <block type="task" id="B1" action="write-file" desc="Write graphData to temp file">
+        <field name="path">${graphRoot}/temp/batch-${module}-${timestamp}.json</field>
+        <field name="content">${graphData}</field>
+        <field name="output" var="temp_file_path"/>
+      </block>
+
+      <!-- Step 2: Add nodes -->
+      <block type="task" id="B2" action="run-script" desc="Add nodes from temp file">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "add-nodes" --platformId "${platformId}" --module "${module}" --file "${temp_file_path}" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="nodes_result"/>
+      </block>
+
+      <!-- Step 3: Add edges -->
+      <block type="task" id="B3" action="run-script" desc="Add edges from temp file">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "add-edges" --platformId "${platformId}" --module "${module}" --file "${temp_file_path}" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="edges_result"/>
+      </block>
+
+      <!-- Step 4: Update index -->
+      <block type="task" id="B4" action="run-script" desc="Rebuild global index">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "rebuild-index" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="index_result"/>
+      </block>
+
+      <!-- Step 5: Update metadata -->
+      <block type="task" id="B5" action="run-script" desc="Update graph metadata">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "update-meta" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="meta_result"/>
+      </block>
+
+      <!-- Step 6: Clean up temp file -->
+      <block type="task" id="B6" action="run-script" desc="Clean up temp file">
+        <field name="command">rm "${temp_file_path}"</field>
+        <field name="note">Remove temporary batch file after successful write</field>
+      </block>
+
+      <block type="event" id="E1" action="log" level="info" desc="Log batch write complete">
+        <field name="message">Batch write completed: ${nodes_result.count} nodes, ${edges_result.count} edges</field>
+        <field name="output" var="nodes_written" from="${nodes_result.count}"/>
+        <field name="output" var="edges_written" from="${edges_result.count}"/>
+      </block>
+
+    </branch>
+
+    <!-- Action: init-module -->
+    <branch test="${action} == 'init-module'" name="Initialize Module">
+      
+      <block type="task" id="B7" action="run-script" desc="Initialize empty module structure">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "init-module" --platformId "${platformId}" --module "${module}" --graphRoot "${graphRoot}"</field>
+        <field name="rules">
+          Creates:
+          - ${graphRoot}/nodes/${platformId}/${module}.json — empty nodes array
+          - ${graphRoot}/edges/${platformId}/${module}.json — empty edges array
+          - Updates ${graphRoot}/graph-meta.json — adds ${platformId}/${module} to modules list
+          - Creates ${graphRoot}/edges/${platformId}/cross-module.json if not exists
+          - Creates ${graphRoot}/indices/index.json if not exists
+        </field>
+        <field name="output" var="init_result"/>
+      </block>
+
+      <block type="event" id="E2" action="log" level="info" desc="Log module init complete">
+        <field name="message">Module ${module} initialized for platform ${platformId}</field>
+        <field name="output" var="nodes_written" value="0"/>
+        <field name="output" var="edges_written" value="0"/>
+      </block>
+
+    </branch>
+
+    <!-- Action: update-node -->
+    <branch test="${action} == 'update-node'" name="Update Node">
+      
+      <block type="task" id="B8" action="run-script" desc="Update existing node fields">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "update-node" --platformId "${platformId}" --id "${nodeId}" --data '${nodeData}' --graphRoot "${graphRoot}"</field>
+        <field name="output" var="update_result"/>
+      </block>
+
+      <block type="event" id="E3" action="log" level="info" desc="Log node update complete">
+        <field name="message">Node ${nodeId} updated successfully</field>
+        <field name="output" var="nodes_written" value="1"/>
+        <field name="output" var="edges_written" value="0"/>
+      </block>
+
+    </branch>
+
+    <!-- Action: remove-node -->
+    <branch test="${action} == 'remove-node'" name="Remove Node">
+      
+      <block type="task" id="B9" action="run-script" desc="Remove node and connected edges">
+        <field name="command">node "${skill_path}/scripts/graph-write.js" --action "remove-node" --platformId "${platformId}" --id "${nodeId}" --graphRoot "${graphRoot}"</field>
+        <field name="output" var="remove_result"/>
+      </block>
+
+      <block type="event" id="E4" action="log" level="info" desc="Log node removal complete">
+        <field name="message">Node ${nodeId} and connected edges removed</field>
+        <field name="output" var="nodes_written" value="-1"/>
+        <field name="output" var="edges_written" value="-1"/>
+      </block>
+
+    </branch>
+
+  </block>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="status" value="success" type="string" desc="Operation result"/>
+    <field name="action" from="${action}" type="string" desc="Action performed"/>
+    <field name="module" from="${module}" type="string" desc="Target module"/>
+    <field name="nodesWritten" from="${nodes_written}" type="number" desc="Number of nodes written"/>
+    <field name="edgesWritten" from="${edges_written}" type="number" desc="Number of edges written"/>
+    <field name="message" type="string" desc="Summary message"/>
+  </block>
+
+</workflow>