speccrew 0.7.16 → 0.7.17

package/.speccrew/skills/speccrew-pm-phase1-knowledge-check/workflow.agentflow.xml

@@ -0,0 +1,440 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="pm-phase1-knowledge-check" status="pending">
+
+  <!-- ========== Input Parameters ========== -->
+  <block type="input" id="I1" desc="Phase 1 Knowledge Check Input">
+    <field name="workspace_path" required="true" type="string" desc="Absolute path to speccrew-workspace root"/>
+    <field name="sync_state_bizs_dir" required="true" type="string" desc="Absolute path to knowledges/base/sync-state/knowledge-bizs"/>
+    <field name="configs_dir" required="true" type="string" desc="Absolute path to docs/configs directory"/>
+    <field name="ide_skills_dir" required="false" type="string" desc="Absolute path to IDE skills directory"/>
+    <field name="source_path" required="false" type="string" desc="Project source root from .speccrewrc"/>
+    <field name="language" required="false" type="string" desc="User language (auto-detected)"/>
+    <field name="user_requirement" required="false" type="string" desc="User requirement text for module matching"/>
+    <field name="update_progress_script" required="true" type="string" desc="Absolute path to update-progress.js script"/>
+  </block>
+
+  <!-- ========== Phase 1 Mandatory Rules ========== -->
+  <block type="rule" id="P1-R1" level="mandatory" desc="Phase 1 Mandatory Constraints">
+    <field name="text">DO NOT manually search directories or construct status reports yourself - MUST dispatch Worker with speccrew-pm-knowledge-detector skill</field>
+    <field name="text">DO NOT create features-*.json files manually - ALL features files MUST be generated by scripts via Worker</field>
+    <field name="text">DO NOT execute knowledge-base scripts via Bash - ALL script execution MUST happen inside Worker Agents</field>
+    <field name="text">Output files MUST go to knowledges/base/sync-state/knowledge-bizs/ - NEVER write to knowledges/techs/*/sync-state/</field>
+  </block>
+
+  <!-- ========== Step 1.1: Knowledge Base Status Detection ========== -->
+  <block type="task" id="P1-B1" action="dispatch-to-worker" status="pending" desc="Dispatch knowledge detector worker">
+    <field name="agent">speccrew-task-worker</field>
+    <field name="skill">speccrew-pm-knowledge-detector</field>
+    <field name="context">
+      workspace_path: ${workspace_path}
+      sync_state_bizs_dir: ${sync_state_bizs_dir}
+      configs_dir: ${configs_dir}
+    </field>
+    <field name="output" var="knowledge_status"/>
+  </block>
+
+  <!-- ========== Step 1.2: Three-Path Gateway ========== -->
+  <block type="gateway" id="P1-G1" mode="exclusive" desc="Route based on knowledge status">
+    
+    <!-- ==================== Path A: Full Knowledge ==================== -->
+    <!-- System overview and detailed module documentation are available -->
+    <branch test="${knowledge_status.status} == 'full'" name="Path A: Full Knowledge">
+      
+      <!-- Load system overview summary via Worker -->
+      <block type="task" id="P1A-B1" action="dispatch-to-worker" status="pending" desc="Read system-overview.md summary">
+        <field name="agent">speccrew-task-worker</field>
+        <field name="skill">speccrew-pm-system-summary-reader</field>
+        <field name="context">
+          system_overview_path: ${knowledge_status.system_overview_path}
+          language: ${language}
+        </field>
+        <field name="output" var="system_context"/>
+      </block>
+      
+      <block type="event" id="P1A-E1" action="log" desc="Log full knowledge path">
+        <field name="message">✅ Full knowledge base detected. System overview loaded. Proceeding to Phase 2.</field>
+      </block>
+    </branch>
+
+    <!-- ==================== Path B: Lite Knowledge ==================== -->
+    <!-- Feature inventory exists but detailed analysis may be incomplete -->
+    <branch test="${knowledge_status.status} == 'lite'" name="Path B: Lite Knowledge">
+      
+      <!-- Path B Recovery Check: Check DISPATCH-PROGRESS.json existence -->
+      <block type="task" id="P1B-B0" action="check-file" status="pending" desc="Check DISPATCH-PROGRESS.json existence">
+        <field name="path" value="${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"/>
+        <field name="output" var="dispatch_progress_exists"/>
+      </block>
+
+      <block type="gateway" id="P1B-G0" mode="exclusive" desc="Recovery checkpoint">
+        <!-- Resume from Step 3 if pending tasks exist -->
+        <branch test="${dispatch_progress_exists} == true" name="Resume from Step 3">
+          <block type="task" id="P1B-B0-READ" action="read-json" status="pending" desc="Read DISPATCH-PROGRESS.json">
+            <field name="path" value="${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"/>
+            <field name="output" var="dispatch_progress"/>
+          </block>
+          <block type="gateway" id="P1B-G0-CHK" mode="exclusive" desc="Check progress status">
+            <branch test="${dispatch_progress.pending_count} == 0 AND ${dispatch_progress.completed_count} > 0" name="All Completed">
+              <block type="set-variable" id="P1B-V0-SKIP" name="skip_to_step5" value="true"/>
+            </branch>
+            <branch default="true" name="Has Pending Tasks">
+              <block type="set-variable" id="P1B-V0-RESUME" name="resume_from_step3" value="true"/>
+            </branch>
+          </block>
+        </branch>
+        <branch default="true" name="Start from Step 1">
+          <block type="set-variable" id="P1B-V0-START" name="start_from_step1" value="true"/>
+        </branch>
+      </block>
+
+      <!-- ===== Path B Step 1: Module Matching ===== -->
+      <block type="gateway" id="P1B-G1" mode="exclusive" desc="Skip matcher if resuming">
+        <branch test="${start_from_step1} == true" name="Run Module Matcher">
+          <block type="task" id="P1B-B1" action="dispatch-to-worker" status="pending" desc="Dispatch module matcher worker">
+            <field name="agent">speccrew-task-worker</field>
+            <field name="skill">speccrew-pm-module-matcher</field>
+            <field name="context">
+              sync_state_bizs_dir: ${sync_state_bizs_dir}
+              requirement_text: ${user_requirement}
+              language: ${language}
+            </field>
+            <field name="output" var="matched_modules"/>
+          </block>
+
+          <!-- ===== Path B Step 1.5: Initialize Dispatch Progress ===== -->
+          <!-- Save matcher result to temporary file -->
+          <block type="task" id="P1B-B1-5-SAVE" action="write-json" status="pending" desc="Save matcher result">
+            <field name="path" value="${workspace_path}/knowledges/bizs/.matcher-result.json"/>
+            <field name="data" value="${matched_modules}"/>
+          </block>
+
+          <!-- Run dispatch progress initialization script -->
+          <block type="task" id="P1B-B1-5-INIT" action="run-script" status="pending" desc="Initialize DISPATCH-PROGRESS.json">
+            <field name="command">node "${update_progress_script}" init-knowledge-tasks --file "${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json" --matcher-result "${workspace_path}/knowledges/bizs/.matcher-result.json" --features-dir "${workspace_path}/knowledges/bizs"</field>
+            <field name="output" var="init_result"/>
+          </block>
+
+          <!-- HARD GATE: DISPATCH-PROGRESS.json must exist -->
+          <block type="rule" id="P1B-R1" level="mandatory" desc="Dispatch Progress Gate">
+            <field name="text">HARD GATE: DISPATCH-PROGRESS.json MUST exist before proceeding to Step 2</field>
+            <field name="text">DO NOT proceed until file is created and contains tasks</field>
+          </block>
+        </branch>
+        <branch default="true" name="Skip - Resuming"/>
+      </block>
+
+      <!-- ===== Path B Step 2: Generate Analyze Task Plan ===== -->
+      <block type="gateway" id="P1B-G2" mode="exclusive" desc="Skip task plan if resuming">
+        <branch test="${resume_from_step3} != true AND ${skip_to_step5} != true" name="Generate Task Plans">
+          <block type="task" id="P1B-B2" action="read-json" status="pending" desc="Read DISPATCH-PROGRESS.json">
+            <field name="path" value="${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"/>
+            <field name="output" var="dispatch_tasks"/>
+          </block>
+
+          <!-- For each matched module, dispatch module-initializer -->
+          <block type="loop" id="P1B-L2" mode="sequential" desc="Generate analyze task plans">
+            <field name="items" value="${matched_modules.modules}"/>
+            
+            <block type="task" id="P1B-B2-WORKER" action="dispatch-to-worker" status="pending" desc="Execute module initializer">
+              <field name="agent">speccrew-task-worker</field>
+              <field name="skill">speccrew-pm-module-initializer</field>
+              <field name="context">
+                source_path: ${source_path}
+                module_name: ${item.module_name}
+                platform_id: ${item.platform_id}
+                platform_type: ${item.platform_type}
+                platform_subtype: ${item.platform_subtype}
+                tech_stack: ${item.tech_stack}
+                features_file: ${sync_state_bizs_dir}/features-${item.platform_id}.json
+                output_path: ${workspace_path}/knowledges
+                completed_dir: ${sync_state_bizs_dir}/completed
+                sourceFile: features-${item.platform_id}.json
+                language: ${language}
+                workspace_path: ${workspace_path}
+              </field>
+            </block>
+          </block>
+        </branch>
+        <branch default="true" name="Skip - Resuming"/>
+      </block>
+
+      <!-- ===== Path B Step 3: Execute Feature Analysis (Parallel Dispatch) ===== -->
+      <!-- MANDATORY: Process ALL pending tasks without stopping for user confirmation -->
+      <block type="rule" id="P1B-R3" level="mandatory" desc="Step 3 Continuous Execution">
+        <field name="text">CONTINUOUS EXECUTION: Process ALL pending tasks without stopping for user confirmation</field>
+        <field name="text">DO NOT ask "do you want to continue?" mid-way - scope was determined by matcher</field>
+      </block>
+
+      <block type="gateway" id="P1B-G3" mode="exclusive" desc="Skip analysis if all completed">
+        <branch test="${skip_to_step5} != true" name="Execute Feature Analysis">
+          <block type="task" id="P1B-B3-READ" action="read-json" status="pending" desc="Read current progress">
+            <field name="path" value="${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"/>
+            <field name="output" var="analysis_tasks"/>
+          </block>
+
+          <!-- Parallel loop for feature analysis dispatch -->
+          <!-- max-concurrency=5 for batch processing -->
+          <block type="loop" id="P1B-L3" mode="parallel" max-concurrency="5" desc="Execute feature analysis workers">
+            <field name="items" value="${analysis_tasks.tasks[?status=='pending']}"/>
+            
+            <block type="task" id="P1B-B3-WORKER" action="dispatch-to-worker" status="pending" desc="Execute feature analyzer">
+              <field name="agent">speccrew-task-worker</field>
+              <field name="skill">${item.analyzer_skill}</field>
+              <field name="context">
+                fileName: ${item.fileName}
+                sourcePath: ${source_path}/${item.sourcePath}
+                documentPath: ${workspace_path}/${item.documentPath}
+                module: ${item.module}
+                platform_id: ${item.platform_id}
+                platform_type: ${item.platform_type}
+                platform_subtype: ${item.platform_subtype}
+                tech_stack: ${item.tech_stack}
+                language: ${language}
+                completed_dir: ${sync_state_bizs_dir}/completed
+                sourceFile: features-${item.platform_id}.json
+              </field>
+              <field name="output" var="analysis_result"/>
+            </block>
+
+            <!-- Update task status after worker completes -->
+            <block type="task" id="P1B-B3-UPDATE" action="run-script" status="pending" desc="Update task status">
+              <field name="command">node "${update_progress_script}" update-task --file "${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json" --task-id "${item.id}" --status completed</field>
+            </block>
+          </block>
+
+          <!-- ===== Path B Step 3.5: Generate Graph Data ===== -->
+          <!-- MUST complete before Step 4 - Graph data enriches module summaries -->
+          <block type="event" id="P1B-E3-5" action="log" desc="Start graph data generation">
+            <field name="message">📊 Generating graph data for completed analyses...</field>
+          </block>
+
+          <!-- Read completed tasks for graph generation -->
+          <block type="task" id="P1B-B3-5-READ" action="read-json" status="pending" desc="Read completed tasks">
+            <field name="path" value="${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"/>
+            <field name="output" var="completed_tasks"/>
+          </block>
+
+          <!-- Parallel graph generation for API analyses -->
+          <block type="loop" id="P1B-L3-5-API" mode="parallel" max-concurrency="5" desc="Generate API graph data">
+            <field name="items" value="${completed_tasks.tasks[?status=='completed' AND analyzer_skill=='speccrew-knowledge-bizs-api-analyze']}"/>
+            
+            <block type="task" id="P1B-B3-5-API-WORKER" action="dispatch-to-worker" status="pending" desc="Execute API graph generator">
+              <field name="agent">speccrew-task-worker</field>
+              <field name="skill">speccrew-knowledge-bizs-api-graph</field>
+              <field name="context">
+                api_analysis_path: ${workspace_path}/${item.documentPath}
+                platform_id: ${item.platform_id}
+                output_dir: ${sync_state_bizs_dir}/completed
+                module: ${item.module}
+                fileName: ${item.fileName}
+                sourcePath: ${item.sourcePath}
+                sourceFile: features-${item.platform_id}.json
+                language: ${language}
+                subpath: ${item.subpath}
+              </field>
+            </block>
+          </block>
+
+          <!-- Parallel graph generation for UI analyses -->
+          <block type="loop" id="P1B-L3-5-UI" mode="parallel" max-concurrency="5" desc="Generate UI graph data">
+            <field name="items" value="${completed_tasks.tasks[?status=='completed' AND analyzer_skill=='speccrew-knowledge-bizs-ui-analyze']}"/>
+            
+            <block type="task" id="P1B-B3-5-UI-WORKER" action="dispatch-to-worker" status="pending" desc="Execute UI graph generator">
+              <field name="agent">speccrew-task-worker</field>
+              <field name="skill">speccrew-knowledge-bizs-ui-graph</field>
+              <field name="context">
+                fileName: ${item.fileName}
+                sourcePath: ${source_path}/${item.sourcePath}
+                documentPath: ${workspace_path}/${item.documentPath}
+                module: ${item.module}
+                platform_type: ${item.platform_type}
+                platform_subtype: ${item.platform_subtype}
+                completed_dir: ${sync_state_bizs_dir}/completed
+                sourceFile: features-${item.platform_id}.json
+                status: success
+                analysisNotes: Graph data generation from UI analysis
+                language: ${language}
+              </field>
+            </block>
+          </block>
+        </branch>
+        <branch default="true" name="Skip - Already Completed"/>
+      </block>
+
+      <!-- ===== Path B Step 4: Generate Module Summaries ===== -->
+      <block type="task" id="P1B-B4-MODULES" action="read-json" status="pending" desc="Get matched module list">
+        <field name="path" value="${workspace_path}/knowledges/bizs/.matcher-result.json"/>
+        <field name="output" var="modules_for_summary"/>
+      </block>
+
+      <block type="loop" id="P1B-L4" mode="parallel" max-concurrency="5" desc="Generate module summaries">
+        <field name="items" value="${modules_for_summary.modules}"/>
+        
+        <block type="task" id="P1B-B4-WORKER" action="dispatch-to-worker" status="pending" desc="Execute module summarizer">
+          <field name="agent">speccrew-task-worker</field>
+          <field name="skill">speccrew-knowledge-module-summarize</field>
+          <field name="context">
+            module_name: ${item.module_name}
+            module_path: ${workspace_path}/knowledges/bizs/${item.platform_id}/${item.module_name}
+            language: ${language}
+          </field>
+        </block>
+      </block>
+
+      <!-- ===== Path B Step 5: Update Features Status ===== -->
+      <block type="task" id="P1B-B5" action="run-script" status="pending" desc="Update features analyzed status">
+        <field name="command">node "${update_progress_script}" update-features-analyzed --features-dir "${sync_state_bizs_dir}" --progress-file "${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"</field>
+      </block>
+
+      <!-- ===== Path B Step 6: Generate System Overview ===== -->
+      <!-- This step MUST complete before Phase 1 exits -->
+      <block type="task" id="P1B-B6" action="dispatch-to-worker" status="pending" desc="Generate system overview">
+        <field name="agent">speccrew-task-worker</field>
+        <field name="skill">speccrew-knowledge-system-summarize</field>
+        <field name="context">
+          modules_path: ${workspace_path}/knowledges/bizs
+          output_path: ${workspace_path}/knowledges/bizs
+          language: ${language}
+        </field>
+        <field name="output" var="system_overview_result"/>
+      </block>
+
+      <!-- ===== Path B Step 7: Cleanup Intermediate Files ===== -->
+      <!-- Only execute after confirming Step 6 completed successfully -->
+      <block type="rule" id="P1B-R7" level="mandatory" desc="Step 7 Prerequisite">
+        <field name="text">Step 6 MUST complete: system-overview.md exists and is non-empty</field>
+        <field name="text">All tasks in DISPATCH-PROGRESS.json must have status "completed"</field>
+      </block>
+
+      <block type="task" id="P1B-B7-VERIFY" action="check-file" status="pending" desc="Verify system-overview.md exists">
+        <field name="path" value="${workspace_path}/knowledges/bizs/system-overview.md"/>
+        <field name="min_size" value="100"/>
+        <field name="output" var="overview_exists"/>
+      </block>
+
+      <block type="task" id="P1B-B7" action="run-script" status="pending" desc="Cleanup intermediate files">
+        <field name="command">Remove-Item "${workspace_path}/knowledges/bizs/.matcher-result.json" -ErrorAction SilentlyContinue; Remove-Item "${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json" -ErrorAction SilentlyContinue</field>
+      </block>
+
+      <block type="event" id="P1B-E7" action="log" desc="Path B completion">
+        <field name="message">✅ Path B complete: Knowledge base initialized. System overview generated.</field>
+      </block>
+    </branch>
+
+    <!-- ==================== Path C: No Knowledge ==================== -->
+    <!-- No knowledge base exists - trigger lightweight feature inventory scan -->
+    <branch test="${knowledge_status.status} == 'none'" name="Path C: No Knowledge">
+      
+      <!-- Mandatory rules for Path C -->
+      <block type="rule" id="P1C-R1" level="mandatory" desc="Path C Mandatory Rules">
+        <field name="text">DO NOT skip to Phase 2 without running feature inventory - this is AUTOMATIC</field>
+        <field name="text">DO NOT ask user whether to run feature inventory - automatic initialization is MANDATORY</field>
+        <field name="text">DO NOT run module-initializer here - deep init is scoped by requirement in Path B</field>
+        <field name="text">DO NOT expose internal concepts (Stage 0, Stage 1) to user</field>
+      </block>
+
+      <!-- C-Step 1: Notify user -->
+      <block type="event" id="P1C-E1" action="log" desc="Inform user about initialization">
+        <field name="message">No business knowledge base detected. Scanning project structure to discover available modules...</field>
+      </block>
+
+      <!-- C-Step 2: Dispatch Worker to generate feature inventory -->
+      <block type="task" id="P1C-B2" action="dispatch-to-worker" status="pending" desc="Generate feature inventory">
+        <field name="agent">speccrew-task-worker</field>
+        <field name="skill">speccrew-knowledge-bizs-init-features</field>
+        <field name="context">
+          workspace_path: ${workspace_path}
+          language: ${language}
+          sync_state_bizs_dir: ${sync_state_bizs_dir}
+          configs_dir: ${configs_dir}
+          ide_skills_dir: ${ide_skills_dir}
+        </field>
+        <field name="output" var="init_features_result"/>
+      </block>
+
+      <!-- C-Step 3: Re-run detector to verify status changed -->
+      <block type="task" id="P1C-B3" action="dispatch-to-worker" status="pending" desc="Re-run knowledge detector">
+        <field name="agent">speccrew-task-worker</field>
+        <field name="skill">speccrew-pm-knowledge-detector</field>
+        <field name="context">
+          workspace_path: ${workspace_path}
+          sync_state_bizs_dir: ${sync_state_bizs_dir}
+          configs_dir: ${configs_dir}
+        </field>
+        <field name="output" var="recheck_status"/>
+      </block>
+
+      <!-- C-Gateway: Check detection result and route accordingly -->
+      <block type="gateway" id="P1C-G1" mode="exclusive" desc="Check re-detection result">
+        
+        <!-- If status is now "lite", execute Path B sequence -->
+        <branch test="${recheck_status.status} == 'lite'" name="Proceed to Path B">
+          <block type="event" id="P1C-E2" action="log" desc="Log transition to Path B">
+            <field name="message">✅ Feature inventory generated. Executing Path B for module matching and deep initialization...</field>
+          </block>
+          
+          <!-- Execute Path B Step 1: Module Matcher -->
+          <block type="task" id="P1C-B-PATHB-1" action="dispatch-to-worker" status="pending" desc="Dispatch module matcher worker">
+            <field name="agent">speccrew-task-worker</field>
+            <field name="skill">speccrew-pm-module-matcher</field>
+            <field name="context">
+              sync_state_bizs_dir: ${sync_state_bizs_dir}
+              requirement_text: ${user_requirement}
+              language: ${language}
+            </field>
+            <field name="output" var="matched_modules"/>
+          </block>
+
+          <!-- Execute Path B Step 1.5: Initialize Dispatch Progress -->
+          <block type="task" id="P1C-B-PATHB-1-5-SAVE" action="write-json" status="pending" desc="Save matcher result">
+            <field name="path" value="${workspace_path}/knowledges/bizs/.matcher-result.json"/>
+            <field name="data" value="${matched_modules}"/>
+          </block>
+
+          <block type="task" id="P1C-B-PATHB-1-5-INIT" action="run-script" status="pending" desc="Initialize DISPATCH-PROGRESS.json">
+            <field name="command">node "${update_progress_script}" init-knowledge-tasks --file "${workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json" --matcher-result "${workspace_path}/knowledges/bizs/.matcher-result.json" --features-dir "${workspace_path}/knowledges/bizs"</field>
+          </block>
+
+          <!-- Continue with Path B Steps 2-7 inline -->
+          <!-- Note: These steps are abbreviated here - full implementation would mirror Path B above -->
+          <block type="set-variable" id="P1C-V-STATUS" name="knowledge_status" value="lite"/>
+          <block type="set-variable" id="P1C-V-CONTEXT" name="system_context" value="Feature inventory available. Module matching completed."/>
+        </branch>
+
+        <!-- If status is still "none", report error -->
+        <branch test="${recheck_status.status} == 'none'" name="Initialization Failed">
+          <block type="event" id="P1C-E3" action="error" desc="Report initialization failure">
+            <field name="message">❌ Feature inventory generation failed. Unable to initialize knowledge base.</field>
+          </block>
+          <block type="set-variable" id="P1C-V-FAIL" name="knowledge_status" value="none"/>
+          <block type="set-variable" id="P1C-V-FAIL-CTX" name="system_context" value="Knowledge base initialization failed. Proceeding in degraded mode."/>
+        </branch>
+
+        <!-- If status is "full" (rare but possible), use full knowledge path -->
+        <branch test="${recheck_status.status} == 'full'" name="Full Knowledge Detected">
+          <block type="task" id="P1C-B-FULL" action="dispatch-to-worker" status="pending" desc="Read system-overview.md summary">
+            <field name="agent">speccrew-task-worker</field>
+            <field name="skill">speccrew-pm-system-summary-reader</field>
+            <field name="context">
+              system_overview_path: ${recheck_status.system_overview_path}
+              language: ${language}
+            </field>
+            <field name="output" var="system_context"/>
+          </block>
+          <block type="set-variable" id="P1C-V-FULL" name="knowledge_status" value="full"/>
+        </branch>
+      </block>
+    </branch>
+  </block>
+
+  <!-- ========== Output ========== -->
+  <block type="output" id="O1" desc="Phase 1 Knowledge Check Result">
+    <field name="knowledge_status" from="${knowledge_status.status}" type="string" desc="full | lite | none"/>
+    <field name="system_context" from="${system_context}" type="string" desc="Summary from system-overview.md or module list"/>
+    <field name="matched_modules" from="${matched_modules}" type="object" desc="List of modules identified as relevant"/>
+    <field name="available_platforms" from="${knowledge_status.available_platforms}" type="array" desc="List of detected platforms"/>
+    <field name="module_count" from="${knowledge_status.module_count}" type="number" desc="Total module count"/>
+    <field name="features_files" from="${knowledge_status.features_files}" type="array" desc="Generated features file paths"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-pm-phase2-complexity-assess/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: speccrew-pm-phase2-complexity-assess
+description: Complexity assessment and skill routing for PM Phase 2. Validates knowledge initialization completeness, evaluates requirement complexity across 5 dimensions, and routes to appropriate PRD workflow (simple vs full pipeline). Use after Phase 1 knowledge detection completes.
+tools: Read, Grep
+---
+
+# Phase 2: Complexity Assessment & Skill Routing
+
+Assess requirement complexity and determine the appropriate skill routing path for PRD generation.
+
+## Trigger Scenarios
+
+- "Assess requirement complexity"
+- "Determine PRD workflow path"
+- "Should I use simple or complex PRD workflow?"
+- "Route to appropriate PRD skill"
+- "Check if knowledge initialization is complete"
+
+## User
+
+PM Agent (speccrew-product-manager)
+
+## Input
+
+| Parameter | Type | Required | Description |
+|-----------|------|----------|-------------|
+| user_requirement | string | Yes | User requirement description or document path |
+| workspace_path | string | Yes | Absolute path to speccrew-workspace root |
+| knowledge_status | object | Yes | Knowledge status from Phase 1 (status, system_overview_path) |
+| language | string | No | Target language for output (auto-detected) |
+
+## Output
+
+| Field | Type | Description |
+|-------|------|-------------|
+| complexity_level | string | simple / moderate / complex |
+| route | string | speccrew-pm-requirement-simple or full-pipeline |
+| complexity_details | object | Detailed breakdown of 5-dimension assessment |
+| verification_status | string | Knowledge initialization verification result |
+
+## AgentFlow Definition
+
+<!-- @agentflow: workflow.agentflow.xml -->
+
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
+
+## Complexity Assessment Matrix
+
+### 5-Dimension Evaluation
+
+| Dimension | Simple | Moderate | Complex |
+|-----------|--------|----------|---------|
+| **Functional Scope** | 1-2 modules, 1-5 features | 2-3 modules, 5-10 features | 3+ modules, 6+ features |
+| **Technical Complexity** | No new tech, 0-2 integrations | 1 new tech, 2-4 integrations | 2+ new techs, 5+ integrations |
+| **Business Rules** | Simple conditions, no state machine | Moderate branching, basic state machine | Complex branching, full state machine |
+| **Data Complexity** | 1-3 entities, simple relationships | 4-6 entities, moderate relationships | 7+ entities, complex relationships |
+| **Team/Time Constraints** | Standard timeline, single team | Moderate constraints | Tight deadline, multiple teams |
+
+### Decision Rules
+
+**→ Simple** (ANY of these):
+- Adding/modifying fields on an existing page
+- Minor feature enhancement within 1-2 modules
+- Business logic adjustment
+- Bug fix documentation
+- Scope: ≤ 5 features, ≤ 2 modules
+
+**→ Moderate** (ANY of these):
+- 2-3 modules involved
+- 5-10 features expected
+- Some cross-module dependencies
+- Standard new feature development
+
+**→ Complex** (ANY of these):
+- New system or major subsystem development
+- Involves 3+ modules
+- Requires 6+ features
+- Needs cross-module dependency management
+- User explicitly requests comprehensive analysis
+
+### Skill Routing
+
+| Complexity | Route | Workflow |
+|------------|-------|----------|
+| simple | speccrew-pm-requirement-simple | Single PRD, streamlined 6-step flow |
+| moderate | full-pipeline | clarify → model → analysis (Master-Sub PRD) |
+| complex | full-pipeline | clarify → model → analysis (Master-Sub PRD) |
+
+> **Default to Simple when in doubt**. It's easier to escalate from simple to complex than to simplify an over-engineered analysis.
+
+## Checklist
+
+- [ ] DISPATCH-PROGRESS.json exists and counts.pending == 0
+- [ ] Knowledge initialization verified complete
+- [ ] User requirement analyzed for module count
+- [ ] Functional scope assessed (modules, features)
+- [ ] Technical complexity evaluated (new tech, integrations)
+- [ ] Business rules complexity determined (conditions, state machine)
+- [ ] Data complexity assessed (entities, relationships)
+- [ ] Team/time constraints considered
+- [ ] Complexity level determined (simple/moderate/complex)
+- [ ] Skill route selected and output
+
+## Key Rules
+
+1. **MANDATORY Verification**: Phase 2.0 knowledge initialization verification CANNOT be skipped
+2. **Pending Tasks Block**: If `counts.pending > 0`, return to Phase 1 Path B - do NOT proceed
+3. **Read-Only Assessment**: This skill performs assessment only, no file modifications
+4. **Escalation Path**: Simple workflow can escalate to complex if scope expands during execution
+5. **Single Gateway**: Use exclusive gateway for routing decision - only one path selected