speccrew 0.3.11 → 0.3.12

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

@@ -50,9 +50,9 @@ Before starting work, check the workflow progress state:
 3. **If WORKFLOW-PROGRESS.json does not exist**:
    - **MUST use script to initialize:**
      ```bash
-     node speccrew-workspace/scripts/update-progress.js init-workflow \
+     node speccrew-workspace/scripts/update-progress.js update-workflow \
        --file speccrew-workspace/iterations/{iteration}/WORKFLOW-PROGRESS.json \
-       --iteration {iteration}
+       --stage 01_prd --status in_progress
      ```
    - **Fallback** (ONLY if script file does not exist):
      Create manually with the following structure:
@@ -273,9 +273,21 @@ When the invoked skill returns:
 >
 > 1. **DO NOT skip Phase 4 when Master-Sub structure is present** — If the Skill output indicates "Master-Sub PRD structure", Phase 4 MUST execute.
 > 2. **DO NOT generate Sub-PRDs yourself** — Each Sub-PRD MUST be generated by invoking `speccrew-task-worker` with `speccrew-pm-sub-prd-generate/SKILL.md`. You are the orchestrator, NOT the writer.
-> 3. **DO NOT create DISPATCH-PROGRESS.json manually** — Use the script: `node speccrew-workspace/scripts/update-progress.js init-dispatch`.
+> 3. **DO NOT create DISPATCH-PROGRESS.json manually** — Use the script: `node speccrew-workspace/scripts/update-progress.js init --stage sub_prd_dispatch --tasks '<JSON_ARRAY>'`.
 > 4. **DO NOT dispatch Sub-PRDs sequentially** — All workers MUST execute in parallel (batch of 6 if modules > 6).
 > 5. **DO NOT proceed to Phase 5 without verification** — After ALL workers complete, execute Phase 5 Verification Checklist before presenting to user.
+>
+> **ABORT CONDITIONS for Phase 4:**
+> - IF Dispatch Plan was not generated by Skill → STOP and return to Skill
+> - IF DISPATCH-PROGRESS.json initialization failed → STOP and report error
+> - IF PM Agent attempts to generate Sub-PRD content itself → STOP (you are ORCHESTRATOR, not WRITER)
+>
+> **FORBIDDEN ACTIONS in Phase 4:**
+> - DO NOT ask user to select which modules to generate first
+> - DO NOT ask user to provide or select templates (template path comes from Skill output)
+> - DO NOT offer strategy choices (generate all / generate 3 first / pick priority)
+> - DO NOT generate any Sub-PRD document content directly
+> - JUST DISPATCH ALL WORKERS AND WAIT FOR COMPLETION
 
 ## Phase 4: Sub-PRD Worker Dispatch (Master-Sub Structure Only)
 
@@ -300,9 +312,10 @@ From the Skill's Step 12c output, collect:
 
 **MANDATORY: Initialize dispatch tracking with script:**
 ```bash
-node speccrew-workspace/scripts/update-progress.js init-dispatch \
+node speccrew-workspace/scripts/update-progress.js init \
   --file speccrew-workspace/iterations/{iteration}/01.product-requirement/DISPATCH-PROGRESS.json \
-  --tasks "module-key-1,module-key-2,module-key-3,..."
+  --stage sub_prd_dispatch \
+  --tasks '[{"id":"module-key-1","name":"Module 1 Name"},{"id":"module-key-2","name":"Module 2 Name"}]'
 ```
 
 > ⚠️ DO NOT create DISPATCH-PROGRESS.json manually with PowerShell or any other method.
@@ -324,7 +337,24 @@ node speccrew-workspace/scripts/update-progress.js update-task \
 
 ### 4.3 Dispatch Workers
 
-Invoke `speccrew-task-worker` agents in parallel, one per module:
+**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
+
+**Implementation:**
+
+For EACH module in the dispatch plan, invoke a new `speccrew-task-worker` agent:
+- **skill_path**: Search with glob `**/speccrew-pm-sub-prd-generate/SKILL.md`
+- **context**: 
+  - `module_name`: from dispatch plan
+  - `module_key`: from dispatch plan
+  - `master_prd_path`: path to Master PRD
+  - `template_path`: PRD template path (from Step 7 glob search result)
+  - `output_dir`: `speccrew-workspace/iterations/{iteration}/01.product-requirement/`
 
 Each worker receives:
 - `skill_path`: `speccrew-pm-sub-prd-generate/SKILL.md`
@@ -342,6 +372,10 @@ Each worker receives:
   - `template_path`: Path to PRD-TEMPLATE.md
   - `output_path`: `{output_dir}/{feature_name}-sub-{module_key}.md`
 
+**Batch Strategy:**
+- If modules ≤ 6: dispatch ALL in parallel
+- If modules > 6: dispatch in batches of 6, wait for batch completion before next batch
+
 **Parallel execution pattern:**
 ```
 Worker 1: Module "customer"     → crm-system-sub-customer.md
@@ -351,7 +385,12 @@ Worker 3: Module "opportunity"  → crm-system-sub-opportunity.md
 Worker N: Module "{module-N}"   → crm-system-sub-{module-N}.md
 ```
 
-**All workers execute simultaneously.** Wait for all workers to complete before proceeding.
+**All workers execute simultaneously (or in batches).** Wait for all workers to complete before proceeding.
+
+**Before proceeding to Phase 5, verify:**
+- [ ] All workers were dispatched via speccrew-task-worker
+- [ ] No Sub-PRD was generated by PM Agent directly
+- [ ] All workers completed (check DISPATCH-PROGRESS.json)
 
 ### 4.4 Collect Results
 
@@ -435,9 +474,9 @@ After user confirms (HARD STOP passed), update `.checkpoints.json`:
 
 | Deliverable | Path | Notes |
 |-------------|------|-------|
-| PRD Document | `speccrew-workspace/iterations/{number}-{type}-{name}/01.prd/[feature-name]-prd.md` | Based on template from `speccrew-pm-requirement-analysis/templates/PRD-TEMPLATE.md` |
-| Business Modeling (complex) | `speccrew-workspace/iterations/{number}-{type}-{name}/01.prd/[feature-name]-bizs-modeling.md` | ISA-95 six-stage modeling, only for complex requirements |
-| Sub-PRD Documents (complex) | `speccrew-workspace/iterations/{number}-{type}-{name}/01.prd/[feature-name]-sub-[module].md` | One per module, generated by worker dispatch |
+| PRD Document | `speccrew-workspace/iterations/{number}-{type}-{name}/01.product-requirement/[feature-name]-prd.md` | Based on template from `speccrew-pm-requirement-analysis/templates/PRD-TEMPLATE.md` |
+| Business Modeling (complex) | `speccrew-workspace/iterations/{number}-{type}-{name}/01.product-requirement/[feature-name]-bizs-modeling.md` | ISA-95 six-stage modeling, only for complex requirements |
+| Sub-PRD Documents (complex) | `speccrew-workspace/iterations/{number}-{type}-{name}/01.product-requirement/[feature-name]-sub-[module].md` | One per module, generated by worker dispatch |
 
 # Constraints
 

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

@@ -663,17 +663,17 @@ Before writing any file, create a complete list of ALL files to generate:
 
 | # | File | Path |
 |---|------|------|
-| 1 | PRD | {iteration}/01.prd/{feature-name}-prd.md |
+| 1 | PRD | {iteration}/01.product-requirement/{feature-name}-prd.md |
 
 **For Master-Sub Structure (present this table to user):**
 
 | # | File Type | Module | Path |
 |---|-----------|--------|------|
-| 1 | Master PRD | (system overview) | {iteration}/01.prd/{feature-name}-prd.md |
-| 2 | Sub-PRD | {module-1-name} | {iteration}/01.prd/{feature-name}-sub-{module-1-key}.md |
-| 3 | Sub-PRD | {module-2-name} | {iteration}/01.prd/{feature-name}-sub-{module-2-key}.md |
+| 1 | Master PRD | (system overview) | {iteration}/01.product-requirement/{feature-name}-prd.md |
+| 2 | Sub-PRD | {module-1-name} | {iteration}/01.product-requirement/{feature-name}-sub-{module-1-key}.md |
+| 3 | Sub-PRD | {module-2-name} | {iteration}/01.product-requirement/{feature-name}-sub-{module-2-key}.md |
 | ... | ... | ... | ... |
-| N+1 | Sub-PRD | {module-N-name} | {iteration}/01.prd/{feature-name}-sub-{module-N-key}.md |
+| N+1 | Sub-PRD | {module-N-name} | {iteration}/01.product-requirement/{feature-name}-sub-{module-N-key}.md |
 
 Total files: 1 (Master) + N (Sub-PRDs) = N+1 files.
 
@@ -684,7 +684,7 @@ Total files: 1 (Master) + N (Sub-PRDs) = N+1 files.
 ### Step 12b: Generate Master PRD
 
 1. Read `templates/PRD-TEMPLATE.md` (already loaded in Step 7)
-2. Create document using `create_file` at: `{iteration}/01.prd/{feature-name}-prd.md`
+2. Create document using `create_file` at: `{iteration}/01.product-requirement/{feature-name}-prd.md`
 
 3. Fill content using `search_replace` per section:
 

package/package.json

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