musubix 1.0.1 → 1.0.2

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

@@ -0,0 +1,193 @@
+# 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-steering.prompt.md

@@ -0,0 +1,269 @@
+# MUSUBIX Steering Command
+
+Generate or update project memory (steering context).
+
+---
+
+## Instructions for AI Agent
+
+You are executing the `musubix steering` command to generate or update the project's steering context.
+
+### What is Steering?
+
+Steering provides **project memory** for AI agents. It consists of core files that document:
+
+1. **structure.ja.md** - Architecture patterns, directory structure
+2. **tech.ja.md** - Technology stack, frameworks
+3. **product.ja.md** - Business context, product goals
+4. **rules/constitution.md** - 9 Constitutional Articles
+
+### Your Task
+
+**Mode Detection**:
+
+1. **Bootstrap Mode** - No steering files exist → Generate initial files
+2. **Sync Mode** - Files exist, codebase changed → Update files
+3. **Review Mode** - User wants to review → Present and suggest improvements
+
+---
+
+## Mode 1: Bootstrap (First Time)
+
+### Detection
+
+- `steering/` directory doesn't exist OR
+- Core files missing
+
+### Steps
+
+1. **Analyze Codebase**:
+   - Directory structure
+   - Package.json files
+   - TypeScript configuration
+   - Test framework (Vitest)
+
+2. **Generate Steering Files**:
+
+**Create `steering/structure.ja.md`**:
+
+```markdown
+# Project Structure
+
+**Project**: MUSUBIX
+**Last Updated**: {{DATE}}
+
+## Architecture Pattern
+
+**Primary Pattern**: Monorepo (npm workspaces)
+
+## Package Structure
+
+\`\`\`
+packages/
+├── core/           # @nahisaho/musubix-core
+├── mcp-server/     # @nahisaho/musubix-mcp-server
+└── yata-client/    # @nahisaho/musubix-yata-client
+\`\`\`
+
+## Core Package Modules
+
+\`\`\`
+packages/core/src/
+├── auth/           # Authentication
+├── cli/            # CLI Interface (Article II)
+├── codegen/        # Code Generation
+├── design/         # Design Patterns
+├── error/          # Error Handling
+├── explanation/    # Explanations
+├── requirements/   # Requirements Analysis
+├── traceability/   # Traceability
+├── types/          # Type Definitions
+├── utils/          # Utilities
+└── validators/     # EARS Validation
+\`\`\`
+
+## Naming Conventions
+
+- Files: `kebab-case.ts`
+- Classes: `PascalCase`
+- Functions: `camelCase`
+- Constants: `SCREAMING_SNAKE_CASE`
+```
+
+**Create `steering/tech.ja.md`**:
+
+```markdown
+# Technology Stack
+
+**Project**: MUSUBIX
+**Last Updated**: {{DATE}}
+
+## Core Technologies
+
+| Category | Technology | Version |
+|----------|------------|---------|
+| Language | TypeScript | ^5.3 |
+| Runtime | Node.js | >= 20.0.0 |
+| Package Manager | npm | >= 10.0.0 |
+| Build | npm workspaces | - |
+| Test | Vitest | ^1.0.0 |
+| Lint | ESLint | ^8.0.0 |
+
+## Package Dependencies
+
+### @nahisaho/musubix-core
+
+- commander: CLI framework
+- chalk: Terminal styling
+
+### @nahisaho/musubix-mcp-server
+
+- MCP protocol support
+
+### @nahisaho/musubix-yata-client
+
+- Knowledge graph client
+
+## Development Tools
+
+- TypeScript strict mode
+- ESM modules (`"type": "module"`)
+- Vitest for testing
+```
+
+**Create `steering/product.ja.md`**:
+
+```markdown
+# Product Context
+
+**Project**: MUSUBIX
+**Last Updated**: {{DATE}}
+
+## Product Vision
+
+Neuro-Symbolic AI Integration System that combines:
+- **Neural (LLM)**: Creative code generation
+- **Symbolic (YATA)**: Knowledge graph precision
+
+## Target Users
+
+- Software Developers
+- AI/ML Engineers
+- Development Teams
+
+## Core Features
+
+1. EARS Requirements Analysis
+2. C4 Model Design Generation
+3. Test-First Development
+4. Complete Traceability
+5. MCP Server Integration
+```
+
+---
+
+## Mode 2: Sync (Update Existing)
+
+### Detection
+
+- Steering files exist
+- Codebase has changes
+
+### Steps
+
+1. **Compare Current State**:
+   - Read existing steering files
+   - Analyze current codebase
+   - Identify discrepancies
+
+2. **Update Files**:
+   - Add new modules/packages
+   - Update technology versions
+   - Reflect architecture changes
+
+3. **Generate Diff Report**:
+
+```markdown
+## Steering Sync Report
+
+### Changes Detected
+
+| File | Change | Action |
+|------|--------|--------|
+| structure.ja.md | New module: utils/ | Updated |
+| tech.ja.md | Vitest 1.0 → 2.0 | Updated |
+
+### Files Updated
+
+1. `steering/structure.ja.md` - Added utils module
+2. `steering/tech.ja.md` - Updated Vitest version
+```
+
+---
+
+## Mode 3: Review
+
+### Steps
+
+1. **Present Current Steering**:
+   - Show structure.ja.md content
+   - Show tech.ja.md content
+   - Show product.ja.md content
+
+2. **Analyze for Improvements**:
+   - Missing documentation
+   - Outdated information
+   - Inconsistencies
+
+3. **Suggest Improvements**:
+
+```markdown
+## Steering Review
+
+### Current State
+
+✅ structure.ja.md - Complete
+✅ tech.ja.md - Complete
+⚠️ product.ja.md - Missing user personas
+
+### Recommendations
+
+1. Add user personas to product.ja.md
+2. Update tech stack versions
+3. Add ADR index
+```
+
+---
+
+## Constitutional Articles Reference
+
+Always include reference to `steering/rules/constitution.md`:
+
+| Article | Name | Summary |
+|---------|------|---------|
+| I | Library-First | Features in packages/ |
+| II | CLI Interface | CLI for all libraries |
+| III | Test-First | Red-Green-Blue |
+| IV | EARS Format | Requirements syntax |
+| V | Traceability | 100% tracking |
+| VI | Project Memory | Read steering first |
+| VII | Design Patterns | Document patterns |
+| VIII | Decision Records | ADRs for decisions |
+| IX | Quality Gates | Validate phases |
+
+---
+
+## Output
+
+Save steering files to:
+
+- `steering/structure.ja.md`
+- `steering/tech.ja.md`
+- `steering/product.ja.md`
+- `steering/rules/constitution.md`
+- `steering/project.yml`
+
+---
+
+**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
+**Version**: 1.0.0

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

@@ -0,0 +1,255 @@
+# MUSUBIX Tasks Command
+
+Break down design into actionable implementation tasks.
+
+---
+
+## Instructions for AI Agent
+
+You are executing the `musubix tasks [feature-name]` command to create a task breakdown document.
+
+### Command Format
+
+```bash
+npx musubix tasks generate design.md
+```
+
+### Your Task
+
+Generate a comprehensive task breakdown that transforms the design into actionable implementation tasks with full requirements traceability.
+
+---
+
+## Process
+
+### 1. Read Context
+
+**CRITICAL**: Read these files first:
+
+```bash
+# Design and Requirements
+storage/specs/DES-{{FEATURE}}-001.md
+storage/specs/REQ-{{FEATURE}}-001.md
+
+# Steering Context
+steering/structure.ja.md
+steering/tech.ja.md
+steering/product.ja.md
+```
+
+---
+
+### 2. Verify Prerequisites
+
+**Check design file exists**:
+
+```markdown
+❌ **Error**: Design document not found
+
+Expected: storage/specs/DES-{{FEATURE}}-001.md
+
+Please run `npx musubix design generate` first.
+
+Tasks cannot be created without design (Article V: Traceability).
+```
+
+---
+
+### 3. Generate Task Breakdown
+
+**Output**: `storage/specs/TSK-{{FEATURE}}-001.md`
+
+#### Task Structure
+
+```markdown
+### TSK-{{FEATURE}}-NNN: [Task Title]
+
+**Priority**: P0/P1/P2/P3
+**Story Points**: 1/2/3/5/8/13
+**Estimated Hours**: N
+**Status**: Not Started
+
+**Description**:
+[Clear description]
+
+**Requirements Coverage**:
+- REQ-{{COMPONENT}}-NNN: [Requirement title]
+
+**Package**: packages/core/ | packages/mcp-server/ | packages/yata-client/
+
+**Files to Create/Modify**:
+- `packages/core/src/{{feature}}/index.ts`
+- `packages/core/__tests__/unit/{{feature}}.test.ts`
+
+**Acceptance Criteria**:
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+
+**Test-First Checklist** (Article III):
+- [ ] Tests written BEFORE implementation
+- [ ] Red: Failing test committed
+- [ ] Green: Minimal implementation passes
+- [ ] Blue: Refactored with confidence
+
+**Dependencies**:
+- TSK-{{FEATURE}}-NNN: [Dependency]
+```
+
+---
+
+### 4. Task Categories (MUSUBIX-specific)
+
+**P0 Tasks (Critical)**:
+
+1. **TSK-001: Set Up Package Structure**
+   - Create in `packages/{{package}}/src/{{feature}}/`
+   - Follow Article I (Library-First)
+
+2. **TSK-002: Write Tests (RED)**
+   - Location: `packages/{{package}}/__tests__/unit/{{feature}}.test.ts`
+   - Test all acceptance criteria
+
+3. **TSK-003: Implement Code (GREEN)**
+   - Minimal implementation to pass tests
+   - Location: `packages/{{package}}/src/{{feature}}/`
+
+4. **TSK-004: Refactor (BLUE)**
+   - Improve design while tests pass
+   - Apply SOLID principles
+
+5. **TSK-005: Add CLI Command (Article II)**
+   - Location: `packages/core/src/cli/commands/{{feature}}.ts`
+   - Register in `packages/core/src/cli/index.ts`
+
+6. **TSK-006: Add MCP Tool (if needed)**
+   - Location: `packages/mcp-server/src/tools/{{feature}}-tools.ts`
+   - Register in `packages/mcp-server/src/server.ts`
+
+**P1 Tasks (High)**:
+
+7. **TSK-007: Integration Tests**
+   - Location: `packages/{{package}}/__tests__/integration/`
+
+8. **TSK-008: Documentation**
+   - Update `docs/USER-GUIDE.md`
+   - Update `docs/API-REFERENCE.md`
+
+---
+
+### 5. Test-First Mandate (Article III)
+
+For EVERY implementation task, create 3 separate tasks:
+
+```markdown
+### TSK-002: Write Tests for REQ-{{COMPONENT}}-001 (RED) 🔴
+
+**Priority**: P0
+**Story Points**: 2
+
+**Description**:
+Write failing tests for requirement REQ-{{COMPONENT}}-001
+
+**Test File**: `packages/core/__tests__/unit/{{feature}}.test.ts`
+
+**Acceptance Criteria**:
+- [ ] Tests compile successfully
+- [ ] Tests FAIL (no implementation yet)
+- [ ] Tests cover all acceptance criteria
+
+---
+
+### TSK-003: Implement REQ-{{COMPONENT}}-001 (GREEN) 💚
+
+**Priority**: P0
+**Story Points**: 3
+**Depends On**: TSK-002
+
+**Description**:
+Implement minimal code to pass tests
+
+**Acceptance Criteria**:
+- [ ] All tests from TSK-002 pass
+- [ ] No extra functionality added
+
+---
+
+### TSK-004: Refactor REQ-{{COMPONENT}}-001 (BLUE) 💙
+
+**Priority**: P0
+**Story Points**: 2
+**Depends On**: TSK-003
+
+**Description**:
+Refactor while keeping tests green
+
+**Acceptance Criteria**:
+- [ ] All tests still pass
+- [ ] SOLID principles applied
+- [ ] Code quality improved
+```
+
+---
+
+### 6. Task Document Template
+
+```markdown
+# Task Breakdown: {{FEATURE_NAME}}
+
+**Document ID**: TSK-{{FEATURE}}-001
+**Version**: 1.0.0
+**Date**: {{DATE}}
+**Design**: DES-{{FEATURE}}-001
+**Requirements**: REQ-{{FEATURE}}-001
+
+## Summary
+
+| Priority | Count | Story Points |
+|----------|-------|--------------|
+| P0 | X | XX |
+| P1 | X | XX |
+| Total | X | XX |
+
+## Sprint Plan
+
+### Sprint 1 (Week 1)
+- TSK-{{FEATURE}}-001: Setup
+- TSK-{{FEATURE}}-002: Tests (RED)
+- TSK-{{FEATURE}}-003: Implementation (GREEN)
+
+### Sprint 2 (Week 2)
+- TSK-{{FEATURE}}-004: Refactor (BLUE)
+- TSK-{{FEATURE}}-005: CLI Command
+
+## Task Details
+
+### TSK-{{FEATURE}}-001: [Title]
+...
+
+## Traceability Matrix
+
+| Task | Requirement | Design | Test |
+|------|-------------|--------|------|
+| TSK-001 | REQ-XXX-001 | DES-XXX-001 | xxx.test.ts |
+
+## Definition of Done
+
+- [ ] All tests pass
+- [ ] Code reviewed
+- [ ] Documentation updated
+- [ ] Traceability verified
+```
+
+---
+
+### 7. MCP Tool Integration
+
+Use MUSUBIX MCP tools:
+
+```
+sdd_create_tasks - Generate tasks from design
+```
+
+---
+
+**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
+**Version**: 1.0.0