musubix 3.4.1 → 3.4.3

package/.github/prompts/sdd-change-init.prompt.md

@@ -1,269 +0,0 @@
-# MUSUBIX Change Init Command
-
-Initialize a change proposal for brownfield projects (existing codebase).
-
----
-
-## Instructions for AI Agent
-
-You are executing the `musubix change init [change-name]` command to create a change proposal for an existing codebase.
-
-### Command Format
-
-```bash
-npx musubix change init add-2fa
-npx musubix change init migrate-to-graphql
-npx musubix change init refactor-auth-service
-```
-
-### Your Task
-
-Generate a change proposal specification that documents what will be added, modified, or removed in the existing MUSUBIX system.
-
----
-
-## Process
-
-### 1. Read Steering Context (Article VI)
-
-**IMPORTANT**: Before starting, read steering files:
-
-```bash
-steering/product.ja.md      # Current product context
-steering/structure.ja.md    # Existing architecture
-steering/tech.ja.md         # Current technology stack
-```
-
----
-
-### 2. Analyze Existing System
-
-**Research Current Implementation**:
-
-```bash
-# Search for related code
-grep -r "{{related-feature}}" packages/
-
-# Find existing requirements
-ls storage/specs/REQ-*.md
-
-# Check existing design documents
-ls storage/specs/DES-*.md
-```
-
-**Document Current State**:
-
-- What exists now?
-- What packages are affected?
-- What dependencies exist?
-- What tests cover this area?
-
----
-
-### 3. Gather Change Requirements
-
-**Ask User**:
-
-- Why is this change needed?
-- What problem does it solve?
-- What must NOT change (backward compatibility)?
-- What is the timeline?
-
-**Impact Analysis**:
-
-- [ ] packages/core/ components
-- [ ] packages/mcp-server/ tools
-- [ ] packages/yata-client/ integration
-- [ ] CLI commands
-- [ ] Tests
-- [ ] Documentation
-
----
-
-### 4. Generate Change Proposal
-
-**Output**: `storage/changes/{{CHANGE_NAME}}-proposal.md`
-
-```markdown
-# Change Proposal: {{CHANGE_NAME}}
-
-**Document ID**: CHG-{{CHANGE}}-001
-**Version**: 1.0.0
-**Date**: {{DATE}}
-**Status**: Proposed
-
-## Summary
-
-**Change Type**: Feature / Enhancement / Refactor / Bug Fix
-**Affected Packages**: packages/core/, packages/mcp-server/
-**Risk Level**: Low / Medium / High
-
-## Motivation
-
-**Problem Statement**:
-[Why is this change needed?]
-
-**Business Value**:
-[What value does this provide?]
-
-## Current State
-
-### Existing Implementation
-
-| Component | Location | Description |
-|-----------|----------|-------------|
-| AuthService | packages/core/src/auth/ | Current auth implementation |
-
-### Existing Tests
-
-| Test File | Coverage |
-|-----------|----------|
-| auth.test.ts | 85% |
-
-## Proposed Changes
-
-### ADDED Requirements
-
-#### REQ-{{COMPONENT}}-NEW-001: [New Feature]
-
-> [EARS statement]
-
-**Priority**: P1
-**Acceptance Criteria**:
-- [ ] [Criterion 1]
-
-### MODIFIED Requirements
-
-#### REQ-{{COMPONENT}}-001: [Modified Feature]
-
-**Current**:
-> [Current EARS statement]
-
-**Proposed**:
-> [New EARS statement]
-
-**Change Reason**: [Why modify?]
-
-### REMOVED Requirements
-
-#### REQ-{{COMPONENT}}-OLD-001: [Deprecated Feature]
-
-**Reason**: [Why remove?]
-**Migration Path**: [How to migrate?]
-
-## Impact Analysis
-
-### Affected Components
-
-| Package | Component | Impact |
-|---------|-----------|--------|
-| core | auth/service.ts | Modified |
-| mcp-server | tools/auth-tools.ts | Modified |
-
-### Breaking Changes
-
-- [ ] CLI API changes
-- [ ] MCP tool changes
-- [ ] Type changes
-
-### Migration Requirements
-
-1. [Migration step 1]
-2. [Migration step 2]
-
-## Implementation Plan
-
-### Phase 1: Preparation
-
-- [ ] Create feature branch
-- [ ] Write tests for new requirements
-- [ ] Update documentation
-
-### Phase 2: Implementation
-
-- [ ] Implement changes
-- [ ] Update affected components
-- [ ] Add feature flag (if needed)
-
-### Phase 3: Validation
-
-- [ ] Run all tests
-- [ ] Validate traceability
-- [ ] Code review
-
-## Rollback Plan
-
-1. Revert feature flag
-2. Deploy previous version
-3. Restore database (if needed)
-
-## Approval
-
-| Role | Name | Date | Status |
-|------|------|------|--------|
-| Architect | | | Pending |
-| Lead Dev | | | Pending |
-```
-
----
-
-### 5. Delta Specification
-
-For modifications, create delta spec:
-
-```markdown
-## Delta Specification
-
-### packages/core/src/auth/service.ts
-
-**Change Type**: Modified
-
-**Current Implementation**:
-\`\`\`typescript
-export class AuthService {
-  async login(email: string, password: string): Promise<Session> {
-    // Current implementation
-  }
-}
-\`\`\`
-
-**Proposed Implementation**:
-\`\`\`typescript
-export class AuthService {
-  async login(email: string, password: string, mfaCode?: string): Promise<Session> {
-    // New implementation with MFA support
-    if (this.config.mfaEnabled && !mfaCode) {
-      throw new MFARequiredError();
-    }
-  }
-}
-\`\`\`
-
-**Breaking Change**: Yes - New optional parameter
-**Migration**: Update all callers to handle MFARequiredError
-```
-
----
-
-### 6. Traceability
-
-Link to existing documents:
-
-```markdown
-## Traceability
-
-### Related Requirements
-- REQ-AUTH-001: User authentication (MODIFIED)
-- REQ-AUTH-NEW-001: MFA support (ADDED)
-
-### Related Design
-- DES-AUTH-001: Authentication design (UPDATE REQUIRED)
-
-### Related Tasks
-- TSK-AUTH-001: Implement MFA (NEW)
-```
-
----
-
-**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
-**Version**: 1.0.0

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

@@ -1,250 +0,0 @@
-# MUSUBIX Design Command
-
-Generate technical design from requirements using C4 model.
-
----
-
-## Instructions for AI Agent
-
-You are executing the `musubix design [feature-name]` command to create a technical design specification.
-
-### Command Format
-
-```bash
-npx musubix design generate requirements.md
-npx musubix design patterns context
-npx musubix design validate design.md
-npx musubix design c4 design.md
-npx musubix design adr decision
-```
-
-### Your Task
-
-Generate a comprehensive technical design that implements the requirements while adhering to constitutional governance.
-
----
-
-## Process
-
-### 1. Read Context (Article VI)
-
-**CRITICAL**: Read these files BEFORE designing:
-
-```bash
-# Steering Context
-steering/structure.ja.md    # Architecture patterns to follow
-steering/tech.ja.md         # Technology stack (TypeScript, Node.js 20+)
-steering/product.ja.md      # Product goals and users
-
-# Requirements
-storage/specs/REQ-{{FEATURE}}-001.md  # What to implement
-```
-
----
-
-### 2. Verify Requirements Exist
-
-**If NOT found**:
-
-```markdown
-❌ **Requirements file not found**
-
-Expected: storage/specs/REQ-{{FEATURE}}-001.md
-
-Please run `npx musubix requirements analyze {{feature}}` first.
-
-Design cannot proceed without requirements (Article V: Traceability).
-```
-
----
-
-### 3. Generate Design Document (C4 Model)
-
-**Output**: `storage/specs/DES-{{FEATURE}}-001.md`
-
-#### A. Context Diagram (Level 1)
-
-- System boundary
-- External users
-- External systems
-
-#### B. Container Diagram (Level 2)
-
-MUSUBIX architecture:
-
-```
-┌─────────────────────────────────────────────────────────┐
-│                    MUSUBIX System                        │
-│                                                          │
-│  ┌─────────────────┐  ┌─────────────────┐               │
-│  │ @nahisaho/      │  │ @nahisaho/      │               │
-│  │ musubix-core    │←→│ musubix-mcp-    │               │
-│  │                 │  │ server          │               │
-│  └────────┬────────┘  └────────┬────────┘               │
-│           │                    │                         │
-│           │    ┌───────────────┘                         │
-│           │    │                                         │
-│           ▼    ▼                                         │
-│  ┌─────────────────┐                                    │
-│  │ @nahisaho/      │                                    │
-│  │ musubix-yata-   │                                    │
-│  │ client          │                                    │
-│  └─────────────────┘                                    │
-└─────────────────────────────────────────────────────────┘
-```
-
-#### C. Component Diagram (Level 3)
-
-For packages/core/:
-
-```
-packages/core/src/
-├── auth/           # Authentication & Authorization
-├── cli/            # CLI Interface (Article II)
-├── codegen/        # Code Generation & Analysis
-├── design/         # Design Patterns & C4 Models
-├── error/          # Error Handling
-├── explanation/    # Explanation Generation
-├── requirements/   # Requirements Analysis
-├── traceability/   # Traceability
-├── types/          # Type Definitions
-├── utils/          # Utilities
-└── validators/     # EARS Validation
-```
-
----
-
-### 4. Requirements Mapping (Article V)
-
-**CRITICAL**: Map EVERY requirement to design decisions.
-
-```markdown
-| Component | Requirements | Design Rationale |
-|-----------|--------------|------------------|
-| CLI | REQ-CLI-001 | Command interface |
-| Validator | REQ-EARS-001 | EARS pattern validation |
-| MCP Server | REQ-MCP-001 | Tool/prompt exposure |
-```
-
----
-
-### 5. API Design
-
-For CLI commands:
-
-```typescript
-// packages/core/src/cli/commands/{{feature}}.ts
-
-export interface {{Feature}}Options {
-  input: string;
-  output?: string;
-  format?: 'json' | 'markdown';
-}
-
-export async function {{feature}}Command(options: {{Feature}}Options): Promise<void> {
-  // REQ-{{COMPONENT}}-001: [Requirement title]
-}
-```
-
-For MCP tools:
-
-```typescript
-// packages/mcp-server/src/tools/{{feature}}-tools.ts
-
-export const {{feature}}Tool: ToolDefinition = {
-  name: 'sdd_{{feature}}',
-  description: '{{Feature description}}',
-  inputSchema: {
-    type: 'object',
-    properties: {
-      // ...
-    },
-    required: ['...'],
-  },
-  handler: async (args) => {
-    // REQ-{{COMPONENT}}-001
-  },
-};
-```
-
----
-
-### 6. Design Document Template
-
-```markdown
-# Design Document: {{FEATURE_NAME}}
-
-**Document ID**: DES-{{FEATURE}}-001
-**Version**: 1.0.0
-**Date**: {{DATE}}
-**Requirements**: REQ-{{FEATURE}}-001
-
-## Overview
-
-- **Purpose**: [Design purpose]
-- **Package**: packages/core/ | packages/mcp-server/ | packages/yata-client/
-
-## C4 Model
-
-### Level 1: Context
-[Context diagram]
-
-### Level 2: Container
-[Container diagram]
-
-### Level 3: Component
-[Component diagram]
-
-## Requirements Traceability
-
-| Requirement | Component | Implementation |
-|-------------|-----------|----------------|
-| REQ-XXX-001 | cli/commands/{{feature}}.ts | {{Feature}}Command |
-
-## API Design
-
-### CLI Interface (Article II)
-
-\`\`\`bash
-npx musubix {{feature}} [options]
-\`\`\`
-
-### TypeScript Interface
-
-\`\`\`typescript
-export interface {{Feature}}Options {
-  // ...
-}
-\`\`\`
-
-## ADR (Architecture Decision Records)
-
-### ADR-001: [Decision Title]
-
-**Status**: Accepted
-**Context**: [Why was this decision needed?]
-**Decision**: [What was decided?]
-**Consequences**: [What are the results?]
-
-## Traceability
-
-- **Requirements**: REQ-{{FEATURE}}-001
-- **Tasks**: TSK-{{FEATURE}}-001
-- **Tests**: packages/core/__tests__/unit/{{feature}}.test.ts
-```
-
----
-
-### 7. MCP Tool Integration
-
-Use MUSUBIX MCP tools:
-
-```
-sdd_create_design - Create design document
-sdd_validate_design - Validate traceability
-```
-
----
-
-**MUSUBIX**: https://github.com/nahisaho/MUSUBIX
-**Version**: 1.0.0