musubix 3.3.8 → 3.3.9

package/.github/prompts/sdd-implement.prompt.md

@@ -1,387 +0,0 @@
-# MUSUBIX Implement Command
-
-Execute implementation tasks for a feature following Test-First principles.
-
----
-
-## Instructions for AI Agent
-
-You are executing the `musubix implement [feature-name]` command to implement a feature following SDD workflow.
-
-### Command Format
-
-```bash
-npx musubix implement authentication
-npx musubix codegen generate design.md
-```
-
-### Your Task
-
-Implement the feature by executing tasks from the task breakdown document, following Test-First principles (Article III) and constitutional governance.
-
----
-
-## Process
-
-### 1. Read All Context
-
-**CRITICAL**: Read these files first:
-
-```bash
-# Task Breakdown
-storage/specs/TSK-{{FEATURE}}-001.md
-
-# Design
-storage/specs/DES-{{FEATURE}}-001.md
-
-# Requirements
-storage/specs/REQ-{{FEATURE}}-001.md
-
-# Steering Context
-steering/structure.ja.md
-steering/tech.ja.md
-steering/product.ja.md
-```
-
----
-
-### 2. Verify Prerequisites
-
-**Check task breakdown exists**:
-
-```markdown
-❌ **Error**: Task breakdown not found
-
-Expected: storage/specs/TSK-{{FEATURE}}-001.md
-
-Please run `npx musubix tasks generate` first.
-```
-
----
-
-### 3. Use Todo Tracking
-
-Track implementation progress:
-
-```markdown
-1. TSK-001: Set Up Package Structure
-2. TSK-002: Write Tests (RED)
-3. TSK-003: Implement Code (GREEN)
-4. TSK-004: Refactor (BLUE)
-5. TSK-005: CLI Interface (Article II)
-6. TSK-006: MCP Tool (if needed)
-```
-
----
-
-### 4. Execute Tasks in Order
-
-#### TSK-001: Set Up Package Structure
-
-**Create structure in appropriate package**:
-
-```
-packages/core/src/{{feature}}/
-├── index.ts          # Public API exports
-├── service.ts        # Business logic
-├── types.ts          # TypeScript types
-└── errors.ts         # Custom errors
-
-packages/core/__tests__/
-├── unit/
-│   └── {{feature}}.test.ts
-└── integration/
-    └── {{feature}}.integration.test.ts
-```
-
-**Create public API**:
-
-```typescript
-// packages/core/src/{{feature}}/index.ts
-
-/**
- * {{Feature}} Module
- * 
- * @see REQ-{{COMPONENT}}-001
- * @see DES-{{FEATURE}}-001
- */
-
-export { {{Feature}}Service } from './service.js';
-export type { {{Feature}}Options, {{Feature}}Result } from './types.js';
-```
-
-**Create types**:
-
-```typescript
-// packages/core/src/{{feature}}/types.ts
-
-/**
- * @see REQ-{{COMPONENT}}-001
- */
-export interface {{Feature}}Options {
-  input: string;
-  output?: string;
-}
-
-export interface {{Feature}}Result {
-  success: boolean;
-  data?: unknown;
-  error?: string;
-}
-```
-
----
-
-#### TSK-002: Write Tests (RED Phase) 🔴
-
-**CRITICAL (Article III)**: Tests BEFORE implementation.
-
-```typescript
-// packages/core/__tests__/unit/{{feature}}.test.ts
-
-import { describe, it, expect, beforeEach } from 'vitest';
-import { {{Feature}}Service } from '../../src/{{feature}}/index.js';
-
-describe('REQ-{{COMPONENT}}-001: {{Requirement Title}}', () => {
-  let service: {{Feature}}Service;
-
-  beforeEach(() => {
-    service = new {{Feature}}Service();
-  });
-
-  // Acceptance Criterion 1
-  it('should [acceptance criterion 1]', async () => {
-    // Arrange
-    const input = { /* ... */ };
-
-    // Act
-    const result = await service.process(input);
-
-    // Assert
-    expect(result.success).toBe(true);
-  });
-
-  // Acceptance Criterion 2
-  it('should handle errors gracefully', async () => {
-    // Arrange
-    const invalidInput = { /* ... */ };
-
-    // Act & Assert
-    await expect(service.process(invalidInput)).rejects.toThrow();
-  });
-});
-```
-
-**Run tests** (should FAIL):
-
-```bash
-npm test packages/core/__tests__/unit/{{feature}}.test.ts
-# Expected: Tests FAIL (service.ts doesn't exist yet)
-```
-
----
-
-#### TSK-003: Implement Code (GREEN Phase) 💚
-
-**Create minimal implementation**:
-
-```typescript
-// packages/core/src/{{feature}}/service.ts
-
-import type { {{Feature}}Options, {{Feature}}Result } from './types.js';
-import { ValidationError } from './errors.js';
-
-/**
- * {{Feature}} Service
- * 
- * @see REQ-{{COMPONENT}}-001
- * @see DES-{{FEATURE}}-001
- */
-export class {{Feature}}Service {
-  /**
-   * Process {{feature}} request
-   * 
-   * Acceptance Criteria:
-   * - [Criterion 1]
-   * - [Criterion 2]
-   */
-  async process(options: {{Feature}}Options): Promise<{{Feature}}Result> {
-    // Validate input
-    this.validate(options);
-
-    // Process
-    const result = await this.execute(options);
-
-    return {
-      success: true,
-      data: result,
-    };
-  }
-
-  private validate(options: {{Feature}}Options): void {
-    if (!options.input) {
-      throw new ValidationError('input is required');
-    }
-  }
-
-  private async execute(options: {{Feature}}Options): Promise<unknown> {
-    // Minimal implementation
-    return { processed: true };
-  }
-}
-```
-
-**Run tests** (should PASS):
-
-```bash
-npm test packages/core/__tests__/unit/{{feature}}.test.ts
-# Expected: Tests PASS ✅
-```
-
----
-
-#### TSK-004: Refactor (BLUE Phase) 💙
-
-**Improve code while keeping tests green**:
-
-- Extract validators
-- Add proper error handling
-- Apply SOLID principles
-- Improve naming
-
-```bash
-npm test packages/core/__tests__/unit/{{feature}}.test.ts
-# Expected: Tests still PASS ✅
-```
-
----
-
-#### TSK-005: CLI Command (Article II)
-
-**Create CLI command**:
-
-```typescript
-// packages/core/src/cli/commands/{{feature}}.ts
-
-import type { Command } from 'commander';
-import { {{Feature}}Service } from '../../{{feature}}/index.js';
-
-/**
- * Register {{feature}} command
- * 
- * @see REQ-CLI-001
- * @see Article II: CLI Interface Mandate
- */
-export function register{{Feature}}Command(program: Command): void {
-  program
-    .command('{{feature}}')
-    .description('{{Feature description}}')
-    .argument('<input>', 'Input file or value')
-    .option('-o, --output <path>', 'Output path')
-    .option('--json', 'Output as JSON')
-    .action(async (input, options) => {
-      const service = new {{Feature}}Service();
-      const result = await service.process({ input, ...options });
-      
-      if (options.json) {
-        console.log(JSON.stringify(result, null, 2));
-      } else {
-        console.log(result);
-      }
-    });
-}
-```
-
-**Register in CLI**:
-
-```typescript
-// packages/core/src/cli/index.ts
-
-import { register{{Feature}}Command } from './commands/{{feature}}.js';
-
-// In setupCommands function:
-register{{Feature}}Command(program);
-```
-
----
-
-#### TSK-006: MCP Tool (if needed)
-
-**Create MCP tool**:
-
-```typescript
-// packages/mcp-server/src/tools/{{feature}}-tools.ts
-
-import type { ToolDefinition, ToolResult } from '../types.js';
-
-/**
- * {{Feature}} Tool
- * 
- * @see REQ-MCP-001
- */
-export const {{feature}}Tool: ToolDefinition = {
-  name: 'sdd_{{feature}}',
-  description: '{{Feature description}}',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      input: {
-        type: 'string',
-        description: 'Input value',
-      },
-    },
-    required: ['input'],
-  },
-  handler: async (args): Promise<ToolResult> => {
-    const { input } = args as { input: string };
-    
-    // Implementation
-    return {
-      content: [{ type: 'text', text: `Processed: ${input}` }],
-    };
-  },
-};
-```
-
----
-
-### 5. Validation Commands
-
-```bash
-# Run all tests
-npm test
-
-# Type check
-npm run typecheck
-
-# Lint
-npm run lint
-
-# Build
-npm run build
-```
-
----
-
-### 6. Git Workflow
-
-```bash
-# RED phase
-git add packages/core/__tests__/
-git commit -m "test: add failing tests for REQ-{{COMPONENT}}-001"
-
-# GREEN phase
-git add packages/core/src/{{feature}}/
-git commit -m "feat: implement REQ-{{COMPONENT}}-001"
-
-# BLUE phase
-git commit -m "refactor: improve {{feature}} implementation"
-
-# CLI
-git commit -m "feat: add {{feature}} CLI command (Article II)"
-```
-
----
-
-**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
-**Version**: 1.0.0

package/.github/prompts/sdd-requirements.prompt.md

@@ -1,193 +0,0 @@
-# MUSUBIX Requirements Command
-
-Create EARS-format requirements specification through interactive dialogue.
-
----
-
-## Instructions for AI Agent
-
-You are executing the `musubix requirements [feature-name]` command to create a requirements specification.
-
-### Command Format
-
-```bash
-npx musubix requirements analyze authentication
-npx musubix requirements validate spec.md
-npx musubix requirements map spec.md
-```
-
-### Your Task
-
-**CRITICAL**: Before generating requirements, engage in an interactive 1-on-1 dialogue with the user to uncover the TRUE PURPOSE behind their request.
-
-### Output Directory
-
-**Requirements documents are saved to**: `storage/specs/`
-
-- File: `storage/specs/REQ-{{FEATURE}}-001.md`
-
----
-
-## Process
-
-### 1. Read Steering Context (Article VI)
-
-**IMPORTANT**: Before starting, read steering files to understand project context:
-
-```bash
-# Read these files first
-steering/product.ja.md      # Business context, users, goals
-steering/structure.ja.md    # Architecture patterns
-steering/tech.ja.md         # Technology stack
-```
-
-**Extract**:
-
-- Target users
-- Product goals
-- Existing architecture patterns
-- Technology constraints (TypeScript, Node.js 20+)
-
----
-
-### 2. Interactive True Purpose Discovery
-
-**CRITICAL RULE**: Ask ONE question at a time, then STOP and WAIT.
-
-#### Question Sequence
-
-**Turn 1**: WHY question
-```
-この機能で解決したい『本当の課題』は何ですか？
-```
-
-**Turn 2**: WHO question
-```
-この機能を最も必要としているのは誰ですか？
-```
-
-**Turn 3**: WHAT-IF question
-```
-もしこの機能が完璧に動作したら、何が変わりますか？
-```
-
-**Turn 4**: CONSTRAINT question
-```
-この機能で『絶対にやってはいけないこと』はありますか？
-```
-
-**Turn 5**: SUCCESS CRITERIA question
-```
-この機能が『成功した』と言えるのはどんな状態ですか？
-```
-
----
-
-### 3. Apply EARS Format (Article IV)
-
-**CRITICAL**: All requirements MUST use one of 5 EARS patterns.
-
-| Pattern | Syntax | Usage |
-|---------|--------|-------|
-| **Ubiquitous** | `The [system] SHALL [action]` | Always-active features |
-| **Event-driven** | `WHEN [event], the [system] SHALL [action]` | User action triggers |
-| **State-driven** | `WHILE [state], the [system] SHALL [action]` | Continuous conditions |
-| **Unwanted** | `IF [error], THEN the [system] SHALL [action]` | Error handling |
-| **Optional** | `WHERE [feature], the [system] SHALL [action]` | Feature flags |
-
----
-
-### 4. Generate Requirements Document
-
-**Template**:
-
-```markdown
-# Requirements Specification: {{FEATURE_NAME}}
-
-**Document ID**: REQ-{{FEATURE}}-001
-**Version**: 1.0.0
-**Date**: {{DATE}}
-**Status**: Draft
-
-## Overview
-
-- **Purpose**: [True purpose discovered through dialogue]
-- **Scope**: [In/Out scope]
-- **Package**: packages/core/ or packages/mcp-server/ or packages/yata-client/
-
-## Stakeholders
-
-| Role | Description | Needs |
-|------|-------------|-------|
-| Developer | Uses MUSUBIX CLI | Efficient workflow |
-
-## Functional Requirements
-
-### REQ-{{COMPONENT}}-001: [Title]
-
-**EARS Pattern**: [Pattern name]
-
-> [EARS statement]
-
-**Priority**: P0/P1/P2/P3
-**Acceptance Criteria**:
-- [ ] [Criterion 1]
-- [ ] [Criterion 2]
-
-**Traceability**: → DES-{{FEATURE}}-001
-
-## Non-Functional Requirements
-
-### REQ-PERF-001: Performance
-The system SHALL respond within 200ms for 95% of requests.
-
-### REQ-SEC-001: Security
-The system SHALL prevent OWASP Top 10 vulnerabilities.
-
-## Traceability Matrix
-
-| Requirement | Design | Task | Test |
-|-------------|--------|------|------|
-| REQ-{{COMPONENT}}-001 | DES-{{FEATURE}}-001 | TSK-{{FEATURE}}-001 | TBD |
-```
-
----
-
-### 5. Requirements ID Format
-
-**Format**: `REQ-[COMPONENT]-[NUMBER]`
-
-**Examples**:
-- `REQ-CLI-001` - CLI component
-- `REQ-MCP-001` - MCP Server component
-- `REQ-YATA-001` - YATA Client component
-- `REQ-CORE-001` - Core library component
-
----
-
-### 6. Quality Checklist
-
-Each requirement MUST have:
-
-- [ ] Unique ID (REQ-COMPONENT-NNN)
-- [ ] EARS pattern (one of 5)
-- [ ] Clear SHALL statement
-- [ ] Testable acceptance criteria
-- [ ] Priority (P0/P1/P2/P3)
-- [ ] Status (Draft initially)
-
----
-
-### 7. MCP Tool Integration
-
-Use MUSUBIX MCP tools:
-
-```
-sdd_create_requirements - Create requirements document
-sdd_validate_requirements - Validate EARS patterns
-```
-
----
-
-**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
-**Version**: 1.0.0

package/.github/prompts/sdd-review.prompt.md

@@ -1,155 +0,0 @@
-# MUSUBIX Code Review Command
-
-Perform comprehensive code review with SOLID principles and quality checks.
-
----
-
-## Instructions for AI Agent
-
-You are executing the `musubix review [feature-name]` command to perform code review.
-
-### Command Format
-
-```bash
-npx musubix codegen analyze <file>
-npx musubix trace validate
-```
-
-### Your Task
-
-Perform comprehensive code review focusing on:
-
-1. SOLID Principles Compliance
-2. Code Quality Metrics
-3. Design Pattern Usage
-4. Traceability Verification
-5. Best Practices Adherence
-
----
-
-## Process
-
-### 1. Read Source Code and Context
-
-```bash
-# Source Code
-packages/core/src/{{feature}}/**/*.ts
-packages/mcp-server/src/tools/**/*.ts
-
-# Design Documentation
-storage/specs/DES-{{FEATURE}}-001.md
-
-# Steering Context
-steering/structure.ja.md
-steering/tech.ja.md
-steering/rules/constitution.md
-```
-
-### 2. SOLID Principles Check
-
-Review each file for:
-
-| Principle | Check |
-|-----------|-------|
-| **S**ingle Responsibility | 1つのクラス/関数は1つの責務のみ |
-| **O**pen/Closed | 拡張に開き、修正に閉じている |
-| **L**iskov Substitution | 派生クラスは基底クラスと置換可能 |
-| **I**nterface Segregation | クライアント固有のインターフェース |
-| **D**ependency Inversion | 抽象に依存、具象に依存しない |
-
-### 3. Code Quality Metrics
-
-Analyze:
-
-- **Cyclomatic Complexity**: 関数あたり10以下
-- **Lines per Function**: 50行以下
-- **Lines per File**: 300行以下
-- **Nesting Depth**: 3レベル以下
-- **Parameter Count**: 5個以下
-
-### 4. Design Pattern Review
-
-Check for:
-
-- [ ] Repository Pattern (データアクセス)
-- [ ] Service Layer (ビジネスロジック)
-- [ ] Factory Pattern (オブジェクト生成)
-- [ ] Value Objects (ドメイン概念)
-- [ ] Result Type (エラーハンドリング)
-
-### 5. Best Practices Check
-
-| カテゴリ | チェック項目 |
-|---------|-------------|
-| 命名規則 | PascalCase (型), camelCase (変数/関数), UPPER_CASE (定数) |
-| TypeScript | strict mode, 明示的な型定義, any禁止 |
-| エラー処理 | Result<T, E>パターン, 適切なエラーメッセージ |
-| コメント | JSDoc形式, 複雑なロジックの説明 |
-| インポート | 絶対パス, 循環参照なし |
-
----
-
-## Output Format
-
-```markdown
-# Code Review Report: {{FEATURE}}
-
-## Summary
-- **Overall Score**: A/B/C/D/F
-- **Files Reviewed**: X files
-- **Issues Found**: X critical, X warnings, X suggestions
-
-## SOLID Compliance
-| Principle | Status | Notes |
-|-----------|--------|-------|
-| SRP | ✅/⚠️/❌ | ... |
-| OCP | ✅/⚠️/❌ | ... |
-| LSP | ✅/⚠️/❌ | ... |
-| ISP | ✅/⚠️/❌ | ... |
-| DIP | ✅/⚠️/❌ | ... |
-
-## Quality Metrics
-| Metric | Value | Status |
-|--------|-------|--------|
-| Avg Cyclomatic Complexity | X | ✅/⚠️/❌ |
-| Max Lines per Function | X | ✅/⚠️/❌ |
-| Max Nesting Depth | X | ✅/⚠️/❌ |
-
-## Issues
-
-### Critical (Must Fix)
-1. [FILE:LINE] Description
-
-### Warnings (Should Fix)
-1. [FILE:LINE] Description
-
-### Suggestions (Nice to Have)
-1. [FILE:LINE] Description
-
-## Recommendations
-1. ...
-2. ...
-```
-
----
-
-## Traceability
-
-This skill implements:
-- **Article III**: Test-First Imperative (コードレビューによる品質確保)
-- **Article VII**: Simplicity Gate (コードの複雑性チェック)
-
----
-
-## Related Commands
-
-```bash
-# Static analysis
-npx musubix codegen analyze <file>
-
-# Traceability validation
-npx musubix trace validate
-
-# Security scanning
-npx musubix codegen security <path>
-```