speccrew 0.7.19 → 0.7.20

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

@@ -76,3 +76,13 @@ Applies ISA-95 Stages 1-3 as structured analysis framework:
 - Include technical implementation details
 - Create circular module dependencies
 - Manually write JSON files
+
+### Diagram Format Rule (MANDATORY)
+- All diagrams MUST use Mermaid syntax (graph TB, graph TD, graph LR, etc.)
+- ASCII art diagrams are FORBIDDEN
+- Reference `mermaid-rule.md` for compatibility
+
+### Template
+- Module design document MUST follow `templates/MODULE-DESIGN-TEMPLATE.md` structure
+- All 10 sections are required
+- Fill template with analyzed data from ISA-95 stages

package/.speccrew/skills/speccrew-pm-requirement-model/templates/MODULE-DESIGN-TEMPLATE.md

@@ -0,0 +1,175 @@
+# Module Design Document (.module-design.md)
+
+> **Iteration**: iteration_name
+> **Generated**: date
+> **System**: system_name
+> **Tech Stack**: tech_stack
+> **Document Type**: ISA-95 Business Modeling & Module Decomposition
+
+---
+
+## 1. Business Domain Analysis (ISA-95 Stage 1: Domain Description)
+
+### 1.1 Domain Boundary Definition
+
+<!-- Describe system positioning -->
+
+#### System Scope (IN-SCOPE)
+| Domain | Description |
+|--------|-------------|
+| domain | description |
+
+#### Out of Scope (OUT-OF-SCOPE)
+| Domain | Description | Planned Phase |
+|--------|-------------|---------------|
+| domain | description | phase |
+
+### 1.2 Actor Definition
+| Actor ID | Actor Name | Responsibilities | Data Scope | Typical Scenario |
+|----------|------------|------------------|------------|------------------|
+| role_id | role_name | responsibility | data_scope | scenario |
+
+### 1.3 Core Business Glossary
+| Term | Definition | Business Rule | Related Module |
+|------|------------|---------------|----------------|
+| term | definition | rule | module |
+
+### 1.4 Domain Model Diagram
+
+```mermaid
+graph TB
+    M01[M01 System Foundation] --> M02[M02 Module Name]
+    M01 --> M04[M04 Module Name]
+    M02 --> M03[M03 Module Name]
+    %% Draw based on actual module dependencies
+```
+
+---
+
+## 2. Function Decomposition (ISA-95 Stage 2: Functions in Domain)
+
+### 2.1 WBS Work Breakdown Structure
+
+#### module_id - module_name (count function points)
+| Function ID | Function Name | Description | Priority | Dependencies |
+|-------------|---------------|-------------|----------|--------------|
+| func_id | func_name | description | priority | dependency |
+
+### 2.2 Function Priority Distribution
+| Priority | Function Points | Percentage | Module Distribution |
+|----------|-----------------|------------|--------------------|
+| **P0 (Core)** | count | percent | modules |
+| **P1 (Important)** | count | percent | modules |
+| **P2 (Optional)** | count | percent | modules |
+
+---
+
+## 3. Module Priority & Phasing (ISA-95 Stage 3: Functions of Interest)
+
+### 3.1 MoSCoW Priority Analysis
+| Priority | Definition | Module | Description |
+|----------|------------|--------|-------------|
+
+### 3.2 Implementation Phases
+
+#### Phase 1 (MVP - Minimum Viable Product)
+**Core Chain**: core_chain
+| Module | Function Points | Deliverables |
+|--------|-----------------|--------------|
+
+**MVP Acceptance Criteria**:
+- ✅ criteria
+
+#### Phase 2 (Full Version - Stage 1)
+<!-- Same structure as above -->
+
+#### Phase 3 (Stage 2 Planning)
+<!-- Same structure as above -->
+
+---
+
+## 4. Module Dependencies
+
+### 4.1 Dependency Matrix
+| Module | Dependent Module | Dependency Type | Description |
+|--------|------------------|-----------------|-------------|
+
+### 4.2 Dependency Graph
+
+```mermaid
+graph TD
+    M01[M01 System Foundation] --> M02[M02 Module Name]
+    M01 --> M04[M04 Module Name]
+    M02 --> M03[M03 Module Name]
+    %% Draw directed acyclic graph based on dependency matrix
+```
+
+### 4.3 Circular Dependency Check
+<!-- Must confirm no circular dependencies -->
+
+---
+
+## 5. Module Implementation Sequence
+
+### 5.1 Implementation Phase Ordering
+
+```mermaid
+graph LR
+    P0[Phase 0: Infrastructure] --> P1[Phase 1: Core Entities]
+    P1 --> P2[Phase 2: Core Workflows]
+    P2 --> P3[Phase 3: Value-Added Features]
+    P3 --> P4[Phase 4: Data Analytics]
+    %% Adjust based on actual phases
+```
+
+### 5.2 Parallel Development Recommendations
+| Phase | Parallel Modules | Description |
+|-------|------------------|-------------|
+
+---
+
+## 6. Module Boundary Definition
+
+### 6.1 Module Responsibility Boundaries
+| Module | Core Responsibilities | Excluded Responsibilities | Boundary Notes |
+|--------|----------------------|--------------------------|----------------|
+
+### 6.2 Data Ownership
+| Data Entity | Owner Module | Read-Only Modules | Description |
+|-------------|--------------|-------------------|-------------|
+
+---
+
+## 7. Tech Stack Capability Reuse Analysis
+
+### 7.1 Reusable Capabilities
+| Required Function | Existing Capability | Reuse Level | Development Effort | Notes |
+|-------------------|---------------------|-------------|--------------------|-------|
+
+### 7.2 New Development Capabilities
+| Capability | Module | Development Priority | Estimated Effort | Notes |
+|------------|--------|---------------------|------------------|-------|
+
+---
+
+## 8. Risks & Mitigation Measures
+
+### 8.1 Technical Risks
+| Risk Item | Affected Modules | Impact Level | Probability | Mitigation Measures |
+|-----------|------------------|--------------|-------------|---------------------|
+
+### 8.2 Business Risks
+| Risk Item | Affected Modules | Impact Level | Probability | Mitigation Measures |
+|-----------|------------------|--------------|-------------|---------------------|
+
+---
+
+## 9. Module Summary
+| Module ID | Module Name | Function Points | Priority | Implementation Phase | Dependencies | Core Responsibilities |
+|-----------|-------------|-----------------|----------|---------------------|--------------|-----------------------|
+
+---
+
+## 10. Sign-off
+| Role | Name | Date | Signature |
+|------|------|------|-----------|

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

@@ -27,6 +27,12 @@
     <field name="text">Manually write JSON files</field>
   </block>
 
+  <block type="rule" id="R-MERMAID" level="mandatory" desc="All diagrams must use Mermaid syntax">
+    <field name="text">MANDATORY: All diagrams (domain model, dependency graph, implementation phases) MUST use Mermaid syntax.</field>
+    <field name="text">ASCII art diagrams are FORBIDDEN. Use graph TB, graph TD, graph LR as appropriate.</field>
+    <field name="text">Reference workspace-template/docs/rules/mermaid-rule.md for compatibility guidelines.</field>
+  </block>
+
   <!-- ============================================================
        Main Processing Sequence
        ============================================================ -->
@@ -161,8 +167,15 @@
       </branch>
     </block>
 
+    <!-- Read module design template -->
+    <block type="task" id="B10-TPL" action="read-file" desc="Read module design template">
+      <field name="path">${skill_path}/templates/MODULE-DESIGN-TEMPLATE.md</field>
+      <field name="output" var="template_content"/>
+    </block>
+
     <!-- Step 4: Generate .module-design.md -->
     <block type="task" id="B11" action="generate" desc="Generate module design document">
+      <field name="template" value="${template_content}"/>
       <field name="output_path" value="${iteration_path}/01.product-requirement/.module-design.md"/>
       <field name="sections">
         - ISA-95 Analysis Summary (if complex)

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

@@ -1,7 +1,7 @@
 ---
 name: speccrew-product-manager-orchestration
 version: 2.0.0
-description: Product Manager 核心编排技能（纯路由层 v2.0），负责工作流恢复路由和各 Phase Skill 的 dispatch-to-worker 调度。所有业务逻辑由独立的 Phase Skill 执行。
+description: Product Manager core orchestration skill (pure routing layer v2.0), responsible for workflow resume routing and dispatch-to-worker scheduling for each Phase Skill. All business logic is executed by independent Phase Skills.
 tools: Read, Write, Glob, Grep, Bash, Agent
 ---
 
@@ -34,32 +34,32 @@ tools: Read, Write, Glob, Grep, Bash, Agent
 
 # Product Manager Orchestration (v2.0)
 
-纯路由层编排技能，负责：
+Pure routing layer orchestration skill, responsible for:
 
-1. **Workflow Initialization** - Phase 0 初始化并返回恢复目标
-2. **Resume Routing** - 根据 `resume_target` 跳转到正确的 Phase
-3. **Phase Dispatch** - 每个 Phase 只有一个 `dispatch-to-worker` 调用
-4. **User Confirmation Gates** - Phase 3 和 Phase 4a 的强制性用户确认门禁
+1. **Workflow Initialization** - Phase 0 initialization and returning resume target
+2. **Resume Routing** - Jump to the correct Phase based on `resume_target`
+3. **Phase Dispatch** - Each Phase has only one `dispatch-to-worker` call
+4. **User Confirmation Gates** - Mandatory user confirmation gates for Phase 3 and Phase 4a
 
 ## Architecture: Pure Routing Layer
 
-本 Skill 是**纯路由层**，所有业务逻辑由独立的 Phase Skill 执行：
+This Skill is a **pure routing layer**, all business logic is executed by independent Phase Skills:
 
 | Phase | Block ID | Skill | Purpose |
 |-------|----------|-------|---------|
-| Phase 0 | P0 | `speccrew-pm-phase0-init` | 工作流初始化、迭代目录创建/定位、恢复状态检测 |
-| Phase 1 | P1 | `speccrew-pm-phase1-knowledge-check` | 知识库状态检测、模块匹配、知识初始化 |
-| Phase 2 | P2 | `speccrew-pm-phase2-complexity-assess` | 复杂度评估、简单/复杂路径决策 |
-| Phase 3 | P3 | `speccrew-pm-requirement-clarify` | 需求澄清、问答收集 |
-| Phase 4 Simple | P4-SIMPLE | `speccrew-pm-requirement-simple` | 简单需求：单 PRD 生成 |
-| Phase 4a | P4A | `speccrew-pm-requirement-model` | 复杂需求：ISA-95 建模 |
-| Phase 4b | P4B | `speccrew-pm-requirement-analysis` | 复杂需求：Master PRD 生成 |
-| Phase 5 | P5 | `speccrew-pm-phase5-subprd-dispatch` | Sub-PRD Worker 分发 |
-| Phase 6 | P6 | `speccrew-pm-phase6-verify-confirm` | 验证清单、用户审核、最终确认 |
+| Phase 0 | P0 | `speccrew-pm-phase0-init` | Workflow initialization, iteration directory creation/locating, resume state detection |
+| Phase 1 | P1 | `speccrew-pm-phase1-knowledge-check` | Knowledge base status detection, module matching, knowledge initialization |
+| Phase 2 | P2 | `speccrew-pm-phase2-complexity-assess` | Complexity assessment, simple/complex path decision |
+| Phase 3 | P3 | `speccrew-pm-requirement-clarify` | Requirement clarification, Q&A collection |
+| Phase 4 Simple | P4-SIMPLE | `speccrew-pm-requirement-simple` | Simple requirements: single PRD generation |
+| Phase 4a | P4A | `speccrew-pm-requirement-model` | Complex requirements: ISA-95 modeling |
+| Phase 4b | P4B | `speccrew-pm-requirement-analysis` | Complex requirements: Master PRD generation |
+| Phase 5 | P5 | `speccrew-pm-phase5-subprd-dispatch` | Sub-PRD Worker dispatch |
+| Phase 6 | P6 | `speccrew-pm-phase6-verify-confirm` | Verification checklist, user review, final confirmation |
 
 ## User Confirmation Gates (MANDATORY)
 
-Phase 3 和 Phase 4a 之后有**强制性用户确认门禁**：
+There are **mandatory user confirmation gates** after Phase 3 and Phase 4a:
 
 ### R-CONFIRM Rule Block
 
@@ -81,9 +81,9 @@ Phase 3 和 Phase 4a 之后有**强制性用户确认门禁**：
 ```
 
 **Key Points:**
-- `action="user-confirm"` — 必须等待用户明确确认
-- `skippable="false"` — 不可跳过
-- checkpoint 写入**必须**在用户确认后执行
+- `action="user-confirm"` — Must wait for explicit user confirmation
+- `skippable="false"` — Cannot be skipped
+- Checkpoint write **MUST** be executed after user confirmation
 
 ## Resume Router
 
@@ -114,18 +114,18 @@ Phase 0 输出 `resume_target` 控制恢复跳转：
 
 | Parameter | Type | Required | Description |
 |-----------|------|----------|-------------|
-| `user_requirement` | string | Yes | 用户需求描述或需求文档路径 |
-| `workspace_root` | string | Yes | speccrew-workspace 根目录路径 |
-| `source_path` | string | No | 项目源代码根目录（从 .speccrewrc 读取） |
-| `language` | string | No | 用户语言（默认自动检测） |
+| `user_requirement` | string | Yes | User requirement description or requirement document path |
+| `workspace_root` | string | Yes | speccrew-workspace root directory path |
+| `source_path` | string | No | Project source code root directory (read from .speccrewrc) |
+| `language` | string | No | User language (default auto-detect) |
 
 ## Output
 
-- `status` - 执行状态 (success / partial / failed)
-- `prd_files` - 生成的 PRD 文件列表
-- `feature_list` - 功能清单文件路径
-- `workflow_stage` - 当前工作流阶段状态
-- `next_agent` - 下一步建议的 Agent
+- `status` - Execution status (success / partial / failed)
+- `prd_files` - List of generated PRD files
+- `feature_list` - Feature list file path
+- `workflow_stage` - Current workflow stage status
+- `next_agent` - Recommended next Agent
 
 ---
 

package/package.json

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