speccrew 0.6.23 → 0.6.25

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

@@ -578,11 +578,29 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
 >
 > This step aggregates all module-overview.md files into a single system-overview.md, which PM Agent uses as the primary knowledge context when processing new requirements.
 >
-> ⚠️ This step MUST complete before Phase 1 exits. system-overview.md is required for subsequent requirement analysis.
->
-> Only after ALL Steps complete, proceed to Phase 2 (Requirement Clarification).
->
-> 🛑 **Path B Completion Check**:
+⚠️ This step MUST complete before Phase 1 exits. system-overview.md is required for subsequent requirement analysis.
+
+**Path B Step 7: Cleanup Intermediate Files**
+
+After system-overview.md is successfully generated, delete intermediate files that are no longer needed:
+
+```bash
+# Delete matcher result (used for task generation, no longer needed)
+rm "{workspace_path}/knowledges/bizs/.matcher-result.json"
+
+# Delete dispatch progress (used for task tracking, no longer needed)
+rm "{workspace_path}/knowledges/bizs/DISPATCH-PROGRESS.json"
+```
+
+⚠️ Only execute cleanup AFTER confirming:
+- [ ] Step 6 completed: system-overview.md exists and is non-empty
+- [ ] All tasks in DISPATCH-PROGRESS.json have status "completed"
+
+These files were used for breakpoint recovery during initialization. Once all tasks complete and system-overview.md is generated, they become obsolete and can be safely removed.
+
+Only after ALL Steps complete, proceed to Phase 2 (Requirement Clarification).
+
+🛑 **Path B Completion Check**:
 > Before proceeding to Phase 2, verify:
 > - [ ] Step 1.5 completed: DISPATCH-PROGRESS.json created with all tasks
 > - [ ] Step 2 completed: task plan JSON generated for each matched module
@@ -590,7 +608,8 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
 > - [ ] Step 4 completed: module-summarize Workers completed for ALL matched modules
 > - [ ] Step 5 completed: features-*.json updated with analyzed=true
 > - [ ] Step 6 completed: system-overview.md generated
-> 
+> - [ ] Step 7 completed: intermediate files (.matcher-result.json, DISPATCH-PROGRESS.json) cleaned up
+>
 > If ANY step is incomplete, DO NOT proceed. Execute the missing steps first.
 
 4. **IF feature inventory fails**:
@@ -1734,6 +1753,29 @@ and invoke the Feature Designer Agent (speccrew-feature-designer).
 DO NOT proceed to Feature Design in this conversation.
 ```
 
+**5.3.5 Cleanup PRD Intermediate Files**
+
+After PRD verification passes and user has confirmed, delete intermediate process files that are no longer needed:
+
+**Files to delete:**
+- `{iteration_path}/01.product-requirement/.checkpoints.json` (execution checkpoint tracking)
+- `{iteration_path}/01.product-requirement/.prd-generation-report.md` (intermediate generation report)
+- `{iteration_path}/01.product-requirement/.prd-completion-report.md` (completion report)
+- `{iteration_path}/01.product-requirement/.sub-prd-dispatch-plan.json` (Sub-PRD dispatch plan)
+
+**Files to KEEP (referenced by downstream phases):**
+- Master PRD and all Sub-PRD documents (`*-prd.md`, `*-sub-*.md`)
+- `.clarification-summary.md`
+- `.module-design.md`
+- `.clarification-questions-round-*.md` (optional, for reference)
+
+⚠️ **Only execute cleanup AFTER:**
+- All Sub-PRDs are verified and confirmed
+- User has explicitly confirmed in Phase 6.2
+- WORKFLOW-PROGRESS.json has been updated to "confirmed" status
+
+> 🛑 **FORBIDDEN**: DO NOT delete PRD documents or clarification-related files.
+
 **END** — Do not invoke or suggest transitioning to the next stage agent.
 
 # Deliverables

package/package.json

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