speccrew 0.7.56 → 0.7.57

package/.speccrew/agents/speccrew-system-designer.md

@@ -31,8 +31,8 @@ Phase 2: Resource Verification
 Phase 3: Framework Evaluation (HARD STOP)
   └── Dispatch speccrew-sd-framework-evaluate skill → User confirms
         ↓
-Phase 4: Generate DESIGN-OVERVIEW.md (WORKER-DISPATCH)
-  └── Dispatch speccrew-sd-design-overview-generate skill → Wait for worker → Validate output
+Phase 4: Generate DESIGN-OVERVIEW.md (WORKER-DISPATCH + HARD STOP)
+  └── Dispatch speccrew-sd-design-overview-generate skill → Wait for worker → Validate → User confirms
         ↓
 Phase 5: Dispatch Per-Platform Skills
   ├── Single Feature + Single Platform → Direct skill invocation
@@ -126,7 +126,7 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 | Phase 2 | KNOWLEDGE-FIRST | MUST load ALL techs knowledge before Phase 3. DO NOT assume technology stack |
 | Phase 3 | WORKER-DISPATCH | Framework evaluation MUST be dispatched to speccrew-task-worker via **Agent tool**. Agent MUST NOT invoke speccrew-sd-framework-evaluate via Skill tool. |
 | Phase 3 | HARD STOP | User must confirm framework decisions before proceeding to Phase 4 |
-| Phase 4 | WORKER-DISPATCH | DESIGN-OVERVIEW.md generation MUST be dispatched to speccrew-task-worker via **Agent tool**. Agent MUST NOT generate this file inline. |
+| Phase 4 | WORKER-DISPATCH + HARD STOP | DESIGN-OVERVIEW.md generation MUST be dispatched to speccrew-task-worker via **Agent tool**. After worker completes, present summary to user and WAIT for confirmation before Phase 5. |
 | Phase 5 | SKILL-ONLY | Platform design workers MUST use platform-specific design skills. Agent MUST NOT write design documents itself |
 | Phase 6 | HARD STOP | User must confirm all designs before finalizing |
 | ALL | ABORT ON FAILURE | If any skill invocation fails → STOP and report. Do NOT generate content manually as fallback |
@@ -544,6 +544,20 @@ Proceed to Phase 4? (Confirm/Cancel)
 > - ❌ DO NOT generate DESIGN-OVERVIEW.md yourself
 > - ❌ DO NOT use Skill tool to invoke speccrew-sd-design-overview-generate
 
+> ⚠️ **HARD STOP — Phase 4.5: DESIGN-OVERVIEW.md Confirmation**
+> After worker completes and DESIGN-OVERVIEW.md passes validation:
+> 1. Present summary to user: feature count, platform count, matrix entries, key design decisions
+> 2. **STOP** — Wait for user explicit confirmation
+> 3. User responses:
+>    - "确认" or "OK" → Update checkpoint, proceed to Phase 5
+>    - "修改" + specific changes → Re-dispatch worker with adjustments
+>    - "取消" → Abort workflow
+> **FORBIDDEN during HARD STOP**:
+> - ❌ DO NOT update checkpoint until user confirms
+> - ❌ DO NOT suggest next steps
+> - ❌ DO NOT proceed to Phase 5
+> - ❌ DO NOT auto-approve even if all validations pass
+
 Create the top-level overview at:
 `{iterations_dir}/{current}/03.system-design/DESIGN-OVERVIEW.md`
 

package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.md

@@ -114,13 +114,16 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
 4. **Wait** for the worker agent to complete and return results
 5. After worker completes, verify DESIGN-OVERVIEW.md exists at output_path
 6. Then proceed to Phase 4 checkpoint validation (P4-CP1)
+7. Present DESIGN-OVERVIEW.md summary to user (feature count, platform count, matrix entries)
+8. **⚠️ HARD STOP** — Wait for user explicit confirmation before proceeding to Phase 5
 
 **CRITICAL**: The `Agent tool` creates a NEW agent session — this is completely different from the `Skill tool` which executes inline.
 
 ### HARD STOP Checkpoints
 
 This workflow has **mandatory HARD STOP** checkpoints at:
-- **Phase 3.5**: Framework evaluation confirmation (user MUST approve)
+- **Phase 3.5**: Framework evaluation confirmation (user MUST approve framework decisions)
+- **Phase 4.5**: Design overview confirmation (user MUST approve DESIGN-OVERVIEW.md before Phase 5 dispatch)
 - **Phase 6.1**: Joint design confirmation (user MUST approve all designs)
 
 DO NOT proceed past these checkpoints without explicit user confirmation.

package/.speccrew/skills/speccrew-system-designer-orchestration/workflow.agentflow.xml

@@ -285,6 +285,15 @@
     <block type="checkpoint" id="P4-CP1" name="design_overview" desc="DESIGN-OVERVIEW validation">
       <field name="conditions">file_exists, has_design_scope_section, has_tech_decisions_section, has_platform_design_index, index_covers_all_feature_platform_combinations</field>
     </block>
+
+    <!-- Phase 4.5: HARD STOP — User must confirm DESIGN-OVERVIEW.md -->
+    <block type="rule" id="P4-HS1" level="mandatory" desc="HARD STOP — DESIGN-OVERVIEW.md confirmation required">
+      <field name="text">⚠️ HARD STOP — WAIT FOR USER CONFIRMATION</field>
+      <field name="text">Present DESIGN-OVERVIEW.md summary to user (feature count, platform count, matrix entries, key sections)</field>
+      <field name="text">User responses: "确认"/"OK" → proceed to Phase 5 | "修改" + changes → re-dispatch worker | "取消" → abort</field>
+      <field name="text">FORBIDDEN: Do NOT update checkpoint, suggest next steps, or proceed to Phase 5 until user explicitly confirms</field>
+      <field name="text">FORBIDDEN: Do NOT auto-approve even if validation passes — user review is mandatory</field>
+    </block>
   </sequence>
 
   <!-- ========== Phase 5: Dispatch Per-Platform Skills ========== -->

package/package.json

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