speccrew 0.6.22 → 0.6.23

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

@@ -562,6 +562,24 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
 > **Path B Step 5: Update Features Status**
 > After all analyze Workers complete, update each analyzed feature's `analyzed` field to `true` in the corresponding features-*.json file.
 >
+> **Path B Step 6: Generate System Overview**
+> Dispatch a Worker to generate system-overview.md from all module-overview files:
+>
+> ```
+> Use the Agent tool to invoke speccrew-task-worker:
+> - agent: speccrew-task-worker
+> - task: Execute speccrew-knowledge-system-summarize skill
+> - context:
+>     skill: speccrew-knowledge-system-summarize
+>     modules_path: {workspace_path}/knowledges/bizs
+>     output_path: {workspace_path}/knowledges/bizs
+>     language: {language}
+> ```
+>
+> 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**:
@@ -571,6 +589,7 @@ No knowledge base exists. A lightweight feature inventory scan is triggered to d
 > - [ ] Step 3 completed: analyze Workers dispatched and completed for ALL pending features
 > - [ ] 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
 > 
 > If ANY step is incomplete, DO NOT proceed. Execute the missing steps first.
 

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

@@ -1,7 +1,7 @@
 ---
 name: speccrew-system-developer
 description: SpecCrew System Developer. Reads system design blueprints and coordinates cross-platform development task dispatch. Loads techs knowledge, verifies environment readiness, dispatches per-platform dev skills, performs integration checks, and delivers development completion reports. Supports web, mobile, desktop, and backend platforms.
-tools: Read, Write, Glob, Grep, Bash, Agent
+tools: Read, Write, Glob, Grep, Bash
 ---
 
 # Quick Reference — Execution Flow

package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md

@@ -364,6 +364,45 @@ Log: "✅ Checkpoint B (feature_design_review) passed and recorded"
 
 ## Step 5: Determine Output Path & Copy Template
 
+> **⚠️ CRITICAL: Two-Phase Strategy (Skeleton-First, Content-After)**
+>
+> Steps 5 and 6 MUST be executed in two phases to ensure consistent document structure.
+
+### Phase A: Skeleton Construction (BEFORE any content filling)
+
+1. Read FEATURE-SPEC-TEMPLATE.md to identify the complete section structure
+2. Count the number of functions from `.feature-analysis.md` input
+3. For Section 2 Function Details, replicate the template's Function block structure for EACH function:
+   - Copy the EXACT template structure (all 4 sub-sections) from FEATURE-SPEC-TEMPLATE.md
+   - Create `### 2.1 Function: {function_name}` through `### 2.N Function: {function_name}`
+   - Each function block MUST contain these 4 sub-section headers (copied from template):
+     ```
+     #### 2.N.1 Frontend Prototype
+     [TO BE FILLED]
+     
+     #### 2.N.2 Interaction Flow
+     [TO BE FILLED]
+     
+     #### 2.N.3 Backend Interface
+     [TO BE FILLED]
+     
+     #### 2.N.4 Data Definition
+     [TO BE FILLED]
+     ```
+4. Verify skeleton: confirm ALL functions have ALL 4 sub-section headers before proceeding
+
+> ⚠️ DO NOT start filling content until the complete skeleton is verified.
+
+### Phase B: Content Filling (AFTER skeleton is complete)
+
+Fill each `[TO BE FILLED]` placeholder with actual content:
+- **Frontend Prototype** → ASCII wireframes (Pattern A/B/C/M-A/M-B/M-C) + Interface Element Description table
+- **Interaction Flow** → Mermaid `sequenceDiagram` + Interaction Rules table
+- **Backend Interface** → Interface List table + Mermaid `flowchart TD` for Processing Logic + Data Access table
+- **Data Definition** → Fields table + Data Source table
+
+---
+
 ### 5.1 Determine Output Path
 
 **Single Feature Mode** (when `feature_id` provided):
@@ -399,6 +438,13 @@ Log: "✅ Checkpoint B (feature_design_review) passed and recorded"
 
 ## Step 6: Fill Sections Using search_replace
 
+> **⚠️ CRITICAL: Section 2 Function Details Skeleton Verification**
+>
+> Before proceeding with content filling, verify the two-phase strategy was correctly applied:
+> 1. Confirm ALL functions in Section 2 have complete 4 sub-section skeletons (Frontend Prototype, Interaction Flow, Backend Interface, Data Definition)
+> 2. Confirm no `[TO BE FILLED]` placeholders remain unfilled after content filling
+> 3. Confirm each function follows the exact template structure from FEATURE-SPEC-TEMPLATE.md
+
 ### Section Mapping Table
 
 | Template Section | Data Source |
@@ -504,6 +550,7 @@ Log: "✅ Feature Spec generation completed. Checkpoint feature_spec_review pass
 - [ ] Output path determined
 - [ ] Template copied using `create_file`
 - [ ] All sections filled using `search_replace`
+- [ ] **[CRITICAL]** Section 2 Function Details skeleton verified (all functions have 4 sub-sections)
 - [ ] **[CRITICAL]** Interaction Flow uses Mermaid sequenceDiagram (NOT ASCII)
 - [ ] **[CRITICAL]** Processing Logic uses Mermaid flowchart TD (NOT ASCII)
 - [ ] All Mermaid diagrams follow mermaid-rule.md compliance rules

package/.speccrew/skills/speccrew-knowledge-module-summarize/SKILL.md

@@ -126,6 +126,52 @@ Collect all business rules from feature details:
 
 ### Step 5: Generate Complete MODULE-OVERVIEW.md
 
+> **⚠️ CRITICAL: Two-Phase Strategy (Skeleton-First, Content-After)**
+>
+> This step MUST be executed in two phases to ensure consistent document structure.
+
+### Phase A: Skeleton Construction (BEFORE any content filling)
+
+1. Read MODULE-OVERVIEW-TEMPLATE.md to identify the complete section structure
+2. Count data items from extracted information:
+   - Section 3: Count unique **Entities** (deduplicated by entity name)
+   - Section 4: Count unique **Dependencies** (internal + external)
+   - Section 5: Count unique **Core Business Flows**
+   - Section 6: Count unique **Business Rules**
+3. For each section with repeating data items, create complete skeleton structure:
+   - **Section 3 (Entities)**: For each entity, create table row with ALL column placeholders:
+     ```
+     | [Entity Name] | [TO BE FILLED] | [TO BE FILLED] | [TO BE FILLED] |
+     ```
+   - **Section 4 (Dependencies)**: For each dependency, create table row with ALL column placeholders:
+     ```
+     | [Direction] | [Target] | [Content] | [Method] |
+     ```
+   - **Section 5 (Core Business Flows)**: For each flow, create flow item with placeholders:
+     ```
+     **[Flow Name]**: [TO BE FILLED]
+     ```
+   - **Section 6 (Business Rules)**: For each rule, create table row with ALL column placeholders:
+     ```
+     | [Rule ID] | [Rule Name] | [Description] | [Related Features] |
+     ```
+4. Verify skeleton: confirm ALL data items have ALL required column/field placeholders before proceeding
+
+> ⚠️ DO NOT start filling content until the complete skeleton is verified.
+
+### Phase B: Content Filling (AFTER skeleton is complete)
+
+Fill each `[TO BE FILLED]` placeholder with actual content:
+- Entity Description → Business description of the entity
+- Entity Key Attributes → Field names with types (deduplicated from all features)
+- Entity Business Rules → Constraints and validation rules aggregated from features
+- Dependency Content → What is provided/consumed
+- Dependency Method → How the dependency is realized (API call, import, injection)
+- Core Business Flow → Step sequence with actors and outcomes
+- Business Rule Description → Rule logic and enforcement point
+
+---
+
 **⚠️ CRITICAL CONSTRAINTS (apply to this step):**
 > 1. **FORBIDDEN: `create_file` for overview document** — If skeleton exists, use `search_replace`; if not, copy template first then fill with `search_replace`
 > 2. **FORBIDDEN: Full-file rewrite** — Always use targeted `search_replace` on specific sections

package/.speccrew/skills/speccrew-knowledge-system-summarize/SKILL.md

@@ -208,6 +208,48 @@ Create flow-module mapping matrix:
 
 ### Step 7: Generate system-overview.md
 
+> **⚠️ CRITICAL: Two-Phase Strategy (Skeleton-First, Content-After)**
+>
+> This step MUST be executed in two phases to ensure consistent document structure.
+
+### Phase A: Skeleton Construction (BEFORE any content filling)
+
+1. Read SYSTEM-OVERVIEW-TEMPLATE.md to identify the complete section structure
+2. Count aggregated data items from discovered modules:
+   - Section 2: Count unique **Modules** (including platform_type annotation for duplicates)
+   - Section 3: Count unique **End-to-End Business Flows**
+   - Section 4: Count unique **External Integrations**
+3. For each section with repeating data items, create complete skeleton structure:
+   - **Section 2 (Module Topology)**: For each module, create index table row with ALL column placeholders:
+     ```
+     | [Module Name] | [Domain] | [Purpose] | [Entities] | [APIs] | [Detail Doc] |
+     ```
+   - **Section 3 (Business Flows)**: For each flow, create mapping matrix row:
+     ```
+     | [Flow Name] | [Module 1] | [Module 2] | ... | [Module N] |
+     ```
+   - **Section 4 (External Integrations)**: For each integration, create table row:
+     ```
+     | [System Name] | [Integration Type] | [Data Exchanged] | [Protocol] |
+     ```
+4. Verify skeleton: confirm ALL data items have ALL required column placeholders before proceeding
+
+> ⚠️ DO NOT start filling content until the complete skeleton is verified.
+
+### Phase B: Content Filling (AFTER skeleton is complete)
+
+Fill each `[TO BE FILLED]` placeholder with actual content:
+- Module Domain → Business domain classification from module overview
+- Module Purpose → Business purpose extracted from module overview
+- Module Entities → Entity count and key entity names
+- Module APIs → API/Interface count from module overview
+- Module Detail Doc → Relative link to module-overview.md
+- Flow Module Mapping → ✓ for involved modules, - for not involved
+- Integration Data Exchanged → Data structures and formats exchanged
+- Integration Protocol → HTTP/REST, gRPC, WebSocket, etc.
+
+---
+
 **⚠️ CRITICAL CONSTRAINTS (apply to Step 7a and 7b):**
 > 1. **FORBIDDEN: `create_file` for documents** — Document MUST be created by copying template (Step 7a) then filling with `search_replace` (Step 7b)
 > 2. **FORBIDDEN: Full-file rewrite** — Always use targeted `search_replace` on specific sections

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

@@ -179,7 +179,56 @@ ELSE:
 | One list page with filters | Entire reporting subsystem |
 | One form with validation | Multi-step wizard with 10+ steps |
 
-### 4.2 Marking Existing vs New Features
+### 4.2 Section 3.5 Feature Details — Two-Phase Strategy
+
+> **⚠️ CRITICAL: Two-Phase Strategy (Skeleton-First, Content-After)**
+>
+> This step MUST be executed in two phases to ensure consistent document structure.
+
+#### Phase A: Skeleton Construction (BEFORE any content filling)
+
+1. Read PRD-TEMPLATE.md to identify the complete Feature Details structure
+2. Count the number of features from `{module_features}` input
+3. For Section 3.5 Feature Details, replicate the template's Feature block structure for EACH feature:
+   - Copy the EXACT template structure (all 6 sub-sections) from PRD-TEMPLATE.md
+   - Create `#### Feature 1: {feature_name}` through `#### Feature N: {feature_name}`
+   - Each feature block MUST contain these 6 sub-section headers (copied from template):
+     ```
+     **Requirement Description:**
+     [TO BE FILLED]
+     
+     **Interaction Flow:**
+     [TO BE FILLED]
+     
+     **Boundary Conditions:**
+     [TO BE FILLED]
+     
+     **Exception Scenarios:**
+     [TO BE FILLED]
+     
+     **Operation Flow Diagram:**
+     [TO BE FILLED]
+     
+     **Operation Steps Detail:**
+     [TO BE FILLED]
+     ```
+4. Verify skeleton: confirm ALL features have ALL 6 sub-section headers before proceeding
+
+> ⚠️ DO NOT start filling content until the complete skeleton is verified.
+
+#### Phase B: Content Filling (AFTER skeleton is complete)
+
+Fill each `[TO BE FILLED]` placeholder with actual content:
+- **Requirement Description** → Business requirements in business language
+- **Interaction Flow** → User interaction steps (numbered list)
+- **Boundary Conditions** → Table with Condition Type | Scenario | Handling Rule
+- **Exception Scenarios** → Bullet list of exception handling
+- **Operation Flow Diagram** → Mermaid `graph LR` diagram showing operation flow
+- **Operation Steps Detail** → Table: Step | Action | Expected Outcome | Exception Handling
+
+---
+
+### 4.3 Marking Existing vs New Features
 
 | Marker | Meaning |
 |--------|---------|
@@ -189,6 +238,13 @@ ELSE:
 
 ## Step 5: Task Granularity Check
 
+> **⚠️ CRITICAL: Section 3.5 Feature Details Skeleton Verification**
+>
+> Before proceeding, verify the two-phase strategy was correctly applied:
+> 1. Confirm ALL features in Section 3.5 have complete 6 sub-section skeletons
+> 2. Confirm no `[TO BE FILLED]` placeholders remain unfilled
+> 3. Confirm each feature has: Requirement Description, Interaction Flow, Boundary Conditions, Exception Scenarios, Operation Flow Diagram, Operation Steps Detail
+
 **After PRD completion, verify user story granularity:**
 
 **Appropriate Granularity (completable in one iteration):**

package/package.json

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