speccrew 0.1.0

package/.speccrew/skills/speccrew-pm-requirement-analysis/templates/BIZS-MODELING-TEMPLATE.md

@@ -0,0 +1,332 @@
+# Business Modeling - [Feature/Skill Name]
+
+## Document Info
+
+| Item | Value |
+|------|-------|
+| Modeling Target | __________ |
+| Modeling Type | ☐ Agent Skill ☐ Business Feature ☐ System Module |
+| Author | __________ |
+| Date | __________ |
+| Priority | ☐ High ☐ Medium ☐ Low |
+| Version | __________ |
+
+---
+
+## 1. Domain Description
+
+<!-- AI-NOTE: Define WHAT the system is and WHERE its boundaries lie. -->
+
+### 1.1 Domain Boundary
+
+**Domain**: __________
+
+**In-Scope**:
+- __________
+- __________
+
+**Out-of-Scope**:
+- __________
+- __________
+
+### 1.2 External Participants
+
+| Participant Type | Name | Description |
+|------------------|------|-------------|
+| User | __________ | __________ |
+| System | __________ | __________ |
+| Agent | __________ | __________ |
+
+### 1.3 Domain Glossary
+
+| Term | Definition | Related Domain |
+|------|------------|----------------|
+| __________ | __________ | __________ |
+
+### 1.4 System Context Diagram
+
+```mermaid
+graph TD
+    A[External Actor 1] --> B[Target System]
+    C[External Actor 2] --> B
+    D[External System] --> B
+```
+
+---
+
+## 2. Functions in Domain
+
+<!-- AI-NOTE: List ALL functions within domain boundary. Don't filter yet. -->
+
+### 2.1 Function Decomposition (WBS)
+
+```mermaid
+graph TD
+    A[Main Function] --> B[Sub Function 1]
+    A --> C[Sub Function 2]
+    A --> D[Sub Function 3]
+    B --> B1[Task 1.1]
+    B --> B2[Task 1.2]
+```
+
+### 2.2 Function-Capability Mapping Table
+
+| Function Module | Core Sub-function | Business Capability | UML Visualization |
+|-----------------|-------------------|---------------------|-------------------|
+| __________ | __________ | __________ | Use Case / Activity / State |
+
+### 2.3 UML Visualization (As Needed)
+
+<!-- AI-NOTE: Choose: Use Case Diagram (actor-function), Activity Diagram (process flow), State Machine (entity lifecycle only) -->
+
+#### 2.3.1 Use Case Diagram
+
+```mermaid
+graph TB
+    subgraph Actors
+        A1[Actor 1]
+    end
+    subgraph System
+        UC1[Use Case 1]
+        UC2[Use Case 2]
+    end
+    A1 --> UC1
+    A1 --> UC2
+```
+
+#### 2.3.2 Activity Diagram
+
+```mermaid
+flowchart TD
+    A[Start] --> B[Action 1]
+    B --> C{Decision}
+    C -->|Path 1| D[Action 2]
+    C -->|Path 2| E[Action 3]
+    D --> F[End]
+    E --> F
+```
+
+#### 2.3.3 State Machine Diagram (Core Entities Only)
+
+```mermaid
+stateDiagram-v2
+    [*] --> State1
+    State1 --> State2 : Trigger 1
+    State2 --> State3 : Trigger 2
+    State3 --> [*]
+```
+
+---
+
+## 3. Functions of Interest
+
+<!-- AI-NOTE: Focus on CORE functions for MVP. Use MoSCoW method. -->
+
+### 3.1 Core Function Selection (MoSCoW)
+
+| Function Name | Priority | Is Core? | Notes |
+|---------------|----------|----------|-------|
+| __________ | Must have | Yes/No | __________ |
+| __________ | Should have | Yes/No | __________ |
+| __________ | Could have | Yes/No | __________ |
+| __________ | Won't have | Yes/No | __________ |
+
+### 3.2 Core Function Use Case Diagram
+
+```mermaid
+graph TB
+    A[Actor]
+    subgraph System
+        UC1[Core Use Case 1]
+        UC2[Core Use Case 2]
+    end
+    A --> UC1
+    A --> UC2
+```
+
+### 3.3 Non-core Function Notes
+
+| Function | Current Status | Planned Iteration |
+|----------|----------------|-------------------|
+| __________ | Deferred | Iteration X |
+
+---
+
+## 4. Information Flows of Interest
+
+<!-- AI-NOTE: Document HOW information flows between core functions and external systems. -->
+
+### 4.1 Core Information Flow Description
+
+**Description**: __________
+
+**Data Sources**: __________
+
+**Data Destinations**: __________
+
+**Flow Frequency**: __________
+
+### 4.2 Sequence Diagram
+
+```mermaid
+sequenceDiagram
+    participant U as User
+    participant S as System
+    participant D as Database
+    
+    U->>S: Submit request
+    S->>D: Query data
+    D-->>S: Return result
+    S-->>U: Display result
+```
+
+### 4.3 Data Flow Diagram (DFD)
+
+```mermaid
+graph TD
+    subgraph System
+        P1[Process 1]
+        P2[Process 2]
+    end
+    E1[External Entity 1] -- Data Flow 1 --> P1
+    P1 -- Data Flow 2 --> P2
+    P2 -- Data Flow 3 --> E2[External Entity 2]
+```
+
+### 4.4 Interface Interaction List
+
+| Interface Name | Direction | Data Format | Frequency | Core Fields |
+|----------------|-----------|-------------|-----------|-------------|
+| __________ | User→System | JSON/XML | Real-time | __________ |
+
+---
+
+## 5. Categories of Information
+
+<!-- AI-NOTE: Define WHAT data entities exist. Focus on business concepts, not implementation. -->
+
+### 5.1 Information Category Directory
+
+| Information Category | Core Entity | Related Stage | Description |
+|---------------------|-------------|---------------|-------------|
+| __________ | __________ | Stage X | __________ |
+
+### 5.2 Data Dictionary
+
+| Entity Name | Core Attributes | Data Type | Constraints | Description |
+|-------------|-----------------|-----------|-------------|-------------|
+| __________ | __________ | String/Number/Enum | Non-null | __________ |
+
+### 5.3 Conceptual Class Diagram
+
+```mermaid
+classDiagram
+    class Entity1 {
+        +attribute1
+        +attribute2
+    }
+    class Entity2 {
+        +attribute3
+    }
+    Entity1 "1" -- "*" Entity2 : relates
+```
+
+---
+
+## 6. Information Descriptions
+
+<!-- AI-NOTE: IMPLEMENTATION-READY specifications with technical details. -->
+
+### 6.1 Design Class Diagram
+
+```mermaid
+classDiagram
+    class ClassName {
+        -privateAttribute: Type
+        +publicMethod(): ReturnType
+    }
+    class InterfaceName {
+        +interfaceMethod(): ReturnType
+    }
+    ClassName ..|> InterfaceName : implements
+```
+
+### 6.2 Component Diagram
+
+```mermaid
+graph TB
+    C1[Component 1] --> C2[Component 2]
+    C2 --> C3[Component 3]
+```
+
+### 6.3 Information Description Standards
+
+**Output Format**: __________
+
+**Encoding**: UTF-8
+
+**Validation Rules**:
+- __________
+
+**Storage Requirements**: __________
+
+---
+
+## 7. Acceptance Criteria
+
+### 7.1 Functional Acceptance
+
+| Function | Acceptance Condition | Verification Method |
+|----------|---------------------|---------------------|
+| __________ | __________ | Test / Demo / Review |
+
+### 7.2 Performance Acceptance
+
+| Metric | Target | Measurement Method |
+|--------|--------|-------------------|
+| Response Time | ≤ X ms | __________ |
+| Accuracy | ≥ X% | __________ |
+
+### 7.3 Interface Acceptance
+
+| Interface | Success Rate | Error Handling |
+|-----------|-------------|----------------|
+| __________ | ≥ X% | __________ |
+
+---
+
+## 8. Risks and Constraints
+
+### 8.1 Risks
+
+| Risk | Probability | Impact | Mitigation |
+|------|-------------|--------|------------|
+| __________ | High/Medium/Low | High/Medium/Low | __________ |
+
+### 8.2 Constraints
+
+| Constraint Type | Description |
+|-----------------|-------------|
+| Technical | __________ |
+| Business | __________ |
+
+---
+
+## 9. References
+
+### 9.1 Related System Modules
+
+| Module | Relationship | Document Link |
+|--------|-------------|---------------|
+| __________ | Dependency / Dependent | [Link] |
+
+### 9.2 Reference Documents
+
+| Document | Description |
+|----------|-------------|
+| ISA-95 Standard | Business modeling methodology |
+| UML Specification | Visual modeling language |
+
+---
+
+> Document generated using ISA-95 six-stage methodology. Mermaid diagrams follow mermaid-rule.md guidelines.

package/.speccrew/skills/speccrew-pm-requirement-analysis/templates/PRD-TEMPLATE.md

@@ -0,0 +1,200 @@
+# PRD - [Feature Name]
+
+## 1. Background & Goals
+
+### 1.1 Background
+[Describe why this feature is needed and what problem it solves]
+
+### 1.2 Goals
+[Describe the business objectives to be achieved]
+
+## 2. User Stories
+
+### 2.1 Target Users
+[Describe who will use this feature]
+
+### 2.2 User Scenarios
+
+**Scenario 1: [Scenario Name]**
+- **As a** [role]
+- **I want** [action]
+- **So that** [value]
+
+**Scenario 2: [Scenario Name]**
+...
+
+## 3. Functional Requirements
+
+### 3.1 Use Case Diagram
+
+```mermaid
+flowchart TB
+    %% Actor definitions (stadium shape represents actors)
+    U([🧑 User])
+    A([🧑 Admin])
+    
+    %% Use case nodes
+    UC1(Core Feature 1)
+    UC2(Core Feature 2)
+    UC3(Core Feature 3)
+    UC4(Management Feature)
+    
+    %% Relationships
+    U --> UC1
+    U --> UC2
+    U --> UC3
+    A --> UC4
+    A --> UC1
+    
+    %% Include relationships
+    UC1 -.-> UC2
+```
+
+**Use Case Description:**
+
+| Use Case ID | Name | Actor | Description |
+|-------------|------|-------|-------------|
+| UC-001 | Core Feature 1 | User, Admin | [Description] |
+| UC-002 | Core Feature 2 | User | [Description] |
+| UC-003 | Core Feature 3 | User | [Description] |
+| UC-004 | Management Feature | Admin | [Description] |
+
+### 3.2 Business Process Flow
+
+```mermaid
+graph TB
+    %% Process stages
+    START([Start])
+    P1[Stage 1: Input/Preparation]
+    P2[Stage 2: Processing]
+    P3[Stage 3: Validation]
+    P4[Stage 4: Completion]
+    END([End])
+    
+    %% Decision points
+    D1{Valid?}
+    D2{Approved?}
+    
+    %% Flow
+    START --> P1
+    P1 --> P2
+    P2 --> P3
+    P3 --> D1
+    D1 -->|Yes| D2
+    D1 -->|No| P1
+    D2 -->|Yes| P4
+    D2 -->|No| END
+    P4 --> END
+```
+
+**Process Description:**
+
+| Stage | Description | Input | Output | Responsible Role |
+|-------|-------------|-------|--------|------------------|
+| Stage 1 | [Description] | [Input data] | [Output data] | [Role] |
+| Stage 2 | [Description] | [Input data] | [Output data] | [Role] |
+| Stage 3 | [Description] | [Input data] | [Output data] | [Role] |
+| Stage 4 | [Description] | [Input data] | [Output data] | [Role] |
+
+### 3.3 Feature List
+
+| Feature | Priority | Description | Acceptance Criteria |
+|---------|----------|-------------|---------------------|
+| [Feature 1] | P0 | [Description] | [Acceptance Criteria] |
+| [Feature 2] | P1 | [Description] | [Acceptance Criteria] |
+
+### 3.2 Feature Details
+
+#### Feature 1: [Feature Name]
+
+**Requirement Description:**
+[Detailed description of this feature's specific requirements]
+
+**Interaction Flow:**
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+**Boundary Conditions:**
+| Condition Type | Scenario Description | Expected Handling |
+|----------------|---------------------|-------------------|
+| Edge Cases | [e.g., empty input, too long, special characters] | [Handling method] |
+| Concurrency/Race | [e.g., duplicate submission, concurrent operations] | [Handling method] |
+| Permission Boundary | [e.g., unauthorized access, not logged in] | [Handling method] |
+| Dependency Failure | [e.g., third-party service unavailable] | [Handling method] |
+
+**Exception Scenarios:**
+- [Exception 1]: [Handling method]
+- [Exception 2]: [Handling method]
+
+**Operation Flow Diagram:**
+
+```mermaid
+graph LR
+    %% Operation steps
+    S1[Step 1: Action]
+    S2[Step 2: Action]
+    S3[Step 3: Action]
+    S4[Step 4: Action]
+    
+    %% Alternative paths
+    ALT1[Alternative Path A]
+    ALT2[Alternative Path B]
+    
+    %% Flow
+    S1 --> S2
+    S2 --> S3
+    S3 --> S4
+    
+    %% Alternative flows
+    S2 -.-> ALT1
+    S3 -.-> ALT2
+    ALT1 --> S4
+    ALT2 --> S4
+```
+
+**Operation Steps Detail:**
+
+| Step | Action | System Response | User Feedback | Exception Handling |
+|------|--------|-----------------|---------------|-------------------|
+| 1 | [User action] | [System behavior] | [UI feedback] | [Error handling] |
+| 2 | [User action] | [System behavior] | [UI feedback] | [Error handling] |
+| 3 | [User action] | [System behavior] | [UI feedback] | [Error handling] |
+| 4 | [User action] | [System behavior] | [UI feedback] | [Error handling] |
+
+## 4. Non-functional Requirements
+
+- **Performance**: [Performance requirements]
+- **Security**: [Security requirements]
+- **Compatibility**: [Compatibility requirements]
+
+## 5. Acceptance Criteria
+
+### 5.1 Must Have
+- [ ] [Acceptance Item]
+- [ ] [Acceptance Item]
+
+### 5.2 Should Have
+- [ ] [Acceptance Item]
+- [ ] [Acceptance Item]
+
+## 6. Boundary Description
+
+### 6.1 In Scope
+- [Scope Item]
+- [Scope Item]
+
+### 6.2 Out of Scope
+- [Scope Item]
+- [Scope Item]
+
+## 7. Assumptions & Dependencies
+
+- **Assumptions**: [Prerequisites]
+- **Dependencies**: [Other features/systems depended upon]
+
+---
+
+**PRD Status:** 📝 Draft / 👀 In Review / ✅ Confirmed  
+**Confirmation Date:** [Date]  
+**Confirmed By:** [Name]

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

@@ -0,0 +1,195 @@
+---
+name: speccrew-pm-requirement-assess
+description: Quick impact assessment for new requirements. Analyzes affected modules, change type, risk level, and cross-module dependencies using system documentation and knowledge graph. Use when PM Agent needs a lightweight evaluation before deciding whether to run full requirement-analysis workflow.
+tools: Read, Glob, Grep
+---
+
+# Requirement Assessment for Product Manager
+
+Guide PM Agent to quickly assess new requirements using system documentation, module knowledge, and knowledge graph.
+
+## Trigger Scenarios
+
+- "Assess impact scope of new requirement"
+- "Analyze which modules are affected by requirement"
+- "Determine if requirement is new or modification"
+- "Quick requirement assessment"
+- "New requirement impact analysis"
+- "How big is this requirement?"
+
+## User
+
+PM Agent (speccrew-product-manager)
+
+## Input
+
+- New requirement description
+- system-overview.md (system documentation)
+- Related {name}-overview.md files (if specific modules identified)
+- Knowledge graph (for cross-module dependency analysis)
+
+## Output
+
+- Requirement assessment report with:
+  - Impact scope (modules affected, direct + indirect)
+  - Change type (New/Modify/Mixed/Cross-module/Config)
+  - Risk level with specific factors
+  - Recommended workflow path (simple PRD vs full ISA-95 modeling)
+
+## Assessment Workflow
+
+### Step 1: Understand the Requirement
+
+Analyze the new requirement:
+- What business problem does it solve?
+- What entities are involved?
+- What processes are affected?
+
+### Step 2: Load System Context
+
+#### 2.1 Read System Overview
+
+```
+speccrew-workspace/knowledges/bizs/system-overview.md
+```
+
+Identify:
+- Which business domain the requirement belongs to
+- Which modules are potentially related
+- Which business processes are involved
+
+#### 2.2 Load Related Module Overviews
+
+For each potentially affected module:
+```
+speccrew-workspace/knowledges/bizs/{module-name}/{module-name}-overview.md
+```
+
+#### 2.3 Query Knowledge Graph (for cross-module analysis)
+
+Use `speccrew-knowledge-graph-query` skill to trace dependencies:
+
+| Action | Use Case |
+|--------|----------|
+| `search` | Find entities related to requirement keywords |
+| `trace-upstream` | What depends on the affected entities? |
+| `trace-downstream` | What do the affected entities depend on? |
+| `query-nodes` | List all entities in a suspected module |
+
+### Step 3: Determine Change Type
+
+Use decision tree:
+
+```
+New Requirement
+    |
+    +-- Involves new business entity?
+    |      +-- NEW FEATURE
+    |
+    +-- Modifies core attributes of existing entity?
+    |      +-- MODIFICATION
+    |
+    +-- Adds new process steps but reuses existing entities?
+    |      +-- MIXED (New + Modify)
+    |
+    +-- Affects cross-module data flow?
+    |      +-- CROSS-MODULE CHANGE
+    |
+    +-- Can be handled by configuration?
+           +-- CONFIGURATION
+```
+
+### Step 4: Identify Impact Scope
+
+Check for impact on:
+- **Direct modules**: Modules explicitly mentioned in requirement
+- **Dependency modules**: Upstream/downstream from graph query (Step 2.3)
+- **External integrations**: Third-party systems
+- **Data entities**: New or modified entities
+
+### Step 5: Assess Risk Level
+
+| Risk Factor | High Risk Indicators |
+|-------------|---------------------|
+| Scope | Affects 3+ modules |
+| Data | Modifies core entity structure |
+| Integration | Changes external API contracts |
+| Process | Alters critical business flow |
+| State | Modifies entity state machine |
+
+### Step 6: Recommend Workflow Path
+
+Based on assessment results, recommend the appropriate next step:
+
+| Assessment Result | Recommended Path |
+|-------------------|-----------------|
+| 1 module, low risk, clear domain | Simple PRD (skip ISA-95 modeling) |
+| 2+ modules, medium risk | Full requirement-analysis with ISA-95 modeling |
+| Cross-module, high risk | Full requirement-analysis with ISA-95 modeling + Master-Sub PRD |
+| Configuration only | Direct implementation, PRD optional |
+
+### Step 7: Generate Assessment Report
+
+## Assessment Report Template
+
+```markdown
+# Requirement Assessment Report
+
+## Requirement Summary
+- **Description**: [Brief description]
+- **Source**: [Who requested / Which scenario]
+
+## Assessment Result
+
+### Change Type
+[ ] New Feature  [ ] Modification  [ ] Mixed  [ ] Cross-module  [ ] Configuration
+
+### Impact Scope
+| Module | Impact Type | Evidence |
+|--------|-------------|----------|
+| {Module A} | Direct | [from system-overview / graph query] |
+| {Module B} | Indirect | [upstream dependency via graph] |
+
+### Risk Level
+[ ] Low  [ ] Medium  [ ] High
+
+**Risk Factors**:
+- [List specific risks with evidence]
+
+### Recommended Workflow
+- [ ] Simple PRD (speccrew-pm-requirement-analysis, simple path)
+- [ ] Full ISA-95 Modeling + PRD (speccrew-pm-requirement-analysis, complex path)
+- [ ] Full ISA-95 Modeling + Master-Sub PRD (complex path, multi-module)
+- [ ] Configuration change only
+
+### Key Findings from Graph Analysis
+- [Cross-module dependencies discovered]
+- [Upstream/downstream impacts identified]
+
+### Related Documentation
+- [Links to relevant module docs and graph nodes]
+```
+
+## Quick Reference
+
+### Change Type Quick Guide
+
+| Scenario | Change Type | Example |
+|----------|-------------|---------|
+| New entity + new process | New Feature | Add "Refund" entity and refund process |
+| Existing entity, new attribute | Modification | Add "priority" field to Order |
+| Existing entity, new process step | Mixed | Add "approval" step to existing order flow |
+| Changes module interface | Cross-module | Order module needs new API from Inventory |
+| Toggle/feature flag | Configuration | Enable/disable feature per tenant |
+
+## Checklist
+
+- [ ] Requirement understood and categorized
+- [ ] System overview and related module overviews loaded
+- [ ] Knowledge graph queried for cross-module dependencies
+- [ ] Change type determined
+- [ ] Impact scope mapped (direct + indirect with graph evidence)
+- [ ] Risk level assessed with specific factors
+- [ ] Workflow path recommended
+- [ ] Assessment report generated
+