speccrew 0.3.12 → 0.3.14

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

@@ -241,6 +241,13 @@ complexity_notes: <if complex, note affected modules>
 
 ## Phase 3: Invoke Skill
 
+> ⚠️ **PM AGENT ORCHESTRATION PRINCIPLE (Phase 3-5)**
+> You are the ORCHESTRATOR, NOT the WRITER:
+> - Phase 3: DO NOT generate Master PRD yourself → Skill generates it
+> - Phase 4: DO NOT generate Sub-PRD yourself → Workers generate them
+> - Phase 5: DO NOT modify PRD content yourself → Only verify and present
+> - **If Skill fails: STOP and report error to user. DO NOT generate content as fallback.**
+
 Based on the complexity assessment in Phase 1, invoke the appropriate skill:
 
 **For Simple Requirements:**
@@ -257,17 +264,69 @@ Pass the following context to the Skill:
 
 ### After Skill Completes
 
-When the invoked skill returns:
+**Step A: Check Skill Execution Status**
+
+- IF Skill FAILED or returned error → Go to **Phase 3a: Error Recovery**
+- IF Skill SUCCEEDED → Go to **Phase 3b: Validate & Route**
 
-1. **Check if Master-Sub structure was selected** (from skill Step 8 output)
-2. **If Master-Sub**: Skill will output a Sub-PRD Dispatch Plan → **MANDATORY: Execute Phase 4**
-3. **If Single PRD**: Skill completed the entire PRD → **Skip Phase 4, go to Phase 5**
+### Phase 3a: Error Recovery (Skill Failed)
+
+> ⚠️ **ABORT CONDITIONS — Execution MUST STOP:**
+> - Skill reported execution failure or was interrupted
+> - No PRD document was generated
+> - PRD file exists but is incomplete or malformed
+>
+> **FORBIDDEN ACTIONS:**
+> - DO NOT generate Master PRD as fallback
+> - DO NOT generate Sub-PRDs as fallback
+> - DO NOT create partial PRD documents
+> - DO NOT proceed to Phase 4 or Phase 5
+
+Actions:
+1. Report error to user: "Skill execution failed: [specific reason]"
+2. Ask user: "Retry with additional clarification?" or "Abort current workflow?"
+3. IF retry → Return to Phase 2, gather more context, then retry Phase 3
+4. IF abort → END workflow
+
+### Phase 3b: Validate & Route (Skill Succeeded)
+
+1. **Identify PRD structure type** (from Skill output):
+   - Master-Sub structure → Validate Dispatch Plan (Step 2)
+   - Single PRD → Skip to Phase 5
+
+2. **Validate Dispatch Plan (Master-Sub only)**:
+   - [ ] Master PRD file exists and is readable
+   - [ ] Dispatch Plan contains module list (count ≥ 2)
+   - [ ] Each module has: module_name, module_key, module_scope, module_entities
+   - [ ] template_path and output_dir are defined
+   
+   IF ANY validation fails:
+   → STOP. Report: "Dispatch Plan incomplete: [missing items]"
+   → Ask user to retry Skill execution
+   → DO NOT proceed to Phase 4
+
+3. **Route**:
+   - Master-Sub + Dispatch Plan valid → **MANDATORY: Execute Phase 4**
+   - Single PRD → **Skip Phase 4, go to Phase 5**
 
 > ⚠️ **DO NOT present results to user before Phase 4 completes (for complex requirements).**
 > The Master PRD alone is incomplete without Sub-PRDs.
 
 ---
 
+> ⚠️ **MANDATORY RULES FOR PHASE 3:**
+> 1. DO NOT generate Master PRD yourself — it MUST be generated by Skill
+> 2. DO NOT generate any PRD content as fallback if Skill fails
+> 3. DO NOT skip Skill failure validation
+> 4. MUST validate Dispatch Plan completeness before entering Phase 4
+>
+> **ABORT CONDITIONS:**
+> - IF Skill execution failed → STOP and report to user
+> - IF PRD output is missing or incomplete → STOP and report to user
+> - IF PM Agent attempts to generate PRD content itself → STOP (ORCHESTRATOR ONLY)
+
+---
+
 > ⚠️ **MANDATORY RULES FOR PHASE 4 (Sub-PRD Worker Dispatch):**
 > These rules apply to ALL complex requirements (3+ modules). Violation = workflow failure.
 >
@@ -318,6 +377,12 @@ node speccrew-workspace/scripts/update-progress.js init \
   --tasks '[{"id":"module-key-1","name":"Module 1 Name"},{"id":"module-key-2","name":"Module 2 Name"}]'
 ```
 
+> **PowerShell Compatibility Note:**
+> PowerShell cannot properly parse JSON in command-line arguments. Use file-based approach:
+> 1. Write tasks JSON to a temporary file (e.g., `tasks-temp.json`)
+> 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.
 

package/package.json

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

package/workspace-template/docs/rules/mermaid-rule.md

@@ -67,6 +67,19 @@ graph TB
 | `/` | File paths (`/pages/index`) | Remove leading `/` or use parentheses: `pages/index` |
 | `(` `)` | Function calls (`handleQuery()`) | Remove parentheses: `handleQuery` |
 
+**When Special Characters Must Be Preserved:**
+
+If node text must contain parentheses `()`, curly braces `{}`, square brackets `[]`, or colons `:`, wrap the entire text in double quotes to prevent Mermaid from misinterpreting them as shape definitions or syntax elements.
+
+| Wrong (Parse Error) | Correct (Quoted) |
+|---------------------|------------------|
+| `P1[选择对比组(如:面部左脸)]` | `P1["选择对比组(如:面部左脸)"]` |
+| `P2[上传图片(1-N张)]` | `P2["上传图片(1-N张)"]` |
+| `A[Task{ urgent }]` | `A["Task{ urgent }"]` |
+| `B[Array[0]]` | `B["Array[0]"]` |
+
+**Important:** The rule "Quoted node text [\"text\"]" in the Prohibited list refers to unnecessary quoting of plain text. When special characters are present, quoting becomes **required** for correct parsing.
+
 ### 5. Multi-line Text Handling
 
 ```