speccrew 0.4.0 → 0.4.2

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

@@ -503,6 +503,27 @@ Step 3b: Invoke speccrew-pm-requirement-analysis
 
 After the Skill generates the Master PRD and outputs the dispatch plan, the PM Agent takes over to generate Sub-PRDs in parallel using worker agents.
 
+> **Phase 4 Execution Flow:**
+> ```
+> Generate Skill outputs Dispatch Plan
+>     ↓
+> PM reads Dispatch Plan (module list + contexts)
+>     ↓
+> PM initializes DISPATCH-PROGRESS.json (via script)
+>     ↓
+> PM invokes speccrew-task-worker × N (one per module)
+>   └─ Each worker internally calls speccrew-pm-sub-prd-generate
+>     ↓
+> Workers complete → PM updates progress (via script)
+>     ↓
+> ALL workers done → Phase 5
+> ```
+> 
+> **NOT this flow:**
+> ```
+> PM reads Dispatch Plan → PM generates Sub-PRDs directly ← VIOLATION
+> ```
+
 ### 4.1 Read Dispatch Plan
 
 From the Skill's Step 12c output, collect:
@@ -531,8 +552,11 @@ node speccrew-workspace/scripts/update-progress.js init \
 > 2. Read file content in the command: `node scripts/update-progress.js init --stage sub_prd_dispatch --tasks (Get-Content tasks-temp.json -Raw)`
 > 3. Or use: `Get-Content tasks-temp.json | node scripts/update-progress.js init --stage sub_prd_dispatch --tasks -`
 
-> ⚠️ DO NOT create DISPATCH-PROGRESS.json manually with PowerShell or any other method.
-> If the script fails, STOP and report the error to the user.
+> 🛑 **HARD STOP: DISPATCH-PROGRESS.json MUST be created by script ONLY**
+> - MUST use: `node speccrew-workspace/scripts/update-progress.js init --stage sub_prd_dispatch --tasks '<JSON_ARRAY>'`
+> - DO NOT create DISPATCH-PROGRESS.json manually (PowerShell, create_file, or any other method)
+> - IF script fails → STOP workflow immediately, report error to user, ask "Retry or Abort?"
+> - DO NOT proceed to Worker dispatch without successful script execution
 
 After each worker completes:
 ```bash
@@ -550,13 +574,22 @@ node speccrew-workspace/scripts/update-progress.js update-task \
 
 ### 4.3 Dispatch Workers
 
-**PM Agent Role: ORCHESTRATOR ONLY**
-
-You are the dispatcher, NOT the writer. Your job is to:
-1. Invoke `speccrew-task-worker` for EACH module
-2. Pass the correct skill_path and context
-3. Wait for all workers to complete
-4. Collect results
+**PM Agent Role: ORCHESTRATOR ONLY — Phase 4 EXPLICIT RULES**
+
+**MANDATORY — PM MUST:**
+1. Read the Dispatch Plan from generate skill output
+2. Initialize DISPATCH-PROGRESS.json via update-progress.js script
+3. For EACH module in dispatch plan: invoke `speccrew-task-worker` with `skill_path: speccrew-pm-sub-prd-generate/SKILL.md`
+4. Pass ALL required context parameters to each worker
+5. Wait for ALL workers to complete
+6. Update DISPATCH-PROGRESS.json via script after each worker completes
+
+🛑 **FORBIDDEN — PM MUST NOT:**
+- Generate Sub-PRD files directly (via create_file, write, or any file creation)
+- Invoke speccrew-pm-sub-prd-generate skill directly (ONLY speccrew-task-worker invokes it)
+- Create or edit any Sub-PRD content as fallback if worker fails
+- Skip worker dispatch and generate Sub-PRDs inline
+- IF PM attempts ANY of above → WORKFLOW VIOLATION → STOP immediately
 
 **Implementation:**
 

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

@@ -63,7 +63,15 @@ Applies ISA-95 Stages 2-3 outputs for PRD generation:
 
 **Actions:**
 1. Read `.clarification-summary.md` — extract: key decisions, clarified scope, business rules
-2. Read `.module-design.md` — extract: module list, dependency matrix, implementation phases
+2. Read `.module-design.md` — extract:
+   - **Module count**: from `## Module List (Total: N modules)` heading (parse the number N)
+   - **Module list**: rows from Module List table
+   - **Dependency matrix**: rows from Dependency Matrix table
+   - **Implementation phases**: items from Implementation Phases section
+
+   **Validation:**
+   - IF module_count >= 2 → MANDATORY: Use Master-Sub Structure
+   - IF module_count < 2 → Use Single PRD Structure
 
 ## Step 2: Read PRD Template
 
@@ -304,6 +312,18 @@ ELSE:
 → After ALL workers complete → PM Agent executes Phase 5 Verification
 ```
 
+🛑 **CRITICAL HANDOFF — PM Agent MUST NOT:**
+- Generate Sub-PRD files directly
+- Invoke speccrew-pm-sub-prd-generate as its own operation
+- Create Sub-PRD content using create_file or any file write
+- Skip speccrew-task-worker and directly produce Sub-PRD documents
+
+**PM Agent MUST:**
+1. Use Dispatch Plan above to invoke speccrew-task-worker for EACH module
+2. Each worker uses skill_path: speccrew-pm-sub-prd-generate/SKILL.md
+3. Initialize DISPATCH-PROGRESS.json via update-progress.js script (NOT manually)
+4. After ALL workers complete → Execute Phase 5 Verification
+
 **IF Single PRD Structure:** Skip dispatch plan (no Sub-PRDs needed).
 
 ---

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

@@ -80,7 +80,10 @@ Applies ISA-95 Stages 1-3 as structured analysis framework:
 ### Domain Description
 - **System Boundary**: [what's included/excluded]
 - **Actors**: [user roles, external systems]
-- **Domain Glossary**: [term: definition]
+- **Domain Glossary**:
+  | Term | Definition |
+  |------|-----------|
+  | [term] | [definition] |
 ```
 
 **Checkpoint A:** Present to user for confirmation.
@@ -164,12 +167,14 @@ Ready to proceed with module decomposition? Reply "确认".
 
 **Output format:**
 ```markdown
-## Module List
+## Module List (Total: {N} modules)
 | Module | Key | Scope | Key Entities | Owner Domain |
 |--------|-----|-------|-------------|--------------|
 | [Name] | [key] | [scope] | [entities] | [domain] |
 ```
 
+> ⚠️ **MANDATORY:** Replace `{N}` with the actual module count. This count is used by downstream skills for structure validation.
+
 ### 3.2 Cross-Module Dependency Matrix
 
 **Actions:**
@@ -226,7 +231,10 @@ Please review. Reply "确认" to finalize or request changes.
 ### Domain Description
 - **System Boundary**: [description]
 - **Actors**: [list]
-- **Domain Glossary**: [terms]
+- **Domain Glossary**:
+  | Term | Definition |
+  |------|-----------|
+  | [term] | [definition] |
 
 ### Domain Functions (WBS)
 [WBS structure]
@@ -238,7 +246,7 @@ Please review. Reply "确认" to finalize or request changes.
 | Should | [fn] | [rationale] |
 | Could | [fn] | [rationale] |
 
-## Module List
+## Module List (Total: {N} modules)
 | Module | Key | Scope | Key Entities | Owner Domain | Phase |
 |--------|-----|-------|-------------|--------------|-------|
 | [name] | [key] | [scope] | [entities] | [domain] | [1/2/3] |

package/package.json

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