speccrew 0.6.69 → 0.7.1

package/.speccrew/skills/speccrew-knowledge-techs-ui-analyze/workflow.agentflow.xml

@@ -0,0 +1,278 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="knowledge-techs-ui-analyze" status="pending" version="1.0" desc="Analyze UI codebase to extract styles, patterns, and conventions">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="source_path" required="true" type="string" desc="Path to UI source code directory"/>
+    <field name="platform_id" required="true" type="string" desc="Platform identifier (e.g., admin-pc, admin-mobile)"/>
+    <field name="platform_type" required="true" type="string" desc="Platform type (web, mobile, desktop)"/>
+    <field name="framework" required="true" type="string" desc="Frontend framework (vue3, react, uniapp, etc.)"/>
+    <field name="output_path" required="true" type="string" desc="Output directory for generated style guide"/>
+    <field name="language" required="true" type="string" desc="Target language (e.g., zh, en)"/>
+    <field name="skill_path" required="true" type="string" desc="Path to this skill directory"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="forbidden" desc="Document generation constraints">
+    <field name="text">FORBIDDEN: create_file for analysis documents — NEVER use create_file to write any UI analysis document</field>
+    <field name="text">FORBIDDEN: Full-file rewrite — NEVER replace the entire document content in a single operation</field>
+    <field name="text">Each document MUST be created by copying the appropriate template then filling sections with search_replace</field>
+  </block>
+
+  <block type="rule" id="R2" level="mandatory" desc="Template-first workflow">
+    <field name="text">MANDATORY: Template-first workflow — For every output document, copy the corresponding template to target path first, then fill sections with search_replace</field>
+    <field name="text">Skipping copy and writing content directly is FORBIDDEN</field>
+  </block>
+
+  <!-- ============================================================
+       Step 0: Pre-load Required Templates
+       ============================================================ -->
+  <block type="task" id="B0" action="read-file" desc="Read all template files to understand document structures">
+    <field name="templates">
+      - templates/UI-STYLE-GUIDE-TEMPLATE.md → ui-style-guide.md
+      - templates/PAGE-TYPE-SUMMARY-TEMPLATE.md → page-types/page-type-summary.md
+      - templates/PAGE-TYPE-INDIVIDUAL-TEMPLATE.md → page-types/[type]-pages.md
+      - templates/COMPONENT-LIBRARY-TEMPLATE.md → components/component-library.md
+      - templates/COMMON-COMPONENTS-TEMPLATE.md → components/common-components.md
+      - templates/BUSINESS-COMPONENTS-TEMPLATE.md → components/business-components.md
+      - templates/COMPONENT-INDIVIDUAL-TEMPLATE.md → components/{component-name}.md
+      - templates/LAYOUT-PATTERNS-TEMPLATE.md → layouts/page-layouts.md
+      - templates/NAVIGATION-PATTERNS-TEMPLATE.md → layouts/navigation-patterns.md
+      - templates/LAYOUT-INDIVIDUAL-TEMPLATE.md → layouts/{layout-name}-layout.md
+      - templates/STYLE-SYSTEM-TEMPLATE.md → styles/color-system.md
+      - templates/TYPOGRAPHY-TEMPLATE.md → styles/typography.md
+      - templates/SPACING-TEMPLATE.md → styles/spacing-system.md
+    </field>
+    <field name="on_fail">STOP and report error with template path</field>
+    <field name="output" var="templates_loaded"/>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="UI Style Analysis" status="pending" desc="Discover, analyze, and document UI patterns">
+
+    <!-- Step 1: Discover Source Structure -->
+    <block type="task" id="B1" action="analyze" desc="Explore project structure">
+      <field name="key_directories">
+        - src/views/ or src/pages/ - Page components
+        - src/components/ - Reusable components
+        - src/layout/ or src/layouts/ - Layout components
+        - src/styles/ or src/assets/styles/ - Style files
+      </field>
+      <field name="extract_for">ui-style-guide.md Sections: Project Overview, Platform Summary</field>
+      <field name="output" var="project_structure"/>
+    </block>
+
+    <!-- Step 2: Analyze Page Types -->
+    <block type="task" id="B2" action="analyze" desc="Dynamic page type discovery">
+      <field name="rules">
+        File Name Analysis:
+        - Extract naming patterns from page files
+        - Group files by similar naming conventions
+        - Examples: *List.vue, *Form.vue, *Detail.vue, *Chart.vue
+        
+        Component Usage Analysis:
+        - Identify dominant components in each file group
+        - Table-heavy files → likely list/query pages
+        - Form-heavy files → likely create/edit pages
+        - Chart-heavy files → likely report/dashboard pages
+        
+        Route/Navigation Analysis:
+        - Check router configuration for page organization
+        - Identify menu structures and page hierarchies
+      </field>
+      <field name="output" var="page_types"/>
+    </block>
+
+    <block type="task" id="B3" action="generate" desc="Generate page-types/page-type-summary.md">
+      <field name="template">templates/PAGE-TYPE-SUMMARY-TEMPLATE.md</field>
+      <field name="output">${output_path}/page-types/page-type-summary.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="loop" id="L1" over="${page_types}" as="page_type" desc="Generate individual page type documents">
+      <block type="task" action="generate" desc="Generate page-types/${page_type.name}-pages.md">
+        <field name="template">templates/PAGE-TYPE-INDIVIDUAL-TEMPLATE.md</field>
+        <field name="output">${output_path}/page-types/${page_type.name}-pages.md</field>
+        <field name="method">copy template, then use search_replace to fill sections</field>
+      </block>
+    </block>
+
+    <!-- Step 3: Extract Component Usage -->
+    <block type="task" id="B4" action="analyze" desc="Analyze component imports and usage">
+      <field name="categories">
+        UI Framework Components (Element Plus, Ant Design, Vant):
+        - Button, Input, Select, Table, Form, Modal, etc.
+        
+        Common Components (Project-specific):
+        - SearchForm, Pagination, DictTag, ImagePreview, etc.
+        
+        Business Components (Domain-specific):
+        - UserSelect, DeptTree, RolePicker, etc.
+      </field>
+      <field name="output" var="components"/>
+    </block>
+
+    <block type="task" id="B5" action="generate" desc="Generate components/component-library.md">
+      <field name="template">templates/COMPONENT-LIBRARY-TEMPLATE.md</field>
+      <field name="output">${output_path}/components/component-library.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="task" id="B6" action="generate" desc="Generate components/common-components.md">
+      <field name="template">templates/COMMON-COMPONENTS-TEMPLATE.md</field>
+      <field name="output">${output_path}/components/common-components.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="task" id="B7" action="generate" desc="Generate components/business-components.md">
+      <field name="template">templates/BUSINESS-COMPONENTS-TEMPLATE.md</field>
+      <field name="output">${output_path}/components/business-components.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="loop" id="L2" over="${components.individual}" as="component" desc="Generate individual component documents">
+      <block type="task" action="generate" desc="Generate components/${component.name}.md">
+        <field name="template">templates/COMPONENT-INDIVIDUAL-TEMPLATE.md</field>
+        <field name="output">${output_path}/components/${component.name}.md</field>
+        <field name="method">copy template, then use search_replace to fill sections</field>
+        <field name="rules">
+          - For UI framework components: Focus on project-specific usage patterns
+          - For custom components: Full Props/Events/Slots documentation
+          - Skip trivial components (&lt; 10 lines, no props/events)
+        </field>
+      </block>
+    </block>
+
+    <!-- Step 4: Analyze Layout Patterns -->
+    <block type="task" id="B8" action="analyze" desc="Identify common layout patterns">
+      <field name="layout_types">
+        Standard List Layout:
+        - Search Form
+        - Toolbar (Add/Export/Delete buttons)
+        - Data Table
+        - Pagination
+        
+        Standard Form Layout:
+        - Form Card
+        - Form Fields (2-3 columns)
+        - Action Buttons (Submit/Cancel)
+        
+        Detail View Layout:
+        - Detail Card
+        - Description List
+        - Action Buttons
+        
+        Split Pane Layout:
+        - Left: Tree/Menu
+        - Right: Content Table/Form
+      </field>
+      <field name="output" var="layouts"/>
+    </block>
+
+    <block type="task" id="B9" action="generate" desc="Generate layouts/page-layouts.md">
+      <field name="template">templates/LAYOUT-PATTERNS-TEMPLATE.md</field>
+      <field name="output">${output_path}/layouts/page-layouts.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="task" id="B10" action="generate" desc="Generate layouts/navigation-patterns.md">
+      <field name="template">templates/NAVIGATION-PATTERNS-TEMPLATE.md</field>
+      <field name="output">${output_path}/layouts/navigation-patterns.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="loop" id="L3" over="${layouts.individual}" as="layout" desc="Generate individual layout documents">
+      <block type="task" action="generate" desc="Generate layouts/${layout.name}-layout.md">
+        <field name="template">templates/LAYOUT-INDIVIDUAL-TEMPLATE.md</field>
+        <field name="output">${output_path}/layouts/${layout.name}-layout.md</field>
+        <field name="method">copy template, then use search_replace to fill sections</field>
+        <field name="rules">
+          - Minimum 2 pages must share a layout pattern to warrant a document
+          - Generate ASCII layout diagram from actual page structure
+        </field>
+      </block>
+    </block>
+
+    <!-- Step 5: Extract Style Conventions -->
+    <block type="task" id="B11" action="analyze" desc="Analyze style files for color, typography, spacing">
+      <field name="extract">
+        Color System:
+        - Primary colors, Status colors, Text colors, Background colors, Border colors
+        
+        Typography:
+        - Font families, Font sizes, Font weights, Line heights
+        
+        Spacing System:
+        - Padding/Margin scales, Grid system, Container widths
+      </field>
+      <field name="output" var="styles"/>
+    </block>
+
+    <block type="task" id="B12" action="generate" desc="Generate styles/color-system.md">
+      <field name="template">templates/STYLE-SYSTEM-TEMPLATE.md</field>
+      <field name="output">${output_path}/styles/color-system.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="task" id="B13" action="generate" desc="Generate styles/typography.md">
+      <field name="template">templates/TYPOGRAPHY-TEMPLATE.md</field>
+      <field name="output">${output_path}/styles/typography.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <block type="task" id="B14" action="generate" desc="Generate styles/spacing-system.md">
+      <field name="template">templates/SPACING-TEMPLATE.md</field>
+      <field name="output">${output_path}/styles/spacing-system.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+    </block>
+
+    <!-- Step 6: Generate Main Documentation -->
+    <block type="task" id="B15" action="generate" desc="Generate ui-style-guide.md">
+      <field name="template">templates/UI-STYLE-GUIDE-TEMPLATE.md</field>
+      <field name="output">${output_path}/ui-style-guide.md</field>
+      <field name="method">copy template, then use search_replace to fill sections</field>
+      <field name="note">ui-style-guide.md should reference/link to all other generated documents</field>
+    </block>
+
+    <!-- Step 7: Verify Output Completeness -->
+    <block type="task" id="B16" action="validate" desc="Verify all required files exist">
+      <field name="required_files">
+        - ui-style-guide.md
+        - page-types/page-type-summary.md
+        - page-types/[type]-pages.md (one per discovered type)
+        - components/component-library.md
+        - components/common-components.md
+        - components/business-components.md
+        - components/{component-name}.md (one per discovered component)
+        - layouts/page-layouts.md
+        - layouts/navigation-patterns.md
+        - layouts/{layout-name}-layout.md (one per discovered layout)
+        - styles/color-system.md
+        - styles/typography.md
+        - styles/spacing-system.md
+      </field>
+      <field name="output" var="verification_result"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="status" from="${verification_result.status}" type="string" desc="Analysis status"/>
+    <field name="platform_id" from="${platform_id}" type="string" desc="Platform identifier"/>
+    <field name="output_path" from="${output_path}" type="string" desc="Output directory"/>
+    <field name="page_types_count" from="${page_types.length}" type="number" desc="Number of page types discovered"/>
+    <field name="components_count" from="${components.individual.length}" type="number" desc="Number of components documented"/>
+    <field name="layouts_count" from="${layouts.individual.length}" type="number" desc="Number of layouts documented"/>
+    <field name="documents_generated" from="${verification_result.documents_count}" type="number" desc="Total documents generated"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-pm-knowledge-detector/SKILL.md

@@ -58,79 +58,11 @@ Detect business knowledge base availability and completeness status. Scans the s
 | `lite` | has_features = true AND has_system_overview = false |
 | `none` | has_features = false AND has_system_overview = false |
 
-## Workflow
-
-```mermaid
-flowchart TD
-    Start([Start]) --> Step1[Step 1: Check system-overview.md]
-    Step1 --> Step2[Step 2: Scan for features files]
-    Step2 --> Step3[Step 3: Scan for entry-dirs files]
-    Step3 --> Step4[Step 4: Count modules and platforms]
-    Step4 --> Step5[Step 5: Determine status and return JSON]
-    Step5 --> End([End])
-```
-
-### Step 1: Check system-overview.md
-
-Check if the system overview file exists:
-
-1. Path: `{workspace_path}/knowledges/bizs/system-overview.md`
-2. Attempt to read the file
-3. Set `has_system_overview` = true if exists, false otherwise
-4. Set `system_overview_path` = path if exists, null otherwise
-
-**Output**: "Step 1 Status: ✅ COMPLETED - system-overview.md {exists|not found}"
-
-### Step 2: Scan for features files
-
-Scan the sync-state directory for feature inventory files:
-
-1. Use provided path: `{sync_state_bizs_dir}/`
-2. Glob pattern: `features-*.json`
-3. Collect all matching files into `features_files` array
-4. Set `has_features` = true if any files found
-
-**Output**: "Step 2 Status: ✅ COMPLETED - Found {count} features files"
-
-### Step 3: Scan for entry-dirs files
-
-Scan for entry directory configuration files:
-
-1. Use provided path: `{sync_state_bizs_dir}/`
-2. Glob pattern: `entry-dirs-*.json`
-3. Collect all matching files into `entry_dirs_files` array
-4. Set `has_entry_dirs` = true if any files found
-
-**Output**: "Step 3 Status: ✅ COMPLETED - Found {count} entry-dirs files"
-
-### Step 4: Count modules and platforms
-
-For each features file found:
-
-1. Read the JSON content
-2. Extract `platformId` and add to `available_platforms` array
-3. Sum up `modules` array length for `module_count`
-4. Extract `features` array length for feature count per platform
-
-**Output**: "Step 4 Status: ✅ COMPLETED - {platform_count} platforms, {module_count} modules"
-
-### Step 5: Determine status and return JSON
-
-Calculate the overall status:
-
-```
-IF has_system_overview AND has_features THEN
-    status = "full"
-ELSE IF has_features THEN
-    status = "lite"
-ELSE
-    status = "none"
-END IF
-```
+## AgentFlow Definition
 
-Return the complete JSON output.
+<!-- @agentflow: workflow.agentflow.xml -->
 
-**Output**: "Step 5 Status: ✅ COMPLETED - Knowledge status: {status}"
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ## Constraints
 

package/.speccrew/skills/speccrew-pm-knowledge-detector/workflow.agentflow.xml

@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="knowledge-detector-main" status="pending" version="1.0" desc="Detect business knowledge base availability and completeness status">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="workspace_path" required="true" type="string" desc="Absolute path to speccrew workspace"/>
+    <field name="sync_state_bizs_dir" required="true" type="string" desc="Absolute path to sync-state/knowledge-bizs directory"/>
+    <field name="configs_dir" required="true" type="string" desc="Absolute path to docs/configs directory"/>
+    <field name="language" required="true" type="string" desc="Language code for output content"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Path constraints">
+    <field name="text">Use the provided absolute paths directly. DO NOT construct or derive paths yourself.</field>
+    <field name="text">All paths must use forward slashes / as path separators (even on Windows)</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Execution constraints">
+    <field name="text">This skill is READ-ONLY - do not modify any files</field>
+    <field name="text">Use Glob for scanning, avoid deep file reads</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Knowledge Base Detection" status="pending" desc="Scan and detect knowledge base status">
+
+    <!-- Step 1: Check system-overview.md -->
+    <block type="task" id="B1" action="read-file" desc="Check if system-overview.md exists">
+      <field name="path" value="${workspace_path}/knowledges/bizs/system-overview.md"/>
+      <field name="output" var="system_overview_content"/>
+      <field name="on_error">continue</field>
+    </block>
+
+    <!-- Step 2: Scan for features files -->
+    <block type="task" id="B2" action="run-script" desc="Scan for features-*.json files">
+      <field name="command">Get-ChildItem -Path "${sync_state_bizs_dir}" -Filter "features-*.json" -ErrorAction SilentlyContinue | Select-Object -ExpandProperty FullName</field>
+      <field name="output" var="features_files_list"/>
+    </block>
+
+    <!-- Step 3: Scan for entry-dirs files -->
+    <block type="task" id="B3" action="run-script" desc="Scan for entry-dirs-*.json files">
+      <field name="command">Get-ChildItem -Path "${sync_state_bizs_dir}" -Filter "entry-dirs-*.json" -ErrorAction SilentlyContinue | Select-Object -ExpandProperty FullName</field>
+      <field name="output" var="entry_dirs_files_list"/>
+    </block>
+
+    <!-- Step 4: Analyze features files and count modules/platforms -->
+    <block type="loop" id="L1" over="${features_files_list}" as="features_file" desc="Process each features file">
+      <block type="task" id="B4" action="read-file" desc="Read features file content">
+        <field name="path" value="${features_file}"/>
+        <field name="output" var="features_data"/>
+      </block>
+      <block type="task" id="B5" action="analyze" desc="Extract platform and module info">
+        <field name="input" value="${features_data}"/>
+        <field name="extract">
+          - platformId
+          - platformType
+          - modules array length
+          - features array length
+        </field>
+        <field name="output" var="platform_info"/>
+      </block>
+    </block>
+
+    <!-- Step 5: Determine status and compile results -->
+    <block type="task" id="B6" action="analyze" desc="Determine knowledge base status">
+      <field name="input">
+        system_overview_exists: ${system_overview_content} != null
+        features_files: ${features_files_list}
+        entry_dirs_files: ${entry_dirs_files_list}
+        platform_data: ${platform_info}
+      </field>
+      <field name="logic">
+        IF has_system_overview AND has_features THEN status = "full"
+        ELSE IF has_features THEN status = "lite"
+        ELSE status = "none"
+      </field>
+      <field name="output" var="detection_result"/>
+    </block>
+
+    <!-- Checkpoint: Verify detection complete -->
+    <block type="checkpoint" id="CP1" name="detection-complete" desc="Verify detection completed">
+      <field name="verify" value="${detection_result.status} != null"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="status" from="${detection_result.status}" type="string" desc="Knowledge base status: full, lite, or none"/>
+    <field name="has_system_overview" from="${detection_result.has_system_overview}" type="boolean" desc="Whether system-overview.md exists"/>
+    <field name="has_features" from="${detection_result.has_features}" type="boolean" desc="Whether features files exist"/>
+    <field name="has_entry_dirs" from="${detection_result.has_entry_dirs}" type="boolean" desc="Whether entry-dirs files exist"/>
+    <field name="available_platforms" from="${detection_result.available_platforms}" type="array" desc="List of available platform IDs"/>
+    <field name="module_count" from="${detection_result.module_count}" type="number" desc="Total module count"/>
+    <field name="features_files" from="${detection_result.features_files}" type="array" desc="List of features file paths"/>
+    <field name="entry_dirs_files" from="${detection_result.entry_dirs_files}" type="array" desc="List of entry-dirs file paths"/>
+    <field name="system_overview_path" from="${detection_result.system_overview_path}" type="string" desc="Path to system overview file"/>
+    <field name="message" value="Knowledge base status detected successfully" type="string" desc="Status message"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-pm-module-initializer/SKILL.md

@@ -97,115 +97,11 @@ Example: `"ki-web-vue-system-index"`
 
 > **Note**: This ID is consistent with task IDs in DISPATCH-PROGRESS.json and is used for progress tracking.
 
-## Workflow
-
-```mermaid
-flowchart TD
-    Start([Start]) --> Step1[Step 1: Read and filter features]
-    Step1 --> Step2[Step 2: Select analyzer by platform_type]
-    Step2 --> Step3[Step 3: Build task list]
-    Step3 --> Step4[Step 4: Build summarize params]
-    Step4 --> Step5[Step 5: Output task plan JSON]
-    Step5 --> End([End])
-```
-
-### Step 1: Read and Filter Features
-
-**Step 1 Status: 🔄 IN PROGRESS**
-
-1. **Read features file**: Parse the `features_file` JSON
-2. **Filter by module**: Select features where `module == module_name` AND `analyzed == false`
-3. **Record counts**:
-   - Total features for this module
-   - Pending features (analyzed = false)
-
-**Output**: "Step 1 Status: ✅ COMPLETED - Found {total} total features, {pending} pending for analysis"
-
-### Step 2: Select Analyzer by Platform Type
-
-**Step 2 Status: 🔄 IN PROGRESS**
-
-Based on `platform_type`, select the appropriate analyzer Skill:
-
-| platform_type | skill_name | Description |
-|---------------|------------|-------------|
-| web, mobile, desktop | `speccrew-knowledge-bizs-ui-analyze` | UI Feature Analysis |
-| backend | `speccrew-knowledge-bizs-api-analyze` | API Controller Analysis |
-
-**Output**: "Step 2 Status: ✅ COMPLETED - Selected analyzer: {skill_name}"
-
-### Step 3: Build Task List
+## AgentFlow Definition
 
-**Step 3 Status: 🔄 IN PROGRESS**
-
-For each pending feature from Step 1, build a task object with analyzer parameters.
-
-> 🛑 **IMPORTANT**: This Skill does NOT execute analyze. It ONLY generates the task list. PM Agent will dispatch Workers based on this task plan.
-
-#### Task object structure for each pending feature:
-
-```json
-{
-  "id": "ki-{platform_id}-{feature.module}-{feature.fileName}",
-  "fileName": "{feature.fileName}",
-  "sourcePath": "{feature.sourcePath}",
-  "documentPath": "{output_path}/bizs/{platform_id}/{feature.module}/features",
-  "module": "{feature.module}",
-  "platform_type": "{platform_type}",
-  "platform_subtype": "{platform_subtype}",
-  "tech_stack": "{tech_stack}",
-  "language": "{language}",
-  "status": "pending"
-}
-```
-
-For backend features (api-analyze), also include:
-```json
-{
-  "completed_dir": "{completed_dir}",
-  "sourceFile": "{sourceFile}"
-}
-```
-
-**Note**: The `id` field format is `ki-{platform_id}-{module}-{fileName}` where `ki` stands for "knowledge initialization". This ID is consistent with task IDs in DISPATCH-PROGRESS.json for progress tracking.
-
-**Output**: "Step 3 Status: ✅ COMPLETED - Built {count} task entries"
-
-### Step 4: Build Summarize Parameters
-
-**Step 4 Status: 🔄 IN PROGRESS**
-
-Build the summarize_params object for module-summarize skill. This will be used by PM Agent after all analyze tasks complete.
-
-```json
-{
-  "skill": "speccrew-knowledge-module-summarize",
-  "module_name": "{module_name}",
-  "module_path": "{output_path}/bizs/{platform_id}/{module_name}",
-  "language": "{language}"
-}
-```
-
-**Output**: "Step 4 Status: ✅ COMPLETED - Summarize params ready"
-
-### Step 5: Output Task Plan JSON
-
-**Step 5 Status: 🔄 IN PROGRESS**
-
-Compile and output the final task plan:
-
-```json
-{
-  "module_name": "...",
-  "platform_id": "...",
-  "analyzer_skill": "...",
-  "tasks": [...],
-  "total_pending": <count>,
-  "summarize_params": {...}
-}
-```
+<!-- @agentflow: workflow.agentflow.xml -->
 
-**Output**: "Step 5 Status: ✅ COMPLETED - Task plan generated with {count} pending features"
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ## Constraints