speccrew 0.7.15 → 0.7.16

package/.speccrew/agents/speccrew-product-manager.md

@@ -776,11 +776,11 @@ Based on the indicators above:
 
 ## Phase 3: Requirement Clarification
 
-Invoke `speccrew-pm-requirement-clarify` skill to perform requirement clarification.
+**CRITICAL:** PM Agent MUST NOT perform requirement clarification directly. Instead, dispatch a Worker Agent with `speccrew-pm-requirement-clarify` skill.
 
 ### 3.1 Prepare Parameters
 
-Pass the following parameters to the skill:
+Construct the context for the Worker Agent:
 
 | Parameter | Value | Description |
 |-----------|-------|-------------|
@@ -788,23 +788,32 @@ Pass the following parameters to the skill:
 | `iteration_path` | `{iterations_dir}/{iteration}` (absolute path from Phase 0.6) | Current iteration directory |
 | `complexity_hint` | `simple` or `complex` (from Phase 2 assessment) | Complexity assessment result |
 | `knowledge_status` | `full` / `lite` / `none` (from Phase 1) | Knowledge base availability for clarification strategy |
+| `language` | User's language (e.g., `zh`, `en`) | Language for clarification output |
 
-### 3.2 Invoke Clarification Skill
+### 3.2 Dispatch Clarification Worker
 
-**Action:** Invoke `speccrew-pm-requirement-clarify` skill with the parameters above.
+**Action:** Create a Task for `speccrew-task-worker` with `speccrew-pm-requirement-clarify` skill.
 
-**Skill Location:** Search with glob `**/speccrew-pm-requirement-clarify/SKILL.md`
+**FORBIDDEN:**
+- DO NOT invoke `speccrew-pm-requirement-clarify` skill directly via Skill tool
+- DO NOT perform clarification rounds yourself
+- DO NOT generate `.clarification-summary.md` manually
 
-### 3.3 Wait for Completion
+**REQUIRED:**
+- MUST use Task tool to dispatch Worker Agent
+- MUST pass all context parameters to the Worker
+- MUST wait for Worker to complete and return results
 
-The skill will:
+### 3.3 Worker Execution
+
+The dispatched Worker Agent will:
 1. Load requirement document and system knowledge
 2. Execute clarification rounds (chat-based for simple, file-based for complex)
 3. Perform sufficiency checks (4 checks)
 4. Generate `.clarification-summary.md`
 5. Initialize `.checkpoints.json`
 
-**Wait for skill to complete and return.**
+**Wait for Worker to complete and return.**
 
 ### 3.4 Validate Output
 
@@ -931,8 +940,9 @@ Clarification File: {iteration_path}/01.product-requirement/.clarification-summa
 
 > ⚠️ **PM AGENT ORCHESTRATION PRINCIPLE (Phase 4-6)**
 > You are the ORCHESTRATOR, NOT the WRITER:
-> - Phase 4a (Model): DO NOT do ISA-95 analysis yourself → Skill does it
-> - Phase 4b (Generate): DO NOT generate Master PRD yourself → Skill generates it
+> - Phase 4a (Model): DO NOT do ISA-95 analysis yourself → Dispatch Worker with `speccrew-pm-requirement-model` skill
+> - Phase 4a.5 (Confirm): MUST stop for user confirmation after module design → Wait for explicit user approval
+> - Phase 4b (Generate): DO NOT generate Master PRD yourself → Dispatch Worker with `speccrew-pm-requirement-analysis` skill
 > - Phase 5: DO NOT generate Sub-PRD yourself → Workers generate them
 > - Phase 6: DO NOT modify PRD content yourself → Only verify and present
 > - **If ANY Skill fails: STOP and report error to user. DO NOT generate content as fallback.**
@@ -947,19 +957,20 @@ Based on the complexity from `.clarification-summary.md`, invoke the appropriate
 
 **Flow:**
 ```
-Invoke speccrew-pm-requirement-simple
-  → Pass: iteration_path, clarification_file
+Dispatch Worker with speccrew-pm-requirement-simple
+  → Pass: iteration_path, clarification_file, language
   → Wait for: Single PRD file
   → Validate: PRD file exists and size > 2KB
   → IF fails → ABORT (ORCHESTRATOR rule)
   → IF succeeds → Skip Phase 5, go to Phase 6
 ```
 
-**Parameters:**
+**Parameters (for Worker dispatch):**
 | Parameter | Value |
 |-----------|-------|
 | `iteration_path` | `{iterations_dir}/{iteration}` (absolute path from Phase 0.6) |
 | `clarification_file` | `{iteration_path}/01.product-requirement/.clarification-summary.md` |
+| `language` | User's language (e.g., `zh`, `en`) |
 
 ---
 
@@ -969,32 +980,47 @@ Invoke speccrew-pm-requirement-simple
 
 **Flow:**
 ```
-Step 4a: Invoke speccrew-pm-requirement-model
-  → Pass: iteration_path, clarification_file
+Step 4a: Dispatch Worker with speccrew-pm-requirement-model
+  → Pass: iteration_path, clarification_file, language
   → Wait for: .module-design.md
   → Validate: .module-design.md exists + module count >= 2
   → IF fails → ABORT (ORCHESTRATOR rule: do NOT do module decomposition yourself)
 
-Step 4b: Invoke speccrew-pm-requirement-analysis
-  → Pass: iteration_path, clarification_file, module_design_file
+Step 4a.5: User Confirmation Gate (MANDATORY)
+  → Present: Module design summary to user
+  → Request: Explicit confirmation before proceeding
+  → Checkpoint: Update requirement_modeling_confirmed
+  → IF user requests changes → Return to Phase 3 with feedback
+  → IF user confirms → Proceed to Step 4b
+
+Step 4b: Dispatch Worker with speccrew-pm-requirement-analysis
+  → Pass: iteration_path, clarification_file, module_design_file, language
   → Wait for: Master PRD + Dispatch Plan
   → Validate: Master PRD exists + Dispatch Plan has modules array
   → IF fails → ABORT (ORCHESTRATOR rule: do NOT generate PRD yourself)
   → IF succeeds → MANDATORY: Execute Phase 5 (Sub-PRD Worker Dispatch)
 ```
 
-**Step 4a Parameters:**
+**Step 4a Parameters (for Worker dispatch):**
 | Parameter | Value |
 |-----------|-------|
 | `iteration_path` | `{iterations_dir}/{iteration}` (absolute path from Phase 0.6) |
 | `clarification_file` | `{iteration_path}/01.product-requirement/.clarification-summary.md` |
+| `language` | User's language (e.g., `zh`, `en`) |
+
+**Step 4a.5 User Confirmation:**
+| Checkpoint | Value |
+|------------|-------|
+| `checkpoint_name` | `requirement_modeling_confirmed` |
+| `description` | "User confirmed module design results" |
 
-**Step 4b Parameters:**
+**Step 4b Parameters (for Worker dispatch):**
 | Parameter | Value |
 |-----------|-------|
 | `iteration_path` | `{iterations_dir}/{iteration}` (absolute path from Phase 0.6) |
 | `clarification_file` | `{iteration_path}/01.product-requirement/.clarification-summary.md` |
 | `module_design_file` | `{iteration_path}/01.product-requirement/.module-design.md` |
+| `language` | User's language (e.g., `zh`, `en`) |
 
 ---
 
@@ -1086,9 +1112,10 @@ Step 4b: Invoke speccrew-pm-requirement-analysis
 >
 > | Phase | Skill | ORCHESTRATOR Rule |
 > |-------|-------|-------------------|
-> | Phase 3 | `speccrew-pm-requirement-clarify` | DO NOT clarify requirements yourself — Skill handles all clarification rounds |
-> | Phase 4a | `speccrew-pm-requirement-model` | DO NOT perform ISA-95 analysis or module decomposition yourself |
-> | Phase 4b | `speccrew-pm-requirement-analysis` | DO NOT generate Master PRD or Dispatch Plan yourself |
+> | Phase 3 | `speccrew-pm-requirement-clarify` | DO NOT clarify requirements yourself — Dispatch Worker to handle all clarification rounds |
+> | Phase 4a | `speccrew-pm-requirement-model` | DO NOT perform ISA-95 analysis or module decomposition yourself — Dispatch Worker |
+> | Phase 4a.5 | N/A (User Gate) | MUST stop for user confirmation — Wait for explicit approval before Phase 4b |
+> | Phase 4b | `speccrew-pm-requirement-analysis` | DO NOT generate Master PRD or Dispatch Plan yourself — Dispatch Worker |
 > | Phase 5 | `speccrew-pm-sub-prd-generate` (via workers) | DO NOT generate Sub-PRD content yourself |
 > | Phase 6 | PM Agent verification | DO NOT modify PRD content — only verify and present |
 >

package/.speccrew/skills/speccrew-pm-requirement-clarify/SKILL.md

@@ -21,6 +21,7 @@ Requirement clarification with dual-mode support. Produces `.clarification-summa
 | `requirement_file` | string | Yes | Path to requirement document |
 | `iteration_path` | string | Yes | Path to iteration directory |
 | `complexity_hint` | enum | No | `simple` or `complex`. Auto-detect if not provided |
+| `max_clarification_rounds` | number | No | Maximum clarification rounds (default: 5) |
 
 ## Methodology Foundation
 
@@ -32,6 +33,13 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 
 > **DO NOT include:** API definitions, DB structures, code snippets, technical terminology. These belong to Feature Designer or System Designer.
 
+## Templates Used
+
+| Template | Path | Purpose |
+|----------|------|---------|
+| Clarification Questions | `templates/CLARIFICATION-QUESTIONS-TEMPLATE.md` | Round-based questionnaire for user clarification |
+| Clarification Summary | `templates/CLARIFICATION-SUMMARY-TEMPLATE.md` | Final summary document with all Q&A and decisions |
+
 ---
 
 # AgentFlow Definition
@@ -47,9 +55,13 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 - [ ] Requirement document loaded
 - [ ] System knowledge loaded (if exists)
 - [ ] Complexity mode determined
+- [ ] Loop variables initialized (`sufficiency_checks_passed`, `round_number`)
 - [ ] Clarification conducted (appropriate mode)
-- [ ] All 4 Sufficiency Checks passed
-- [ ] `.clarification-summary.md` created
+- [ ] Multi-round clarification executed until ALL 4 Sufficiency Checks pass
+- [ ] Each round generates `.clarification-questions-round-{N}.md`
+- [ ] Round counter incremented after each iteration
+- [ ] Maximum 5 rounds enforced (safety valve)
+- [ ] `.clarification-summary.md` created from template
 - [ ] `.checkpoints.json` initialized via script
 
 ---
@@ -58,8 +70,13 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 
 **Must do:**
 - Always perform at least 1 clarification round
+- **MANDATORY**: Execute multiple rounds until ALL 4 sufficiency checks pass
 - Use file-based for complex mode or 4+ questions
 - Pass all 4 Sufficiency Checks
+- Generate `.clarification-questions-round-{N}.md` for each round
+- Update `sufficiency_checks_passed` variable after each sufficiency check
+- Increment `round_number` after each round
+- Maximum 5 rounds allowed (safety valve)
 - Use `update-progress.js` for JSON files
 - After completion, return control to PM Agent for user confirmation — DO NOT auto-proceed to PRD generation
 

package/.speccrew/skills/speccrew-pm-requirement-clarify/templates/CLARIFICATION-QUESTIONS-TEMPLATE.md

@@ -0,0 +1,49 @@
+# 需求澄清问卷 - Round {round_number}
+
+> **Iteration**: {iteration_name}
+> **Date**: {date}
+> **Complexity**: {complexity_level}
+
+## 澄清背景
+
+基于用户需求："{requirement_summary}"，以下问题需要进一步确认。
+
+## 待确认事项
+
+### 🎯 业务范围与边界
+
+| # | 问题 | 优先级 | 用户回答 |
+|---|------|--------|---------|
+| 1 | {question} | {priority} | _待回答_ |
+
+### 👥 用户角色与权限
+
+| # | 问题 | 优先级 | 用户回答 |
+|---|------|--------|---------|
+| 1 | {question} | {priority} | _待回答_ |
+
+### 🔄 业务规则与流程
+
+| # | 问题 | 优先级 | 用户回答 |
+|---|------|--------|---------|
+| 1 | {question} | {priority} | _待回答_ |
+
+### 🔗 集成与依赖
+
+| # | 问题 | 优先级 | 用户回答 |
+|---|------|--------|---------|
+| 1 | {question} | {priority} | _待回答_ |
+
+### ⚡ 性能与约束
+
+| # | 问题 | 优先级 | 用户回答 |
+|---|------|--------|---------|
+| 1 | {question} | {priority} | _待回答_ |
+
+---
+
+## 填写说明
+
+1. 请在"用户回答"列直接填写您的回答
+2. 如果某个问题不适用，请填写"N/A"并简要说明原因
+3. 如需补充信息，可在回答后追加说明

package/.speccrew/skills/speccrew-pm-requirement-clarify/templates/CLARIFICATION-SUMMARY-TEMPLATE.md

@@ -0,0 +1,52 @@
+# 需求澄清总结
+
+> **Iteration**: {iteration_name}
+> **Total Rounds**: {total_rounds}
+> **Date**: {date}
+> **Final Sufficiency**: {sufficiency_result} ({checks_passed}/4)
+
+## 1. 需求概述
+
+{requirement_overview}
+
+## 2. 复杂度评估
+
+| 维度 | 评估 | 理由 |
+|------|------|------|
+| 业务复杂度 | {business_complexity} | {reason} |
+| 技术复杂度 | {technical_complexity} | {reason} |
+| 集成复杂度 | {integration_complexity} | {reason} |
+| **综合判定** | **{overall_complexity}** | |
+
+## 3. 关键决策记录
+
+| # | 决策项 | 决策结果 | 确认轮次 |
+|---|--------|---------|---------|
+| 1 | {decision_item} | {decision_result} | Round {N} |
+
+## 4. 澄清 Q&A 汇总
+
+### Round {N}
+
+| # | 问题 | 回答 | 分类 |
+|---|------|------|------|
+| 1 | {question} | {answer} | {category} |
+
+## 5. 充分性检查结果
+
+| # | 检查项 | 状态 | 说明 |
+|---|--------|------|------|
+| 1 | 范围边界清晰 | {status} | {detail} |
+| 2 | 关键业务规则已文档化 | {status} | {detail} |
+| 3 | 优先级/分期决策已确定 | {status} | {detail} |
+| 4 | 集成边界已识别 | {status} | {detail} |
+
+## 6. 遗留问题与风险
+
+| # | 问题/风险 | 影响 | 建议处理方式 |
+|---|----------|------|------------|
+| 1 | {issue} | {impact} | {suggestion} |
+
+## 7. 下一步建议
+
+{next_steps}

package/.speccrew/skills/speccrew-pm-requirement-clarify/workflow.agentflow.xml

@@ -14,6 +14,13 @@
   <!-- ============================================================
        Global Constraints
        ============================================================ -->
+  <block type="rule" id="R-MULTIROUND" level="mandatory" desc="Multi-round clarification is MANDATORY">
+    <field name="text">MANDATORY: Clarification MUST execute multiple rounds until ALL 4 sufficiency checks pass.</field>
+    <field name="text">DO NOT terminate after a single round. Each round generates .clarification-questions-round-{N}.md</field>
+    <field name="text">After user answers, perform sufficiency check. If any check fails, generate next round questions.</field>
+    <field name="text">Maximum 5 rounds allowed. If max reached, proceed with warning.</field>
+  </block>
+
   <block type="rule" id="R1" level="mandatory" desc="Execution constraints">
     <field name="text">Always perform at least 1 clarification round</field>
     <field name="text">Use file-based for complex mode or 4+ questions</field>
@@ -69,7 +76,14 @@
       </branch>
     </block>
 
-    <!-- Step 4: Execute Clarification -->
+    <!-- Step 4: Initialize Loop Variables -->
+    <block type="task" id="B6-init" action="set-var" desc="Initialize loop control variables">
+      <field name="sufficiency_checks_passed" value="false"/>
+      <field name="round_number" value="1"/>
+      <field name="max_rounds" value="5"/>
+    </block>
+
+    <!-- Step 5: Execute Clarification -->
     <block type="gateway" id="G2" mode="exclusive" desc="Execute clarification based on mode">
       <branch test="${complexity} == 'simple'" name="Simple Mode Clarification">
         <block type="task" id="B6" action="analyze" desc="Simple mode: 1-3 key questions">
@@ -84,19 +98,28 @@
       </branch>
       <branch test="${complexity} == 'complex'" name="Complex Mode Clarification">
         <!-- Clarification Loop -->
-        <block type="loop" id="L1" condition="sufficiency_checks_passed == false" desc="Clarification rounds until sufficiency">
-          <block type="task" id="B7" action="generate" desc="Create clarification questions file">
-            <field name="output_path" value="${iteration_path}/01.product-requirement/.clarification-questions-round-{round}.md"/>
-            <field name="sections">
-              - Business Background & Goals
-              - Target Users & Scenarios
-              - System Scope & Boundaries
+        <block type="loop" id="L1" condition="sufficiency_checks_passed == false AND round_number <= max_rounds" desc="Clarification rounds until sufficiency">
+          <!-- Load Question Template -->
+          <block type="task" id="B7-load-template" action="read-file" desc="Load clarification questions template">
+            <field name="path" value="${skill_path}/templates/CLARIFICATION-QUESTIONS-TEMPLATE.md"/>
+            <field name="output" var="questions_template"/>
+          </block>
+
+          <block type="task" id="B7" action="generate" desc="Create clarification questions file from template">
+            <field name="template" value="${questions_template}"/>
+            <field name="output_path" value="${iteration_path}/01.product-requirement/.clarification-questions-round-${round_number}.md"/>
+            <field name="vars">
+              - round_number: ${round_number}
+              - iteration_name: ${iteration_name}
+              - date: ${current_date}
+              - complexity_level: ${complexity}
+              - requirement_summary: ${requirement_summary}
             </field>
             <field name="output" var="questions_file"/>
           </block>
 
-          <block type="event" id="E1" action="confirm" title="Clarification Round {round}" type="wait" desc="Wait for user to answer questions">
-            <field name="message">Round {round} questions written. Please fill answers and notify me.</field>
+          <block type="event" id="E1" action="confirm" title="Clarification Round ${round_number}" type="wait" desc="Wait for user to answer questions">
+            <field name="message">Round ${round_number} questions written. Please fill answers and notify me.</field>
           </block>
 
           <block type="task" id="B8" action="read-file" desc="Read answered questions">
@@ -106,6 +129,7 @@
 
           <!-- Sufficiency Check -->
           <block type="task" id="B9" action="analyze" desc="Perform sufficiency check">
+            <field name="input" value="${answered_questions}"/>
             <field name="checks">
               1. Scope boundaries are clear - Explicit in/out scope defined
               2. Key business rules are documented - At least 1 rule identified
@@ -114,24 +138,46 @@
             </field>
             <field name="output" var="sufficiency_result"/>
           </block>
+
+          <!-- Update sufficiency variable based on check result -->
+          <block type="task" id="B9-update" action="set-var" desc="Update sufficiency check status">
+            <field name="sufficiency_checks_passed" value="${sufficiency_result.all_passed}"/>
+            <field name="checks_passed_count" value="${sufficiency_result.passed_count}"/>
+          </block>
+
+          <!-- Increment round number for next iteration -->
+          <block type="task" id="B9-increment" action="set-var" desc="Increment round counter">
+            <field name="round_number" value="${round_number + 1}"/>
+          </block>
         </block>
       </branch>
     </block>
 
-    <!-- Step 5: Generate .clarification-summary.md -->
-    <block type="task" id="B10" action="generate" desc="Generate clarification summary">
+    <!-- Step 6: Generate .clarification-summary.md -->
+    <block type="task" id="B10-load-template" action="read-file" desc="Load summary template">
+      <field name="path" value="${skill_path}/templates/CLARIFICATION-SUMMARY-TEMPLATE.md"/>
+      <field name="output" var="summary_template"/>
+    </block>
+
+    <block type="task" id="B10" action="generate" desc="Generate clarification summary from template">
+      <field name="template" value="${summary_template}"/>
       <field name="output_path" value="${iteration_path}/01.product-requirement/.clarification-summary.md"/>
-      <field name="sections">
-        - Complexity level and rationale
-        - Key decisions table
-        - Clarification Q&A (all rounds)
-        - Sufficiency checks results
-        - Notes
+      <field name="vars">
+        - iteration_name: ${iteration_name}
+        - total_rounds: ${round_number - 1}
+        - date: ${current_date}
+        - sufficiency_result: ${sufficiency_result.all_passed ? 'PASSED' : 'PARTIAL'}
+        - checks_passed: ${sufficiency_result.passed_count}
+        - requirement_overview: ${requirement_summary}
+        - business_complexity: ${complexity}
+        - technical_complexity: ${complexity}
+        - integration_complexity: ${complexity}
+        - overall_complexity: ${complexity}
       </field>
       <field name="output" var="summary_path"/>
     </block>
 
-    <!-- Step 6: Initialize .checkpoints.json -->
+    <!-- Step 7: Initialize .checkpoints.json -->
     <block type="task" id="B11" action="run-script" desc="Initialize checkpoints via script">
       <field name="command">node "${workspace_path}/scripts/update-progress.js" write-checkpoint --file "${iteration_path}/01.product-requirement/.checkpoints.json" --checkpoint requirement_clarification --passed true</field>
       <field name="output" var="checkpoint_result"/>

package/.speccrew/skills/speccrew-product-manager-orchestration/SKILL.md

@@ -25,6 +25,11 @@ tools: Read, Write, Glob, Grep, Bash, Agent
 > - `action="log"` → Output message directly
 > - `action="confirm"` → Present to user and wait for response
 >
+> **CRITICAL DISPATCH RULE:**
+> - PM Agent (Team Leader) MUST NOT execute Skills directly
+> - ALL Skill executions MUST go through `dispatch-to-worker` action
+> - Worker Agent (`speccrew-task-worker`) receives the Skill name and context, then executes the Skill
+>
 > **Step 3**: Execute ALL blocks sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
 
 # Product Manager Orchestration
@@ -34,10 +39,26 @@ Product Manager 的核心编排技能，负责：
 1. **Pipeline Progress Management** - 创建/定位迭代目录，管理工作流进度
 2. **Knowledge Base Detection** - 检测知识库状态并按需初始化
 3. **Complexity Assessment** - 评估需求复杂度，决定简单/复杂路径
-4. **Requirement Clarification** - 调用澄清技能，收集需求细节
-5. **PRD Generation Orchestration** - 协调 PRD 生成（简单路径直接调用，复杂路径分发 Worker）
+4. **Requirement Clarification** - 分发 Worker 执行澄清技能，收集需求细节
+5. **PRD Generation Orchestration** - 协调 PRD 生成（所有 Skill 通过 Worker 分发执行）
 6. **Verification & Confirmation** - 验证 PRD 完整性，等待用户确认
 
+**DISPATCH-TO-WORKER ARCHITECTURE:**
+
+PM Agent 作为 Team Leader，不直接执行任何 Skill。所有 Skill 调用都通过 `dispatch-to-worker` 模式：
+
+| Phase | Action | Skill | Worker |
+|-------|--------|-------|--------|
+| Phase 1 | `dispatch-to-worker` | `speccrew-pm-knowledge-detector` | `speccrew-task-worker` |
+| Phase 1 | `dispatch-to-worker` | `speccrew-pm-system-summary-reader` | `speccrew-task-worker` |
+| Phase 1 | `dispatch-to-worker` | `speccrew-pm-module-matcher` | `speccrew-task-worker` |
+| Phase 1 | `dispatch-to-worker` | `speccrew-knowledge-bizs-init-features` | `speccrew-task-worker` |
+| Phase 3 | `dispatch-to-worker` | `speccrew-pm-requirement-clarify` | `speccrew-task-worker` |
+| Phase 4a | `dispatch-to-worker` | `speccrew-pm-requirement-model` | `speccrew-task-worker` |
+| Phase 4b | `dispatch-to-worker` | `speccrew-pm-requirement-analysis` | `speccrew-task-worker` |
+| Phase 4 (Simple) | `dispatch-to-worker` | `speccrew-pm-requirement-simple` | `speccrew-task-worker` |
+| Phase 5 | `dispatch-to-worker` | `speccrew-pm-sub-prd-generate` | `speccrew-task-worker` |
+
 ## Invocation Method
 
 **CRITICAL**: This skill is loaded directly by Product Manager Agent — do NOT invoke via Worker Agent.
@@ -99,12 +120,18 @@ This agent is an **orchestrator/dispatcher**. Key constraints:
 
 | Phase | Skill | ORCHESTRATOR Rule |
 |-------|-------|-------------------|
-| Phase 3 | `speccrew-pm-requirement-clarify` | DO NOT clarify requirements yourself — Skill handles all clarification rounds |
-| Phase 4a | `speccrew-pm-requirement-model` | DO NOT perform ISA-95 analysis or module decomposition yourself |
-| Phase 4b | `speccrew-pm-requirement-analysis` | DO NOT generate Master PRD or Dispatch Plan yourself |
-| Phase 5 | `speccrew-pm-sub-prd-generate` (via workers) | DO NOT generate Sub-PRD content yourself |
+| Phase 3 | `speccrew-pm-requirement-clarify` | DO NOT clarify requirements yourself — Dispatch Worker to execute |
+| Phase 4a | `speccrew-pm-requirement-model` | DO NOT perform ISA-95 analysis yourself — Dispatch Worker to execute |
+| Phase 4a.5 | User Confirmation Gate | MUST stop for user confirmation after module design |
+| Phase 4b | `speccrew-pm-requirement-analysis` | DO NOT generate Master PRD yourself — Dispatch Worker to execute |
+| Phase 5 | `speccrew-pm-sub-prd-generate` | DO NOT generate Sub-PRD yourself — Dispatch Workers to execute |
 | Phase 6 | PM Agent verification | DO NOT modify PRD content — only verify and present |
 
+**UNIVERSAL DISPATCH RULE:**
+- PM Agent NEVER invokes Skills directly via `action="run-skill"`
+- ALL Skill invocations use `action="dispatch-to-worker"` with `speccrew-task-worker`
+- Worker Agent receives the Skill name in context and executes it
+
 **UNIVERSAL ABORT RULE:**
 - IF ANY skill fails → STOP and report to user
 - DO NOT generate content as fallback

package/.speccrew/skills/speccrew-product-manager-orchestration/workflow.agentflow.xml

@@ -221,14 +221,16 @@
       <field name="text">IF clarification skill fails: ABORT - do NOT generate clarification yourself</field>
     </block>
 
-    <!-- Phase 3.1-3.2: Prepare Parameters & Invoke Skill -->
-    <block type="task" id="P3-B1" action="run-skill" status="pending" desc="Invoke clarification skill">
+    <!-- Phase 3.1-3.2: Prepare Parameters & Dispatch Worker -->
+    <block type="task" id="P3-B1" action="dispatch-to-worker" status="pending" desc="Dispatch requirement clarification worker">
+      <field name="agent">speccrew-task-worker</field>
       <field name="skill">speccrew-pm-requirement-clarify</field>
       <field name="context">
         requirement_file: ${user_requirement}
         iteration_path: ${iteration_path}
         complexity_hint: ${complexity}
         knowledge_status: ${knowledge_status.status}
+        language: ${language}
       </field>
       <field name="output" var="clarification_result"/>
     </block>
@@ -279,11 +281,13 @@
       
       <!-- Path A: Simple Requirements -->
       <branch test="${complexity} == 'simple'" name="Simple Path">
-        <block type="task" id="P4-B1" action="run-skill" status="pending" desc="Invoke simple PRD skill">
+        <block type="task" id="P4-B1" action="dispatch-to-worker" status="pending" desc="Dispatch simple PRD worker">
+          <field name="agent">speccrew-task-worker</field>
           <field name="skill">speccrew-pm-requirement-simple</field>
           <field name="context">
             iteration_path: ${iteration_path}
             clarification_file: ${iteration_path}/01.product-requirement/.clarification-summary.md
+            language: ${language}
           </field>
           <field name="output" var="prd_output"/>
         </block>
@@ -302,11 +306,13 @@
       <branch test="${complexity} == 'complex'" name="Complex Path">
         
         <!-- Phase 4a: Module Modeling -->
-        <block type="task" id="P4-B3" action="run-skill" status="pending" desc="Invoke requirement modeling skill">
+        <block type="task" id="P4-B3" action="dispatch-to-worker" status="pending" desc="Dispatch requirement modeling worker">
+          <field name="agent">speccrew-task-worker</field>
           <field name="skill">speccrew-pm-requirement-model</field>
           <field name="context">
             iteration_path: ${iteration_path}
             clarification_file: ${iteration_path}/01.product-requirement/.clarification-summary.md
+            language: ${language}
           </field>
           <field name="output" var="model_output"/>
         </block>
@@ -326,13 +332,30 @@
           <branch default="true" name="Model Passed"/>
         </block>
 
+        <!-- Phase 4a.5: User Confirmation Gate for Module Design -->
+        <block type="checkpoint" id="P4-CP1" name="requirement_modeling" desc="User confirmation gate for module design">
+          <field name="required" value="true"/>
+        </block>
+
+        <block type="event" id="P4-E1-CONFIRM" action="confirm" desc="Present module design for user confirmation">
+          <field name="prompt">📋 ISA-95 Module Design Complete. Please review .module-design.md before proceeding to PRD generation.</field>
+          <field name="template">module-design-summary</field>
+          <field name="data" value="${model_output}"/>
+        </block>
+
+        <block type="task" id="P4-B4-CHK" action="run-script" status="pending" desc="Update modeling confirmation checkpoint">
+          <field name="command">node ${update_progress_script} write-checkpoint --file ${iteration_path}/01.product-requirement/.checkpoints.json --stage 01_prd --checkpoint requirement_modeling_confirmed --passed true</field>
+        </block>
+
         <!-- Phase 4b: Master PRD Generation -->
-        <block type="task" id="P4-B5" action="run-skill" status="pending" desc="Invoke requirement analysis skill">
+        <block type="task" id="P4-B5" action="dispatch-to-worker" status="pending" desc="Dispatch requirement analysis worker">
+          <field name="agent">speccrew-task-worker</field>
           <field name="skill">speccrew-pm-requirement-analysis</field>
           <field name="context">
             iteration_path: ${iteration_path}
             clarification_file: ${iteration_path}/01.product-requirement/.clarification-summary.md
             module_design_file: ${iteration_path}/01.product-requirement/.module-design.md
+            language: ${language}
           </field>
           <field name="output" var="prd_output"/>
         </block>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.7.15",
+  "version": "0.7.16",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {