speccrew 0.1.0

package/.speccrew/skills/speccrew-fd-feature-design/templates/FEATURE-SPEC-TEMPLATE.md

@@ -0,0 +1,387 @@
+# Feature Specification - [Feature Name]
+
+> **Applicable Scenario**: System feature specification for a single feature or module
+> **Target Audience**: speccrew-feature-designer, speccrew-designer, speccrew-dev
+> **Source PRD**: [Link to PRD document]
+
+---
+
+## 1. Overview
+
+### 1.1 Basic Information
+
+| Item | Description |
+|------|-------------|
+| Feature Name | {Feature Name} |
+| Module | {Module Name} |
+| Core Function | {1-3 sentences describing core feature value} |
+| Target Users | {Describe target user groups} |
+| Applicable Scenario | {Describe core applicable business scenarios} |
+
+### 1.2 Feature Scope
+
+<!-- AI-NOTE: Check all items that this specification covers -->
+
+- [ ] {Function 1} - Frontend prototype + Interaction flow + Backend interface + Data definition
+- [ ] {Function 2} - Frontend prototype + Interaction flow + Backend interface + Data definition
+- [ ] {Function 3} - Frontend prototype + Interaction flow + Backend interface + Data definition
+
+### 1.3 Relationship to Existing System
+
+| Module | Relationship Type | Description |
+|--------|-------------------|-------------|
+| {Module A} | EXISTING | {This module already exists, this feature reads data from it} |
+| {Module B} | MODIFIED | {This module will be modified to support new functionality} |
+| {Module C} | NEW | {This is a new module created for this feature} |
+
+---
+
+## 2. Function Details
+
+<!-- AI-NOTE: Repeat Section 2.N for each function in the feature. Each function should include: frontend prototype, interaction flow, backend interface, and data definition. -->
+
+### 2.1 Function: {Function Name}
+
+#### 2.1.1 Frontend Prototype
+
+<!-- AI-NOTE: Use ASCII wireframes to show the UI layout. Choose the appropriate pattern below based on the interface type. -->
+
+**Pattern A: List Page**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ [Page Title] {e.g., Product Management List}                │
+├─────────────────────────────────────────────────────────────┤
+│ ┌─────────────┬─────────────┬─────────────┬─────────────┐  │
+│ │ Filter Area │ □ Checkbox  │ Input □     │ Dropdown ▼  │  │
+│ │             │ Keyword:____|____________ │ Status:_____▼│  │
+│ │             │ [Query]     [Reset]  [Add]                 │  │
+│ └─────────────┴─────────────┴─────────────┴─────────────┘  │
+│                                                             │
+│ ┌─────────────────────────────────────────────────────────┐ │
+│ │ No.  │ Field 1 │ Field 2 │ Field 3 │ Actions         │ │
+│ ├──────┼─────────┼─────────┼─────────┼─────────────────┤ │
+│ │ 1    │ {Value} │ {Value} │ {Value} │ [Edit][Delete]  │ │
+│ │ 2    │ {Value} │ {Value} │ {Value} │ [Edit][Delete]  │ │
+│ │ ...  │ ...     │ ...     │ ...     │ ...             │ │
+│ └──────┴─────────┴─────────┴─────────┴─────────────────┘ │
+│                                                             │
+│ ┌─────────────────────────────────────────────────────────┐ │
+│ │ Pagination: Total {X} records  Page [1][2][3]  {X}/page ▼│ │
+│ └─────────────────────────────────────────────────────────┘ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Pattern B: Form Page**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ [Page Title] {e.g., Add Product}                            │
+├─────────────────────────────────────────────────────────────┤
+│ ┌─────────────────────────────────────────────────────────┐ │
+│ │ Basic Information Area                                    │ │
+│ │ ┌─────────────┬───────────────────────────────────────┐ │ │
+│ │ │ Label       │ Input/Select                           │ │ │
+│ │ │ Product:    │ ____|__________________________________ │ │ │
+│ │ │ Code:       │ ____|__________________________________ │ │ │
+│ │ │ Status:     │ □ Enable  □ Disable                   │ │ │
+│ │ │ Category:   │ ______▼                               │ │ │
+│ │ └─────────────┴───────────────────────────────────────┘ │ │
+│ └─────────────────────────────────────────────────────────┘ │
+│                                                             │
+│ ┌─────────────────────────────────────────────────────────┐ │
+│ │ [Save]                    [Cancel]                       │ │
+│ └─────────────────────────────────────────────────────────┘ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Pattern C: Modal/Dialog**
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│ ┌─────────────────────────────────────────────────────────┐ │
+│ │ [Modal Title] {e.g., Delete Confirmation}               │ │
+│ ├─────────────────────────────────────────────────────────┤ │
+│ │                                                         │ │
+│ │ Message: {e.g., Are you sure to delete this product?    │ │
+│ │           This action cannot be undone!}                │ │
+│ │                                                         │ │
+│ ├─────────────────────────────────────────────────────────┤ │
+│ │            [Cancel]        [Confirm]                     │ │
+│ └─────────────────────────────────────────────────────────┘ │
+└─────────────────────────────────────────────────────────────┘
+```
+
+**Interface Element Description:**
+
+| Area | Element | Type | Description | Interaction |
+|------|---------|------|-------------|-------------|
+| {Area Name} | {Element Name} | {Input/Button/Link/etc} | {Description of purpose} | {Click/Blur/Change behavior} |
+| {Area Name} | {Element Name} | {Type} | {Description} | {Interaction} |
+
+#### 2.1.2 Interaction Flow
+
+<!-- AI-NOTE: Use Mermaid sequenceDiagram to show the flow: User → Frontend → Backend API → Data Store. NO style definitions allowed. NO HTML tags. -->
+
+```mermaid
+sequenceDiagram
+    actor U as User
+    participant F as Frontend
+    participant A as API
+    participant B as Business Logic
+    participant D as Data Store
+    
+    U->>F: 1. {User action, e.g., Click Add button}
+    F->>F: 2. {Frontend processing, e.g., Open form}
+    U->>F: 3. {User input, e.g., Fill form data}
+    U->>F: 4. {User action, e.g., Click Save}
+    F->>F: 5. {Frontend validation}
+    
+    alt Validation passed
+        F->>A: 6. {API call, e.g., POST /api/resource}
+        A->>B: 7. {Business validation}
+        
+        alt Business validation passed
+            B->>D: 8. {Data operation, e.g., Save data}
+            D-->>B: 9. {Return result}
+            B-->>A: 10. {Return success}
+            A-->>F: 11. {Return success response}
+            F->>F: 12. {UI update, e.g., Show success message}
+            F->>U: 13. {Final state, e.g., Return to list}
+        else Business validation failed
+            B-->>A: {Return error}
+            A-->>F: {Return error response}
+            F->>U: {Show error message}
+        end
+    else Validation failed
+        F->>U: {Show validation error}
+    end
+```
+
+**Interaction Rules:**
+
+| Trigger | Behavior | API Called | Exception Handling |
+|---------|----------|------------|-------------------|
+| {Trigger event} | {Behavior description} | {API name or -} | {Exception handling} |
+| {Trigger} | {Behavior} | {API} | {Exception} |
+
+#### 2.1.3 Backend Interface
+
+**Interface List:**
+
+| Interface Name | Method | Path Pattern | Description | Caller |
+|----------------|--------|--------------|-------------|--------|
+| {Interface Name} | GET/POST/PUT/DELETE | {/api/path/pattern} | {Description} | {Frontend/Other} |
+| {Interface Name} | {Method} | {Path} | {Description} | {Caller} |
+
+**Processing Logic:**
+
+<!-- AI-NOTE: Use Mermaid flowchart TD to show the processing logic for each core interface. Show: business validation → data operation → response. NO style definitions allowed. -->
+
+```mermaid
+flowchart TD
+    Start[Request Received] --> Validation{Business Validation}
+    
+    Validation -->|Failed| ValidationError[Return Validation Error]
+    ValidationError --> End1[End]
+    
+    Validation -->|Passed| CheckPermission{Permission Check}
+    
+    CheckPermission -->|Failed| PermissionError[Return Permission Error]
+    PermissionError --> End2[End]
+    
+    CheckPermission -->|Passed| DataOperation[Execute Data Operation]
+    
+    DataOperation -->|Failed| OperationError[Return Operation Error]
+    OperationError --> End3[End]
+    
+    DataOperation -->|Success| BuildResponse[Build Success Response]
+    BuildResponse --> End4[End]
+```
+
+**Data Access:**
+
+| Operation | Data Structure | Access Type | Description |
+|-----------|----------------|-------------|-------------|
+| {e.g., Query list} | {Structure name} | Read | {Description of access} |
+| {e.g., Create record} | {Structure name} | Create | {Description} |
+| {e.g., Update record} | {Structure name} | Write | {Description} |
+
+#### 2.1.4 Data Definition
+
+**Fields:**
+
+| Field Name | Field Type | Data Format | Constraint Rules | New/Existing | Remarks |
+|------------|------------|-------------|------------------|--------------|---------|
+| {Field Name} | String/Number/Boolean/Date/Enum | {e.g., length ≤32, phone format} | {Required/Optional, Unique, Default value} | NEW/EXISTING | {Additional notes} |
+| {Field Name} | {Type} | {Format} | {Constraints} | NEW/EXISTING | {Remarks} |
+
+**Data Source:**
+
+| Field Name | Data Source | Update Timing | Description |
+|------------|-------------|---------------|-------------|
+| {Field Name} | User input | On form submission | {Description} |
+| {Field Name} | System generated | On record creation | {e.g., Auto-generated ID} |
+| {Field Name} | Reference from {source} | {Timing} | {Description} |
+
+---
+
+### 2.2 Function: {Function Name}
+
+<!-- AI-NOTE: Repeat the same structure as 2.1 for each additional function -->
+
+#### 2.2.1 Frontend Prototype
+
+{ASCII wireframe and element description}
+
+#### 2.2.2 Interaction Flow
+
+{Mermaid sequenceDiagram and interaction rules}
+
+#### 2.2.3 Backend Interface
+
+{Interface list, processing logic flowchart, data access}
+
+#### 2.2.4 Data Definition
+
+{Fields and data source}
+
+---
+
+## 3. Cross-Function Concerns
+
+### 3.1 Shared Data Structures
+
+<!-- AI-NOTE: List data structures used across multiple functions -->
+
+| Structure Name | Used By Functions | Description |
+|----------------|-------------------|-------------|
+| {Structure Name} | {Function 1}, {Function 2} | {Description} |
+| {Structure Name} | {Functions} | {Description} |
+
+### 3.2 Cross-Function Flows
+
+<!-- AI-NOTE: Use Mermaid sequenceDiagram for flows that span multiple functions. NO style definitions. NO HTML tags. -->
+
+```mermaid
+sequenceDiagram
+    actor U as User
+    participant F1 as Function A Frontend
+    participant A1 as Function A API
+    participant F2 as Function B Frontend
+    participant A2 as Function B API
+    participant D as Data Store
+    
+    U->>F1: Action in Function A
+    F1->>A1: API call
+    A1->>D: Data operation
+    A1-->>F1: Response
+    F1->>F2: Navigate to Function B
+    F2->>A2: Load related data
+    A2->>D: Query data
+    A2-->>F2: Return data
+    F2->>U: Display Function B
+```
+
+---
+
+## 4. Business Rules & Constraints
+
+### 4.1 Permission Rules
+
+| Operation | Permission Requirement | No Permission Handling |
+|-----------|----------------------|----------------------|
+| {Operation name} | {Role/Permission required} | {How to handle - hide button, show error, etc.} |
+| {Operation} | {Requirement} | {Handling} |
+
+### 4.2 Business Logic Rules
+
+<!-- AI-NOTE: Numbered list of business rules -->
+
+1. **{Rule Name}**: {Detailed description of the rule}
+2. **{Rule Name}**: {Detailed description}
+3. **{Rule Name}**: {Detailed description}
+
+### 4.3 Validation Rules
+
+| Scenario | Rule | Prompt Message | Validation Timing |
+|----------|------|----------------|-------------------|
+| {Scenario} | {Validation rule} | {Error message to show} | {Frontend/Backend/Both} |
+| {Scenario} | {Rule} | {Message} | {Timing} |
+
+---
+
+## 5. API Contract Summary
+
+### 5.1 Complete API List
+
+| API Name | Method | Path | Description | Related Function |
+|----------|--------|------|-------------|------------------|
+| {API Name} | GET/POST/PUT/DELETE | {/api/path} | {Description} | {Function Name} |
+| {API Name} | {Method} | {Path} | {Description} | {Function Name} |
+
+### 5.2 Shared Response Format
+
+<!-- AI-NOTE: Standard response JSON structure used across all APIs in this feature -->
+
+**Success Response:**
+
+```json
+{
+  "code": 0,
+  "message": "success",
+  "data": {
+    "{field1}": "{value1}",
+    "{field2}": "{value2}"
+  }
+}
+```
+
+**Error Response:**
+
+```json
+{
+  "code": {error_code},
+  "message": "{error_message}",
+  "data": null
+}
+```
+
+### 5.3 Common Error Codes
+
+| Error Code | HTTP Status | Description |
+|------------|-------------|-------------|
+| {Code} | {Status} | {Description} |
+| {Code} | {Status} | {Description} |
+
+---
+
+## 6. Notes
+
+### 6.1 Pending Confirmations
+
+<!-- AI-NOTE: Checklist of items needing confirmation from stakeholders -->
+
+- [ ] **{Item 1}**: {Description of what needs confirmation}
+- [ ] **{Item 2}**: {Description}
+
+### 6.2 Assumptions & Dependencies
+
+<!-- AI-NOTE: List assumptions made and external dependencies -->
+
+- **Assumption 1**: {Description of assumption}
+- **Dependency 1**: {External system or module this feature depends on}
+
+### 6.3 Extension Notes
+
+<!-- AI-NOTE: Notes about future iterations or extensions -->
+
+- {Note about potential future enhancements}
+- {Note about scalability considerations}
+
+---
+
+**Document Status:** Draft / In Review / Published
+**Last Updated:** {Date}
+**Source PRD:** [PRD Document](link)
+**Related Module:** [Module Overview](link)

package/.speccrew/skills/speccrew-get-timestamp/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: speccrew-get-timestamp
+description: Get current timestamp in various formats for file naming and logging. Use when generating dated filenames, report timestamps, or any scenario requiring consistent datetime formatting.
+---
+
+# Get Timestamp
+
+Get current timestamp in specified format for consistent datetime handling across all skills.
+
+## User
+
+Any Agent or script requiring timestamp generation
+
+## Input
+
+- `format` (optional): Timestamp format, default is `YYYY-MM-DD-HHmmss`
+  - `YYYY-MM-DD-HHmmss`: Full datetime for filenames (e.g., `2026-03-17-132645`)
+  - `YYYY-MM-DD`: Date only (e.g., `2026-03-17`)
+  - `HHmm`: Time only 24h format (e.g., `1326`)
+  - `ISO`: ISO 8601 format (e.g., `2026-03-17T13:26:45+08:00`)
+
+## Output
+
+- Timestamp string in specified format (printed to stdout)
+
+## Supported Formats
+
+| Format | Description | Example |
+|--------|-------------|---------|
+| `YYYY-MM-DD-HHmmss` | Full datetime for filenames | `2026-03-17-132645` |
+| `YYYY-MM-DD` | Date only | `2026-03-17` |
+| `HHmm` | Time only (24h) | `1326` |
+| `ISO` | ISO 8601 format | `2026-03-17T13:26:45+08:00` |
+
+## Usage
+
+### Method 1: Direct Script Execution (Node.js - Cross Platform)
+
+```bash
+# Node.js (cross-platform, recommended)
+node scripts/get-timestamp.js "YYYY-MM-DD-HHmmss"
+```
+
+### Method 2: Default Format (YYYY-MM-DD-HHmmss)
+
+```bash
+# Without format parameter, returns YYYY-MM-DD-HHmmss
+node scripts/get-timestamp.js
+```
+
+## Integration Examples
+
+### For Report Filenames
+
+```bash
+TIMESTAMP=$(node scripts/get-timestamp.js "YYYY-MM-DD-HHmmss")
+FILENAME="diagnosis-report-${TIMESTAMP}.md"
+# Result: diagnosis-report-2026-03-17-132645.md
+```
+
+### For Archive Naming
+
+```bash
+TIMESTAMP=$(node scripts/get-timestamp.js "YYYY-MM-DD")
+ARCHIVE_NAME="tech-debt-archived-${TIMESTAMP}.md"
+# Result: tech-debt-archived-2026-03-17.md
+```
+
+### For Template Variables
+
+When filling `{{generated_at}}` in templates:
+```bash
+generated_at=$(node scripts/get-timestamp.js "ISO")
+# Result: 2026-03-17T13:26:45+08:00
+```
+
+## Script Location
+
+- **Node.js**: `scripts/get-timestamp.js` (cross-platform, unified implementation)
+

package/.speccrew/skills/speccrew-get-timestamp/scripts/get-timestamp.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+/**
+ * Get current timestamp in specified format
+ * Usage: node get-timestamp.js [format]
+ * Default format: YYYY-MM-DD-HHmmss
+ */
+
+const FORMATS = {
+  'YYYY-MM-DD-HHmmss': () => {
+    const now = new Date();
+    return `${now.getFullYear()}-${String(now.getMonth() + 1).padStart(2, '0')}-${String(now.getDate()).padStart(2, '0')}-${String(now.getHours()).padStart(2, '0')}${String(now.getMinutes()).padStart(2, '0')}${String(now.getSeconds()).padStart(2, '0')}`;
+  },
+  'YYYY-MM-DD': () => {
+    const now = new Date();
+    return `${now.getFullYear()}-${String(now.getMonth() + 1).padStart(2, '0')}-${String(now.getDate()).padStart(2, '0')}`;
+  },
+  'HHmm': () => {
+    const now = new Date();
+    return `${String(now.getHours()).padStart(2, '0')}${String(now.getMinutes()).padStart(2, '0')}`;
+  },
+  'ISO': () => new Date().toISOString()
+};
+
+function getTimestamp(format = 'YYYY-MM-DD-HHmmss') {
+  const formatter = FORMATS[format];
+  if (formatter) {
+    return formatter();
+  }
+  // Default fallback
+  return FORMATS['YYYY-MM-DD-HHmmss']();
+}
+
+// Main execution
+const format = process.argv[2] || 'YYYY-MM-DD-HHmmss';
+console.log(getTimestamp(format));