@sk8metal/michi-cli 0.20.0 → 0.22.0

package/scripts/utils/docker-requirement-detector.ts

@@ -24,7 +24,7 @@ export function analyzeDockerRequirement(feature: string, projectRoot: string =
   let score = 0;
   
   // design.mdを解析
-  const designPath = join(projectRoot, '.kiro', 'specs', feature, 'design.md');
+  const designPath = join(projectRoot, '.michi', 'specs', feature, 'design.md');
   if (existsSync(designPath)) {
     const design = safeReadFileOrThrow(designPath, 'utf-8');
     
@@ -88,7 +88,7 @@ export function analyzeDockerRequirement(feature: string, projectRoot: string =
   }
   
   // test-type-selection.jsonを解析
-  const testSelectionPath = join(projectRoot, '.kiro', 'specs', feature, 'test-type-selection.json');
+  const testSelectionPath = join(projectRoot, '.michi', 'specs', feature, 'test-type-selection.json');
   if (existsSync(testSelectionPath)) {
     try {
       const testSelection = JSON.parse(safeReadFileOrThrow(testSelectionPath, 'utf-8'));
@@ -117,7 +117,7 @@ export function analyzeDockerRequirement(feature: string, projectRoot: string =
   }
   
   // requirements.mdを解析
-  const requirementsPath = join(projectRoot, '.kiro', 'specs', feature, 'requirements.md');
+  const requirementsPath = join(projectRoot, '.michi', 'specs', feature, 'requirements.md');
   if (existsSync(requirementsPath)) {
     const requirements = safeReadFileOrThrow(requirementsPath, 'utf-8');
     

package/scripts/utils/language-detector.ts

@@ -29,7 +29,7 @@ export function analyzeLanguage(feature: string, projectRoot: string = process.c
   };
   
   // design.mdを解析
-  const designPath = join(projectRoot, '.kiro', 'specs', feature, 'design.md');
+  const designPath = join(projectRoot, '.michi', 'specs', feature, 'design.md');
   if (existsSync(designPath)) {
     const design = safeReadFileOrThrow(designPath, 'utf-8');
     
@@ -93,7 +93,7 @@ export function analyzeLanguage(feature: string, projectRoot: string = process.c
   }
   
   // requirements.mdを解析
-  const requirementsPath = join(projectRoot, '.kiro', 'specs', feature, 'requirements.md');
+  const requirementsPath = join(projectRoot, '.michi', 'specs', feature, 'requirements.md');
   if (existsSync(requirementsPath)) {
     const requirements = safeReadFileOrThrow(requirementsPath, 'utf-8');
     

package/scripts/utils/multi-repo-validator.ts

@@ -159,13 +159,13 @@ export function validateRepositoryUrl(url: string): Result<boolean, string> {
 
 /**
  * Michi導入状況をチェック
- * .kiro/project.json の存在でMichi導入済みと判定
+ * .michi/project.json の存在でMichi導入済みと判定
  *
  * @param localPath - 子リポジトリのlocalPath
  * @returns Michi導入済みかどうか
  */
 export function hasMichiSetup(localPath: string): boolean {
-  const projectJsonPath = path.join(localPath, '.kiro', 'project.json');
+  const projectJsonPath = path.join(localPath, '.michi', 'project.json');
   return fs.existsSync(projectJsonPath);
 }
 
@@ -330,7 +330,7 @@ export function validateLocalPath(
   if (!hasMichiSetupResult) {
     michiSetupCommand = getMichiSetupCommand(localPath);
     warnings.push(
-      `Repository '${repository.name}' does not have Michi setup (.kiro/project.json not found)`,
+      `Repository '${repository.name}' does not have Michi setup (.michi/project.json not found)`,
     );
   }
 

package/scripts/utils/project-analyzer.ts

@@ -143,13 +143,13 @@ export class ProjectAnalyzer {
   }
 
   /**
-   * Get project metadata from .kiro/project.json
+   * Get project metadata from .michi/project.json
    *
    * @param projectRoot - Project root directory (default: process.cwd())
    * @returns Result<ProjectMetadata, ProjectError> - Project metadata or error
    */
   getProjectMetadata(projectRoot: string = process.cwd()): Result<ProjectMetadata, ProjectError> {
-    const projectJsonPath = resolve(projectRoot, '.kiro/project.json');
+    const projectJsonPath = resolve(projectRoot, '.michi/project.json');
 
     if (!existsSync(projectJsonPath)) {
       return failure([{

package/scripts/utils/spec-archiver.ts

@@ -1,6 +1,6 @@
 /**
  * 仕様書アーカイブユーティリティ
- * 完了した仕様書を .kiro/specs/archive/ に移動する
+ * 完了した仕様書を .michi/specs/archive/ に移動する
  */
 
 import { existsSync, renameSync, mkdirSync, readdirSync, writeFileSync } from 'fs';
@@ -67,7 +67,7 @@ export function canArchiveSpec(
     };
   }
 
-  const specDir = resolve(projectRoot, `.kiro/specs/${featureName}`);
+  const specDir = resolve(projectRoot, `.michi/specs/${featureName}`);
 
   if (!existsSync(specDir)) {
     return { canArchive: false, reason: 'Spec not found' };
@@ -137,8 +137,8 @@ export function archiveSpec(
     return { success: false, feature: featureName, error: check.reason };
   }
 
-  const sourceDir = resolve(projectRoot, `.kiro/specs/${featureName}`);
-  const archiveDir = resolve(projectRoot, '.kiro/specs/archive');
+  const sourceDir = resolve(projectRoot, `.michi/specs/${featureName}`);
+  const archiveDir = resolve(projectRoot, '.michi/specs/archive');
   const targetDir = resolve(archiveDir, featureName);
 
   // archive ディレクトリ作成
@@ -178,7 +178,7 @@ export function listSpecs(
   projectRoot: string = process.cwd()
 ): SpecInfo[] {
   const specs: SpecInfo[] = [];
-  const specsDir = resolve(projectRoot, '.kiro/specs');
+  const specsDir = resolve(projectRoot, '.michi/specs');
 
   if (!existsSync(specsDir)) {
     return specs;

package/scripts/utils/spec-updater.ts

@@ -83,7 +83,7 @@ export interface SpecJson {
  * spec.json を読み込む
  */
 export function loadSpecJson(featureName: string, projectRoot: string = process.cwd()): SpecJson {
-  const specPath = resolve(projectRoot, `.kiro/specs/${featureName}/spec.json`);
+  const specPath = resolve(projectRoot, `.michi/specs/${featureName}/spec.json`);
 
   if (!existsSync(specPath)) {
     // 新規作成する場合は最低限の構造を返す
@@ -121,7 +121,7 @@ export function loadSpecJson(featureName: string, projectRoot: string = process.
  * @param projectRoot プロジェクトルート（デフォルト: process.cwd()）
  */
 export function saveSpecJson(featureName: string, spec: SpecJson, projectRoot: string = process.cwd()): void {
-  const specDir = resolve(projectRoot, `.kiro/specs/${featureName}`);
+  const specDir = resolve(projectRoot, `.michi/specs/${featureName}`);
   const specPath = resolve(specDir, 'spec.json');
 
   // ディレクトリが存在しない場合は作成

package/scripts/utils/tasks-converter.ts

@@ -297,7 +297,7 @@ export function convertToMichiFormat(
   );
   lines.push(`- **${language === 'ja' ? '成果物' : 'Deliverables'}**:`);
   lines.push(
-    `  - \`.kiro/specs/${projectName.toLowerCase().replace(/\s+/g, '-')}/requirements.md\``,
+    `  - \`.michi/specs/${projectName.toLowerCase().replace(/\s+/g, '-')}/requirements.md\``,
   );
   lines.push(
     `- **${language === 'ja' ? '受け入れ基準' : 'Acceptance Criteria'}**:`,
@@ -335,7 +335,7 @@ export function convertToMichiFormat(
   );
   lines.push(`- **${language === 'ja' ? '成果物' : 'Deliverables'}**:`);
   lines.push(
-    `  - \`.kiro/specs/${projectName.toLowerCase().replace(/\s+/g, '-')}/design.md\``,
+    `  - \`.michi/specs/${projectName.toLowerCase().replace(/\s+/g, '-')}/design.md\``,
   );
   lines.push(
     `- **${language === 'ja' ? '受け入れ基準' : 'Acceptance Criteria'}**:`,

package/scripts/utils/template-applier.ts

@@ -44,7 +44,7 @@ export interface TemplateData {
 export function loadTestSpecTemplate(testType: string, projectRoot: string = process.cwd()): string {
   const templatePath = join(
     projectRoot,
-    '.kiro',
+    '.michi',
     'settings',
     'templates',
     'test-specs',

package/scripts/validate-phase.ts

@@ -34,7 +34,7 @@ interface ValidationResult {
  * spec.jsonを読み込み
  */
 function loadSpecJson(feature: string): SpecJson {
-  const specPath = join(process.cwd(), '.kiro', 'specs', feature, 'spec.json');
+  const specPath = join(process.cwd(), '.michi', 'specs', feature, 'spec.json');
 
   if (!existsSync(specPath)) {
     throw new Error(`spec.json not found: ${specPath}`);
@@ -67,7 +67,7 @@ function validateRequirements(feature: string): ValidationResult {
   }
   
   // 1. requirements.md存在チェック
-  const requirementsPath = join(process.cwd(), '.kiro', 'specs', feature, 'requirements.md');
+  const requirementsPath = join(process.cwd(), '.michi', 'specs', feature, 'requirements.md');
   if (!existsSync(requirementsPath)) {
     errors.push('❌ requirements.md が作成されていません');
   }
@@ -121,7 +121,7 @@ function validateDesign(feature: string): ValidationResult {
   }
   
   // 1. design.md存在チェック
-  const designPath = join(process.cwd(), '.kiro', 'specs', feature, 'design.md');
+  const designPath = join(process.cwd(), '.michi', 'specs', feature, 'design.md');
   if (!existsSync(designPath)) {
     errors.push('❌ design.md が作成されていません');
   }
@@ -175,7 +175,7 @@ function validateTasks(feature: string): ValidationResult {
   }
   
   // 1. tasks.md存在チェック
-  const tasksPath = join(process.cwd(), '.kiro', 'specs', feature, 'tasks.md');
+  const tasksPath = join(process.cwd(), '.michi', 'specs', feature, 'tasks.md');
   if (!existsSync(tasksPath)) {
     errors.push('❌ tasks.md が作成されていません');
   } else {

package/templates/claude-agent/README.md

@@ -25,7 +25,7 @@ Placeholders are replaced with project-specific values during setup.
 
 - {{LANG_CODE}}: Language code (ja, en, etc.)
 - {{DEV_GUIDELINES}}: Development guidelines
-- {{KIRO_DIR}}: Kiro directory (default: .kiro)
+- {{SPEC_DIR}}: Kiro directory (default: .michi)
 - {{AGENT_DIR}}: Agent directory (default: .claude)
 - {{PROJECT_ID}}: Project ID
 - {{FEATURE_NAME}}: Feature name

package/templates/claude-agent/agents/designer.md

@@ -28,13 +28,13 @@ System design and architecture documentation.
 
 ### Requirements Document
 
-- Location: {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/requirements.md
+- Location: {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/requirements.md
 - Content: Functional and non-functional requirements
 - Format: Structured markdown with acceptance criteria
 
 ### Design Document
 
-- Location: {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/design.md
+- Location: {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/design.md
 - Content: Architecture, interfaces, data models
 - Include: Error handling strategy, security considerations
 
@@ -68,12 +68,12 @@ System design and architecture documentation.
 ## Project Context
 
 - Project ID: {{PROJECT_ID}}
-- Kiro directory: {{KIRO_DIR}}
+- Kiro directory: {{SPEC_DIR}}
 - Agent directory: {{AGENT_DIR}}
 - Feature name: {{FEATURE_NAME}}
 
 ## Constraints
 
 - Do not implement code (delegate to developer)
-- All designs must be documented in {{KIRO_DIR}}/specs/
+- All designs must be documented in {{SPEC_DIR}}/specs/
 - Consider existing architecture patterns in the codebase

package/templates/claude-agent/agents/developer.md

@@ -30,7 +30,7 @@ Code implementation following TDD principles.
 
 ### 1. Red Phase
 
-- Read design document at {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/design.md
+- Read design document at {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/design.md
 - Write failing tests first
 - Define expected behavior through tests
 
@@ -56,7 +56,7 @@ Code implementation following TDD principles.
 ## Project Context
 
 - Project ID: {{PROJECT_ID}}
-- Kiro directory: {{KIRO_DIR}}
+- Kiro directory: {{SPEC_DIR}}
 - Agent directory: {{AGENT_DIR}}
 - Feature name: {{FEATURE_NAME}}
 

package/templates/claude-agent/agents/doc-reviewer.md

@@ -69,11 +69,11 @@ Detect the following patterns:
 
 ### 3.5. Michi-Specific Checks
 
-For documents in `.kiro/specs/` directory:
+For documents in `.michi/specs/` directory:
 - **@-reference integrity**: Verify `@.claude/rules/...` paths exist and are valid
 - **Placeholder detection**: Check for unreplaced placeholders like `{{PLACEHOLDER}}`
 - **Phase compliance**: For `design.md`, verify Test Plan section exists (Phase 0.3-0.4)
-- **Project context**: Validate {{PROJECT_ID}}, {{KIRO_DIR}}, {{AGENT_DIR}} usage
+- **Project context**: Validate {{PROJECT_ID}}, {{SPEC_DIR}}, {{AGENT_DIR}} usage
 
 ### 4. Required Section Verification
 
@@ -96,7 +96,7 @@ Output review results in the format defined in doc-review-rules.md:
 ## Project Context
 
 - Project ID: {{PROJECT_ID}}
-- Kiro directory: {{KIRO_DIR}}
+- Kiro directory: {{SPEC_DIR}}
 - Agent directory: {{AGENT_DIR}}
 
 ## Constraints
@@ -107,7 +107,7 @@ Output review results in the format defined in doc-review-rules.md:
 
 ## Usage Example
 
-When reviewing `.kiro/specs/{{FEATURE_NAME}}/requirements.md`:
+When reviewing `.michi/specs/{{FEATURE_NAME}}/requirements.md`:
 
 1. Read the file using Read tool
 2. Detect document type: Design Document (50-100 lines guideline)

package/templates/claude-agent/agents/manager-agent.md

@@ -27,9 +27,9 @@ Project orchestration and workflow management.
 
 ### 1. Project Initialization
 
-- Initialize spec structure at {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/
+- Initialize spec structure at {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/
 - Create spec.json with project metadata
-- Reference {{KIRO_DIR}}/project.json for project context
+- Reference {{SPEC_DIR}}/project.json for project context
 
 ### 2. Task Management
 
@@ -49,7 +49,7 @@ Project orchestration and workflow management.
 ## Project Context
 
 - Project ID: {{PROJECT_ID}}
-- Kiro directory: {{KIRO_DIR}}
+- Kiro directory: {{SPEC_DIR}}
 - Agent directory: {{AGENT_DIR}}
 
 ## Constraints

package/templates/claude-agent/agents/repo-spec-executor.md

@@ -94,7 +94,7 @@ michi init
 
 ### 生成されたファイル
 
-1. `.kiro/specs/user-authentication/design.md` (320行)
+1. `.michi/specs/user-authentication/design.md` (320行)
    - システムコンテキスト図
    - コンポーネント設計
    - API定義: POST /api/v1/auth/login

package/templates/claude-agent/agents/tester.md

@@ -46,12 +46,12 @@ Manual/automated tests before release:
 
 ### Test Specifications
 
-- Location: {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/test-specs/
+- Location: {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/test-specs/
 - Content: Test cases, scenarios, expected results
 
 ### Test Execution
 
-- Location: {{KIRO_DIR}}/specs/{{FEATURE_NAME}}/test-execution/
+- Location: {{SPEC_DIR}}/specs/{{FEATURE_NAME}}/test-execution/
 - Content: Test scripts, configuration files
 
 ## Quality Standards
@@ -90,7 +90,7 @@ Manual/automated tests before release:
 ## Project Context
 
 - Project ID: {{PROJECT_ID}}
-- Kiro directory: {{KIRO_DIR}}
+- Kiro directory: {{SPEC_DIR}}
 - Agent directory: {{AGENT_DIR}}
 - Feature name: {{FEATURE_NAME}}
 

package/templates/claude-agent/commands/kiro/kiro-spec-impl.md

@@ -14,18 +14,18 @@ This command implements the specifications defined in `tasks.md` following TDD (
 
 - `$ARGUMENTS`: Feature name (e.g., "user-auth")
 
-**Note:** JIRA ticket keys are automatically detected from `.kiro/specs/{feature}/spec.json`. No need to specify them manually.
+**Note:** JIRA ticket keys are automatically detected from `.michi/specs/{feature}/spec.json`. No need to specify them manually.
 
 ## Pre-requisites
 
-1. `.kiro/specs/{feature}/tasks.md` must exist
-2. `.kiro/specs/{feature}/spec.json` must contain JIRA info (run `michi jira:sync` first)
+1. `.michi/specs/{feature}/tasks.md` must exist
+2. `.michi/specs/{feature}/spec.json` must contain JIRA info (run `michi jira:sync` first)
 3. Environment variables must be configured:
    - `ATLASSIAN_URL`: JIRA instance URL
    - `ATLASSIAN_EMAIL`: JIRA user email
    - `ATLASSIAN_API_TOKEN`: JIRA API token
    - `GITHUB_TOKEN`: GitHub API token
-   - ~~`GITHUB_REPO`: GitHub repository (owner/repo format)~~ **Deprecated (v0.5.0+)**: Repository info is now automatically loaded from `.kiro/project.json`
+   - ~~`GITHUB_REPO`: GitHub repository (owner/repo format)~~ **Deprecated (v0.5.0+)**: Repository info is now automatically loaded from `.michi/project.json`
 
 ## Execution Flow
 
@@ -43,7 +43,7 @@ Extract:
 
 ### 2. JIRA Info Detection (Automatic)
 
-Read JIRA information from `.kiro/specs/$FEATURE_NAME/spec.json`:
+Read JIRA information from `.michi/specs/$FEATURE_NAME/spec.json`:
 
 ```json
 {
@@ -72,7 +72,7 @@ This is handled internally. The workflow will:
 
 ### 4. Implementation Phase (TDD)
 
-Read the tasks from `.kiro/specs/$FEATURE_NAME/tasks.md` and implement each Story following TDD:
+Read the tasks from `.michi/specs/$FEATURE_NAME/tasks.md` and implement each Story following TDD:
 
 For each Story in tasks.md:
 

package/templates/claude-agent/commands/kiro/kiro-spec-tasks.md

@@ -5,7 +5,7 @@ description: Generate tasks.md from design specification in Michi workflow forma
 
 # Generate Tasks from Design Specification
 
-**Important**: Generate output in the language specified in `{{KIRO_DIR}}/project.json`.
+**Important**: Generate output in the language specified in `{{SPEC_DIR}}/project.json`.
 
 ## Overview
 
@@ -21,13 +21,13 @@ This command generates a detailed task breakdown (`tasks.md`) from the design sp
 
 ## Input Files
 
-1. `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/design.md` - Design specification
-2. `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/requirements.md` - Requirements specification
-3. `{{KIRO_DIR}}/project.json` - Project metadata
+1. `{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/design.md` - Design specification
+2. `{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/requirements.md` - Requirements specification
+3. `{{SPEC_DIR}}/project.json` - Project metadata
 
 ## Output File
 
-`{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/tasks.md`
+`{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/tasks.md`
 
 ## Required Format: Michi Workflow Structure
 
@@ -114,7 +114,7 @@ Each story within a phase MUST use this format:
 - **Effort**: 0.5 person-days
 - **Description**: Create feature requirements document
 - **Deliverables**:
-  - `.kiro/specs/{{FEATURE_NAME}}/requirements.md`
+  - `.michi/specs/{{FEATURE_NAME}}/requirements.md`
   - Confluence page (Requirements)
 - **Acceptance Criteria**:
   - [ ] Functional requirements defined
@@ -138,7 +138,7 @@ Each story within a phase MUST use this format:
 - **Effort**: 0.5-1.0 person-days
 - **Description**: Architecture design, API design, class design
 - **Deliverables**:
-  - `.kiro/specs/{{FEATURE_NAME}}/design.md`
+  - `.michi/specs/{{FEATURE_NAME}}/design.md`
   - Confluence page (Design Document)
 - **Acceptance Criteria**:
   - [ ] System architecture diagram created
@@ -334,11 +334,11 @@ Each story is automatically assigned the following labels:
 
 ## Execution Steps
 
-1. Read `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/design.md`
-2. Read `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/requirements.md`
+1. Read `{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/design.md`
+2. Read `{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/requirements.md`
 3. Analyze design components and create Story breakdown
 4. Generate `tasks.md` following the Michi Workflow Format above
-5. Save to `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/tasks.md`
+5. Save to `{{SPEC_DIR}}/specs/{{FEATURE_NAME}}/tasks.md`
 
 ## Validation Checklist
 

package/templates/claude-agent/rules/doc-review.md

@@ -57,7 +57,7 @@ alwaysApply: false
 - `node_modules/**/*.md`
 - `.git/**/*.md`
 - `vendor/**/*.md`
-- `.kiro/settings/**/*.md` （テンプレートファイル）
+- `.michi/settings/**/*.md` （テンプレートファイル）
 
 ## 注意事項
 

package/templates/common/.kiro/project.json.template

@@ -1,21 +0,0 @@
-{
-  "projectId": "{{PROJECT_ID}}",
-  "projectName": "{{PROJECT_NAME}}",
-  "language": "{{LANG_CODE}}",
-  "jiraProjectKey": "{{JIRA_KEY}}",
-  "jiraBaseUrl": "https://your-domain.atlassian.net",
-  "confluenceSpaceKey": "{{CONFLUENCE_SPACE}}",
-  "confluenceLabels": ["{{PROJECT_ID}}", "ai-development"],
-  "status": "active",
-  "team": [],
-  "stakeholders": [],
-  "repository": "{{REPO_URL}}",
-  "description": "{{PROJECT_DESCRIPTION}}",
-  "createdAt": "{{CREATED_DATE}}",
-  "metadata": {
-    "testStrategy": "master-test-approach",
-    "cicd": ["github-actions"],
-    "buildTool": "{{BUILD_TOOL}}",
-    "michiVersion": "{{MICHI_VERSION}}"
-  }
-}