speccrew 0.1.0

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

@@ -0,0 +1,305 @@
+---
+name: speccrew-knowledge-module-summarize
+description: Summarize a module's features to complete MODULE-OVERVIEW.md. Reads all FEATURE-DETAIL.md files of a module and generates the complete module overview with entities, dependencies, and business rules.
+tools: Read, Write, Glob
+---
+
+# Module Summarize - Complete Module Overview
+
+Read all {{feature_name}}.md files of a specific module, extract and summarize information to complete {{module_name}}-overview.md (full version with entities, dependencies, flows, and rules).
+
+## Language Adaptation
+
+**CRITICAL**: Generate all content in the language specified by the `language` parameter.
+
+- `language: "zh"` → Generate all content in 中文
+- `language: "en"` → Generate all content in English
+- Other languages → Use the specified language
+
+**All output content (entity names, descriptions, business rules, flow descriptions) must be in the target language only.**
+
+## Trigger Scenarios
+
+- "Summarize module {name} features"
+- "Complete module overview for {name}"
+- "Finalize module documentation for {name}"
+
+## Input
+
+- `module_name`: Module name to summarize
+- `module_path`: Path to module directory (e.g., `speccrew-workspace/knowledges/bizs/{{platform_type}}/{{module_name}}/`) containing:
+  - {{module_name}}-overview.md (initial version)
+  - features/{{feature_name}}.md files
+- `language`: Target language for generated content (e.g., "zh", "en") - **REQUIRED**
+
+## Output
+
+- `{{module_path}}/{{module_name}}-overview.md` - Complete module overview (overwritten)
+
+## Workflow
+
+```mermaid
+flowchart TD
+    Start([Start]) --> Step1[Step 1: Read Prerequisites]
+    Step1 --> Step2[Step 2: Extract Entities]
+    Step2 --> Step3[Step 3: Identify Dependencies]
+    Step3 --> Step4[Step 4: Summarize Business Rules]
+    Step4 --> Step5[Step 5: Generate Complete MODULE-OVERVIEW.md]
+    Step5 --> Step6[Step 6: Report Results]
+    Step6 --> End([End])
+```
+
+### Step 1: Read Prerequisites
+
+Before processing, read all required files:
+
+1. **Read Template**: `templates/MODULE-OVERVIEW-TEMPLATE.md` - Understand the required content structure and section formats
+
+2. **Read Initial Module Overview**: `{{module_path}}/{{module_name}}-overview.md` (initial skeleton created by dispatch) containing:
+   - Section 1: Module Basic Information
+   - Section 2: Feature List Table with links to detail docs
+   - Remaining sections: Empty placeholders
+   - **If missing**: Create a minimal skeleton from feature inventory data
+
+3. **Read All Feature Details**: Find and read all `{{module_path}}/features/{{feature_name}}.md` files
+
+**Edge Cases**:
+- **No feature documents found**: Generate a minimal overview with only Section 1-2, return with `status: "partial"`
+- **Incomplete feature documents**: Extract available data, note gaps with `<!-- DATA INCOMPLETE: {feature_name} missing Section X -->`
+
+For each feature-detail.md, extract and categorize the following:
+
+**From Section 3 (Business Entities / State Objects)** — Priority: High
+- **Backend modules**: Entity names, database fields, types, relationships, ORM constraints
+- **Frontend modules**: State objects (Store/State), component prop interfaces, computed/derived data
+- Aggregate across features to build module-level entity list (deduplicate by entity name)
+
+**From Section 4 (Dependencies)** — Priority: High  
+- **Backend**: Internal module API calls, external service dependencies, shared DTOs
+- **Frontend**: Component imports, Store/State dependencies, route guard dependencies, shared composables/hooks
+- Classify as: "Provided by this module" vs "Consumed from other modules"
+
+**From Section 6 (Business Rules)** — Priority: High
+- Validation rules, state transitions, authorization rules, data consistency constraints
+- Associate each rule with its originating feature
+
+**From Section 5 (Core Processes)** — Priority: Medium
+- Step sequences, branching logic, exception handling paths
+- Identify cross-feature flows that span multiple features
+
+**From Section 2 (Feature Details / API Definitions)** — Priority: Medium
+- Data constraints: field types, ranges, uniqueness, required fields
+- Build constraint matrix for entities
+
+### Step 2: Extract Entities
+
+Aggregate entities from all features:
+
+```
+From Feature A: Order, OrderItem
+From Feature B: Order, Payment
+---------------------------------
+Module Entities: Order, OrderItem, Payment
+```
+
+For each entity, collect:
+- Fields and types
+- Validation constraints
+- Relationships (from multiple features)
+
+### Step 3: Identify Dependencies
+
+Analyze feature details to identify:
+- **Internal dependencies**: Other modules this module calls
+- **External dependencies**: Third-party services, APIs
+- **Data dependencies**: Shared entities, common DTOs
+
+### Step 4: Summarize Business Rules
+
+Collect all business rules from feature details:
+- Validation rules
+- State transition rules
+- Authorization rules
+- Data consistency rules
+
+### Step 5: Generate Complete MODULE-OVERVIEW.md
+
+**IMPORTANT**: ALL generated content (entity descriptions, business rules, flow descriptions, section headers, and narrative text) MUST be written in the language specified by the `language` parameter. Only code identifiers, file paths, and technical terms (class names, API endpoints) remain in their original language.
+
+1. **Read Configuration**:
+   - Read `speccrew-workspace/docs/rules/mermaid-rule.md` - Get Mermaid diagram compatibility guidelines
+
+2. **Use template `templates/MODULE-OVERVIEW-TEMPLATE.md`, fill all sections**:
+   - Follow [Mermaid Diagram Guide](#mermaid-diagram-guide) for diagram generation
+
+**Section 1: Module Basic Info** (from initial version)
+- Keep existing information
+
+**Section 2: Feature List** (from initial version)
+- Keep feature list table
+- Ensure all links to {{feature_name}}.md are correct
+
+**Section 3: Business Entities** (NEW)
+
+**Backend example:**
+| Entity Name | Description | Key Attributes | Business Rules |
+|---|---|---|---|
+| Order | Order master data | id, orderNo, amount, status | Status flow constraint |
+
+**Frontend example:**
+| Entity Name | Description | Key Attributes | Business Rules |
+|---|---|---|---|
+| OrderState | Order list view state | orders[], selectedOrder, loading, error | loading prevents re-fetch |
+| OrderFormProps | Order form component interface | order: Order, editable: boolean, onSave: Function | order required |
+
+Include ER diagram based on entity relationships.
+
+**Section 4: Dependencies** (NEW)
+
+**Backend example:**
+| Direction | Target | Content | Method |
+|---|---|---|---|
+| Uses | UserService | Get user info | API call |
+
+**Frontend example:**
+| Direction | Target | Content | Method |
+|---|---|---|---|
+| Imports | UserStore | Get user state | Store injection |
+| Imports | UserCard | Display user info | Component import |
+
+**Section 5: Core Business Flows** (NEW)
+
+Based on feature interactions, identify core flows:
+
+**Backend example:**
+Create Order: Validate params → Calculate amount → Save to DB → Notify downstream
+
+**Frontend example:**
+Order List: Load data → Display list → User selects → Load detail → Display detail → Edit → Submit → Update state
+
+**Section 6: Business Rules** (NEW)
+
+| Rule ID | Rule Name | Description | Related Features |
+|---------|-----------|-------------|------------------|
+| R001 | Order amount > 0 | Order total must be positive | create-order |
+| R002 | Stock check | Must check inventory before order | create-order |
+
+Apply source traceability rules (see [Reference Guides > Source Traceability Guide](#source-traceability-guide))
+
+### Step 6: Report Results
+
+```
+Module summarization completed:
+- Module: {{module_name}}
+- Features Processed: {{feature_count}}
+- Entities Extracted: {{entity_count}}
+- Dependencies Identified: {{dependency_count}}
+- Business Rules Summarized: {{rule_count}}
+- Output: {{module_name}}-overview.md (complete)
+- Status: success
+```
+
+## Reference Guides
+
+### Mermaid Diagram Guide
+
+When generating Mermaid diagrams, follow these compatibility guidelines:
+
+**Key Requirements:**
+- Use only basic node definitions: `A[text content]`
+- No HTML tags (e.g., `<br/>`)
+- No nested subgraphs
+- No `direction` keyword
+- No `style` definitions
+- Use standard `graph TB/LR` syntax only
+
+**Diagram Types:**
+
+| Diagram Type | Use Case | Example |
+|---------|---------|------|
+| `graph TB/LR` | Module structure, dependencies | Project structure diagram, dependency graph |
+| `sequenceDiagram` | Interaction flow, API calls | User operation flow, service call chain |
+| `flowchart TD` | Business logic, conditional branches | State transition, exception handling |
+| `classDiagram` | Class structure, entity relationships | Data model, service interface |
+| `erDiagram` | Database table relationships | Entity relationship diagram |
+| `stateDiagram-v2` | State machine | Order status, approval status |
+
+### Source Traceability Guide
+
+Aggregate source file references from all feature documents:
+
+> **Note**: Use relative paths from the generated document to the source file. Do NOT use `file://` protocol.
+
+**CRITICAL: Dynamic Relative Path Calculation**
+
+The document generation location is `speccrew-workspace/knowledges/bizs/{platform_id}/{module_path}/{file}.md`, which has a **variable depth** from the project root. You MUST dynamically calculate the relative path depth based on the actual document location.
+
+**Calculation Method:**
+1. Count the number of directory separators (`/`) from the project root to the document's directory
+2. Each directory level requires one `../` to traverse up to the project root
+3. Example: Document at `speccrew-workspace/knowledges/bizs/backend-ai/chat/overview.md` (5 levels) → Use `../../../../../src/...`
+
+**Common Path Depths Reference:**
+| Document Location | Depth | Relative Path Prefix |
+|---|---|---|
+| `speccrew-workspace/knowledges/bizs/{platform}/{module}/` | 5+ | `../../../../../` |
+| `speccrew-workspace/knowledges/bizs/{platform}/{module}/{sub}/` | 6+ | `../../../../../../` |
+
+**Source reference examples by tech stack (assuming document at depth 5):**
+
+Backend (Java): `[OrderController.java](../../../../../src/main/java/.../OrderController.java#L10-L25)`
+Backend (Python): `[views.py](../../../../../app/order/views.py#L10-L25)`
+Backend (Node.js): `[orderController.js](../../../../../src/modules/order/orderController.js#L10-L25)`
+Frontend (Vue): `[OrderList.vue](../../../../../src/views/order/OrderList.vue#L10-L25)`
+Frontend (React): `[OrderDetail.tsx](../../../../../src/pages/order/OrderDetail.tsx#L10-L25)`
+
+1. **File Reference Block** (at document start):
+```markdown
+<cite>
+**Referenced Files**
+- [OrderController.*](path/to/source/OrderController.*)
+- [OrderService.*](path/to/source/OrderService.*)
+</cite>
+```
+
+2. **Diagram Source** (after each Mermaid diagram):
+```markdown
+**Diagram Source**
+- [OrderController.*](path/to/source/OrderController.*#L45-L60)
+```
+
+3. **Section Source** (at end of document):
+```markdown
+**Section Source**
+- [OrderController.*](path/to/source/OrderController.*#L1-L100)
+- [OrderService.*](path/to/source/OrderService.*#L1-L80)
+```
+
+## Notes
+
+> **Note**: This skill focuses on document aggregation only. Knowledge graph data (nodes, edges) is handled separately by the dispatch skill's `process-batch-results.js` script during Stage 2. Module-summarize does NOT read from or write to the knowledge graph.
+
+## Return
+
+**Return Value (JSON format):**
+
+```json
+{
+  "status": "success|failed",
+  "module_name": "module_name",
+  "output_file": "module_name-overview.md",
+  "message": "Module summarization completed with N features processed"
+}
+```
+
+---
+
+## Checklist
+
+- [ ] Step 1: Prerequisites read (template, initial overview, feature details)
+- [ ] Step 2: Entities extracted and aggregated
+- [ ] Step 3: Dependencies identified
+- [ ] Step 4: Business rules collected
+- [ ] Step 5: Section 3-6 completed in {{module_name}}-overview.md
+- [ ] Step 6: Results reported
+

package/.speccrew/skills/speccrew-knowledge-module-summarize/templates/MODULE-OVERVIEW-TEMPLATE.md

@@ -0,0 +1,400 @@
+# Module Overview Document - [Module Name]
+
+> **Applicable Scenario**: Describes a single business module's responsibility boundaries, feature list, entity relationships, and external dependencies, for AI Agent to understand module details
+> **Target Audience**: devcrew-product-manager, devcrew-solution-manager, devcrew-developer
+> **Related Document**: [System Overview Document](../system-overview.md)
+> 
+> <!-- AI-TAG: MODULE_OVERVIEW -->
+> <!-- AI-CONTEXT: Read this document to understand module responsibilities, feature list, entity relationships, and dependency interfaces, used for requirement analysis and solution design -->
+
+<cite>
+**Referenced Files**
+<!-- Path Note: {relativePath} must be dynamically calculated based on document depth. See SKILL.md "Source Traceability Guide" for calculation method. -->
+- [{EntryPoint}]({relativePath}/{sourcePath}/{entryPointFile})    <!-- Backend: Controller/View/Router; Frontend: Page/View component -->
+- [{BusinessLogic}]({relativePath}/{sourcePath}/{businessLogicFile})  <!-- Backend: Service; Frontend: Store/Composable/Hook -->
+- [{DataModel}]({relativePath}/{sourcePath}/{dataModelFile})      <!-- Backend: Entity/Model; Frontend: Type/Interface definition -->
+</cite>
+
+---
+
+## 1. Module Basic Information
+
+### 1.1 Module Positioning
+
+| Item | Description |
+|------|-------------|
+| Module Name | {Fill in module name} |
+| Business Domain | {e.g., Sales Domain, Inventory Domain} |
+| Module Responsibility | {One sentence describing core module responsibility} |
+| Business Value | {What business problem it solves, what value it brings} |
+
+### 1.2 Module Boundary
+
+<!-- AI-TAG: MODULE_BOUNDARY -->
+<!-- AI-NOTE: Module boundaries help AI understand responsibility scope, avoiding scope creep during requirement analysis -->
+
+```mermaid
+graph TB
+    subgraph ThisModule["{Module Name}"]
+        subgraph Responsible["Responsible"]
+            R1[Responsibility 1: Order lifecycle management]
+            R2[Responsibility 2: Order status flow control]
+            R3[Responsibility 3: Order data statistics]
+        end
+    end
+    
+    subgraph External["External Modules"]
+        subgraph DependsOn["This Module Depends On"]
+            D1[Module X: Get user data]
+            D2[Module Y: Get product data]
+        end
+        
+        subgraph DependedBy["Depend On This Module"]
+            U1[Module Z: Use order data]
+            U2[Module W: Receive status notification]
+        end
+        
+        subgraph NotResponsible["Not Responsible"]
+            NR1[Payment Processing: Payment Module]
+            NR2[Logistics Tracking: Logistics Module]
+        end
+    end
+    
+    ThisModule -.-> D1
+    ThisModule -.-> D2
+    U1 -.-> ThisModule
+    U2 -.-> ThisModule
+```
+
+**Diagram Source**
+- [{Module} Entry Point]({relativePath}/{sourcePath}/{moduleEntryFile})
+
+**Boundary Description:**
+| Type | Content | Description |
+|------|---------|-------------|
+| **Responsible** | {Responsibility 1, Responsibility 2, Responsibility 3} | Core responsibilities of this module |
+| **Depends On** | {Module X, Module Y} | External modules called by this module |
+| **Depended By** | {Module Z, Module W} | External modules that call this module |
+| **Not Responsible** | {Payment Processing, Logistics Tracking} | Explicitly out of this module's scope |
+
+---
+
+## 2. Feature List
+
+### 2.1 Feature Tree
+
+<!-- AI-TAG: FEATURE_TREE -->
+<!-- AI-NOTE: Feature tree helps AI understand module feature structure, used for requirement matching and scope judgment -->
+
+```mermaid
+mindmap
+  root(([{Module Name}]))
+    Feature Group A
+      Feature A1 ✅
+      Feature A2 ✅
+      Feature A3 🚧
+      Feature A4 ⏳
+    Feature Group B
+      Feature B1 ✅
+      Feature B2 🚧
+    Feature Group C
+      Feature C1 ⏳
+      Feature C2 ⏳
+```
+
+**Status Legend:** ✅ Released / 🚧 In Development / ⏳ Planned / ❌ Deprecated
+
+### 2.2 Feature List Table
+
+| Feature Group | Feature | Description | Status | Priority | Remarks |
+|---------------|---------|-------------|--------|----------|---------|
+| {Order Management} | {Create Order} | {Supports manual/import creation} | ✅ | P0 | {Released} |
+| {Order Management} | {Query Order} | {Multi-dimensional filter query} | ✅ | P0 | {Released} |
+| {Order Review} | {Submit Review} | {Submit order to review process} | 🚧 | P1 | {In Development} |
+| {Data Statistics} | {Order Report} | {Statistics by time/region} | ⏳ | P2 | {Planned} |
+
+---
+
+## 3. Business Entities and Relationships
+
+### 3.1 Core Entity List
+
+| Entity Name | Type | Description | Key Attributes | Business Rules |
+|---|---|---|---|---|
+| *{Entity1}* | *Data Entity / State Object* | *{description}* | *{key fields}* | *{constraints}* |
+
+<!-- 
+Backend examples: Order (DB Entity), OrderDTO (Data Transfer Object)
+Frontend examples: OrderState (Store State), OrderFormProps (Component Interface)
+-->
+
+### 3.2 Entity Relationship Diagram
+
+<!-- AI-TAG: ENTITY_RELATIONSHIP -->
+<!-- AI-NOTE: ER diagram is crucial for Solution Agent to design databases and APIs -->
+
+```mermaid
+erDiagram
+    ENTITY_A["Entity A: Order Master"] {
+        int OrderID PK
+        string OrderNo UK
+        decimal OrderAmount
+        int OrderStatus
+        datetime CreateTime
+    }
+    
+    ENTITY_B["Entity B: Order Detail"] {
+        int DetailID PK
+        int OrderID FK
+        int ProductID
+        int Quantity
+        decimal UnitPrice
+        decimal Subtotal
+    }
+    
+    ENTITY_C["Entity C: Order Log"] {
+        int LogID PK
+        int OrderID FK
+        int OperationType
+        string OperationContent
+        datetime OperationTime
+        int Operator
+    }
+    
+    ENTITY_D["Entity D: Order Attachment"] {
+        int AttachmentID PK
+        int OrderID FK
+        string AttachmentName
+        string AttachmentPath
+        datetime UploadTime
+    }
+    
+    ENTITY_A ||--o{ ENTITY_B : "1:N"
+    ENTITY_A ||--o{ ENTITY_C : "1:N"
+    ENTITY_A ||--o{ ENTITY_D : "1:N"
+```
+
+<!-- For frontend modules, replace ER diagram with State Relationship diagram:
+```mermaid
+classDiagram
+    class OrderState {
+        +Order[] orders
+        +Order selectedOrder
+        +boolean loading
+        +string error
+        +fetchOrders()
+        +selectOrder(id)
+    }
+    class OrderFormState {
+        +Order formData
+        +boolean isDirty
+        +Object errors
+        +validate()
+        +submit()
+    }
+    OrderState --> OrderFormState : provides selectedOrder
+```
+-->
+
+### 3.3 Entity State Transition
+
+<!-- AI-TAG: STATE_MACHINE -->
+<!-- AI-NOTE: State machine is important for understanding business rules and implementing state control logic -->
+
+**Entity A (Order) State Machine:**
+
+```mermaid
+stateDiagram-v2
+    [*] --> Draft: Create Order
+    
+    Draft --> PendingReview: Submit Review
+    Draft --> Cancelled: Cancel Order
+    
+    PendingReview --> Approved: Review Passed
+    PendingReview --> Rejected: Review Rejected
+    
+    Approved --> Completed: Business Complete
+    
+    Rejected --> Draft: Re-edit
+    
+    Cancelled --> [*]
+    Completed --> [*]
+    
+    note right of Draft
+        Initial state
+        Editable
+    end note
+    
+    note right of Approved
+        Review passed
+        Not modifiable
+    end note
+```
+
+| State | Description | Transferable States | Trigger Condition |
+|-------|-------------|---------------------|-------------------|
+| {Draft} | {Draft state} | {PendingReview/Cancelled} | {Submit/Cancel} |
+| {PendingReview} | {Waiting for review} | {Approved/Rejected} | {Review passed/rejected} |
+| {Approved} | {Review passed} | {Completed} | {Business complete} |
+
+---
+
+## 4. External Dependencies and Interfaces
+
+### 4.1 Module Dependency Relationships
+
+| Dependency Direction | Module Name | Dependency Content | Dependency Method | Description |
+|---------------------|-------------|-------------------|-------------------|-------------|
+| {This module depends on} | {User Center} | {Get user info} | {API call} | {Get details by user ID} |
+| {This module depends on} | {Product Module} | {Get product info} | {API call} | {Get details by product ID} |
+| {Depends on this module} | {Payment Module} | {Query order info} | {API call} | {Validate order during payment} |
+| {Depends on this module} | {Logistics Module} | {Receive order shipment} | {Message subscription} | {Notify after order review passed} |
+
+### 4.2 External Interfaces Provided
+
+| Interface Name | Type | Caller/Consumer | Description |
+|---|---|---|---|
+| *{Interface1}* | *API / Component / Hook / Event* | *{caller}* | *{description}* |
+
+<!-- 
+Backend examples: GET /api/orders (REST API), OrderCreatedEvent (Message)
+Frontend examples: <OrderDetail :order="order" /> (Component Props), useOrder(id) (Hook/Composable), emit('save', order) (Event)
+-->
+
+### 4.3 Dependent Module Interfaces
+
+| Interface Name | Provider | Function Description | Call Scenario |
+|----------------|----------|---------------------|---------------|
+| {Get User} | {User Center} | {Get user by ID} | {Validate when creating order} |
+| {Get Product} | {Product Module} | {Get product by ID} | {Validate when creating order} |
+
+---
+
+## 5. Core Business Processes
+
+### 5.1 Core Process Within Module
+
+<!-- AI-TAG: CORE_PROCESS -->
+<!-- AI-NOTE: Core processes are important for Solution Agent to design solutions and plan interfaces -->
+
+**Process: {Create Order Process}**
+
+```mermaid
+flowchart TD
+    Start([Start]) --> Validate[Validate Parameters]
+    
+    Validate -->|Passed| Calculate[Calculate Amount]
+    Validate -->|Failed| ValError[Return Parameter Error]
+    ValError --> End1([End])
+    
+    Calculate --> Save[Save Order]
+    Calculate -->|Exception| CalError[Return Calculation Error]
+    CalError --> End1
+    
+    Save -->|Success| Notify[Notify Downstream]
+    Save -->|DB Exception| SaveError[Return System Error]
+    SaveError --> End1
+    
+    Notify -->|Success| End2([End])
+    Notify -->|Failed| LogError[Log Compensation]
+    LogError --> End2
+```
+
+**Diagram Source**
+- [{Module} Business Logic]({relativePath}/{sourcePath}/{moduleLogicFile})
+
+**Process Step Description:**
+
+| Step | Step Name | Processing Logic | Input | Output | Exception Handling |
+|------|-----------|------------------|-------|--------|-------------------|
+| 1 | {Parameter Validation} | {Validate user, product, inventory} | {Request parameters} | {Validation result} | {Return parameter error} |
+| 2 | {Amount Calculation} | {Calculate product amount, discount, shipping} | {Product info} | {Order amount} | {Calculation exception} |
+| 3 | {Save Order} | {Write to order master and detail tables} | {Order data} | {Order ID} | {Database exception} |
+| 4 | {Notify Downstream} | {Send order creation message} | {Order ID} | {Send result} | {Log only, no retry} |
+
+<!-- For frontend modules, core processes typically include:
+1. Data Loading Flow: Component mount → Fetch data → Loading state → Render
+2. User Interaction Flow: User action → Validate → API call → Update state → Feedback
+3. Navigation Flow: Route change → Guard check → Load page data → Render
+-->
+
+### 5.2 Exception Handling Rules
+
+| Exception Scenario | Exception Type | Handling Strategy | User Prompt | Log Record |
+|-------------------|----------------|-------------------|-------------|------------|
+| {Parameter validation failed} | {Business Exception} | {Return error directly} | {Show specific error} | {Log warning} |
+| {Product not exist} | {Business Exception} | {Return error} | {Prompt product invalid} | {Log warning} |
+| {Database timeout} | {System Exception} | {Retry 3 times} | {Prompt system busy} | {Log error} |
+| {Downstream notification failed} | {System Exception} | {Log for compensation} | {No prompt to user} | {Log error} |
+
+---
+
+## 6. Business Rules and Constraints
+
+### 6.1 Business Rules
+
+| Rule ID | Rule Name | Rule Description | Trigger Scenario | Related Entity |
+|---------|-----------|------------------|------------------|----------------|
+| {R001} | {Order Amount Validation} | {Order amount must be greater than 0} | {When creating order} | {Order Master} |
+| {R002} | {Inventory Deduction Rule} | {Deduct inventory after order review passed} | {When review passed} | {Order+Inventory} |
+| {R003} | {Status Flow Rule} | {Completed orders cannot be modified} | {When modifying order} | {Order Master} |
+
+### 6.2 Data Constraints
+
+| Constraint Type | Constraint Object | Constraint Rule | Description |
+|-----------------|-------------------|-----------------|-------------|
+| {Uniqueness} | {Order No} | {Globally unique} | {Business order number, cannot duplicate} |
+| {Required} | {User ID} | {Not null} | {Must associate with user} |
+| {Range} | {Order Amount} | {≥0} | {Amount cannot be negative} |
+| {Association} | {Order Detail} | {At least 1 item} | {Order must have details} |
+
+### 6.3 Permission Rules
+
+| Operation / Component | Required Permission | No Permission Handling |
+|---|---|---|
+| *{operation or component}* | *{permission}* | *{handling}* |
+
+<!-- 
+Backend: Create Order → order:create → Return 403
+Frontend: /orders/create route → order:create → Redirect to 403 page
+Frontend: <CreateButton /> → order:create → Hide component
+Frontend: Price field in OrderForm → order:edit_price → Readonly
+-->
+
+---
+
+## 7. Related Pages and Prototypes (Optional)
+
+### 7.1 Page List
+
+| Page Name | Page Type | Function Description | Related Feature | Prototype Document |
+|-----------|-----------|---------------------|-----------------|-------------------|
+| {Order List Page} | {List Page} | {Display order list} | {Query Order} | [Link](ui-prototype.md) |
+| {Order Detail Page} | {Detail Page} | {Display order details} | {View Order} | [Link](ui-prototype.md) |
+| {Order Edit Page} | {Form Page} | {Edit order info} | {Modify Order} | [Link](ui-prototype.md) |
+
+### 7.2 Page Prototype
+
+> For detailed page prototypes, please refer to [Feature Detail Design Template](./FEATURE-DETAIL-TEMPLATE.md)
+
+---
+
+## 8. Change History
+
+| Date | Version | Change Content | Change Type | Owner | Impact Scope |
+|------|---------|----------------|-------------|-------|--------------|
+| {Date} | {v1.2} | {Added order review feature} | {New Feature} | {Zhang San} | {Added review status, review interface} |
+| {Date} | {v1.1} | {Optimized order query performance} | {Performance} | {Li Si} | {Query interface} |
+| {Date} | {v1.0} | {Module initial version} | {Initial Release} | {Wang Wu} | {All} |
+
+---
+
+**Document Status:** 📝 Draft / 👀 In Review / ✅ Published  
+**Last Updated:** {Date}  
+**Maintainer:** {Name}  
+**Related System Document:** [System Overview Document](../system-overview.md)
+
+**Section Source**
+- [{Module} Entry]({relativePath}/{sourcePath}/{moduleEntryFile})
+- [{Module} Logic]({relativePath}/{sourcePath}/{moduleLogicFile})
+- [{Module} Model]({relativePath}/{sourcePath}/{moduleModelFile})