@sk8metal/michi-cli 0.10.1 → 0.12.0

package/templates/cursor/commands/kiro/kiro-spec-tasks.md

@@ -1,354 +0,0 @@
----
-name: /kiro:spec-tasks
-description: Generate tasks.md from design specification in Michi workflow format
----
-
-# Generate Tasks from Design Specification
-
-**Important**: Generate output in the language specified in `{{KIRO_DIR}}/project.json`.
-
-## Overview
-
-This command generates a detailed task breakdown (`tasks.md`) from the design specification (`design.md`) following the **Michi Workflow Format**.
-
-**Critical**: The generated tasks.md MUST follow the Michi Phase structure (Phase 0.1-5, A, B) with Story headers. DO NOT generate AI-DLC checkbox format (`- [ ] 1.`, `- [ ] 1.1`).
-
-## Usage
-
-```
-/kiro:spec-tasks
-```
-
-## 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
-
-## Output File
-
-`{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/tasks.md`
-
-## Required Format: Michi Workflow Structure
-
-### Header Section
-
-```markdown
-# Task Breakdown: {{FEATURE_NAME}}
-
-## Project Information
-
-- **Feature Name**: {{FEATURE_NAME}}
-- **Start Date**: YYYY-MM-DD (Day of week) Day 1
-- **End Date**: YYYY-MM-DD (Day of week)
-- **Total Business Days**: X business days (excluding weekends)
-- **Total Effort Estimate**: X person-days
-- **Holidays**: Excludes Saturdays and Sundays
-- **Note**: This task breakdown is calculated in business days (excluding weekends and holidays)
-```
-
-### Phase Structure (Required)
-
-The tasks.md MUST include these phases in order:
-
-1. **Phase 0.1: Requirements**
-2. **Phase 0.2: Design**
-3. **Phase 0.3: Test Type Selection** (optional)
-4. **Phase 0.4: Test Specification** (optional)
-5. **Phase 1: Environment Setup** (optional)
-6. **Phase 2: TDD Implementation** (required - main development phase)
-7. **Phase A: PR Pre-merge Tests** (optional - CI/CD automated)
-8. **Phase 3: Additional QA** (optional)
-9. **Phase B: Release Preparation Tests** (optional)
-10. **Phase 4: Release Preparation**
-11. **Phase 5: Release**
-
-### Phase Header Format
-
-Each phase MUST use this header format:
-
-```markdown
-## Phase X.Y: Phase Name (Label)
-
-**Period**: Day X-Y
-**Effort**: X person-days
-**Status**: Not Started
-```
-
-### Story Header Format
-
-Each story within a phase MUST use this format:
-
-```markdown
-### Story X.Y.Z: Story Title
-
-- **Assignee**: @Role
-- **Effort**: X person-days
-- **Description**: What this story accomplishes
-- **Deliverables**:
-  - Deliverable 1
-  - Deliverable 2
-- **Acceptance Criteria**:
-  - [ ] Criterion 1
-  - [ ] Criterion 2
-- **Tasks**:
-  - [ ] Task X.Y.Z.1: Task description
-  - [ ] Task X.Y.Z.2: Task description
-- **Dependencies**: Story X.Y.W (if applicable)
-```
-
-## Detailed Phase Guidelines
-
-### Phase 0.1: Requirements
-
-```markdown
-## Phase 0.1: Requirements (Requirements)
-
-**Period**: Day 1
-**Effort**: 0.5 person-days
-**Status**: Not Started
-
-### Story 0.1.1: Requirements Document Creation
-
-- **Assignee**: @PM
-- **Effort**: 0.5 person-days
-- **Description**: Create feature requirements document
-- **Deliverables**:
-  - `.kiro/specs/{{FEATURE_NAME}}/requirements.md`
-  - Confluence page (Requirements)
-- **Acceptance Criteria**:
-  - [ ] Functional requirements defined
-  - [ ] Non-functional requirements defined
-  - [ ] Use cases documented
-  - [ ] PM approved
-```
-
-### Phase 0.2: Design
-
-```markdown
-## Phase 0.2: Design (Design)
-
-**Period**: Day 1-2
-**Effort**: 0.5-1.0 person-days
-**Status**: Not Started
-
-### Story 0.2.1: Basic Design
-
-- **Assignee**: @Architect
-- **Effort**: 0.5-1.0 person-days
-- **Description**: Architecture design, API design, class design
-- **Deliverables**:
-  - `.kiro/specs/{{FEATURE_NAME}}/design.md`
-  - Confluence page (Design Document)
-- **Acceptance Criteria**:
-  - [ ] System architecture diagram created
-  - [ ] Layer structure defined
-  - [ ] API specifications detailed
-  - [ ] Class design completed
-  - [ ] Architect approved
-```
-
-### Phase 2: TDD Implementation (Main Development)
-
-This is the most detailed phase. Break down into multiple stories based on the design.md:
-
-```markdown
-## Phase 2: TDD Implementation (Implementation)
-
-**Period**: Day X-Y
-**Effort**: X person-days
-**Status**: Not Started
-
-### Story 2.1: Project Setup
-
-- **Assignee**: @Developer
-- **Effort**: 0.5 person-days
-- **Description**: Project setup and dependency configuration
-- **Tasks**:
-  - [ ] Task 2.1.1: Create project
-  - [ ] Task 2.1.2: Add dependencies
-  - [ ] Task 2.1.3: Create configuration files
-  - [ ] Task 2.1.4: Create package structure
-  - [ ] Task 2.1.5: Verify build
-- **Deliverables**:
-  - Project configuration files
-  - Package structure
-- **Acceptance Criteria**:
-  - [ ] Project builds successfully
-  - [ ] Application starts
-  - [ ] Package structure matches design
-
-### Story 2.2: [Feature Component] Implementation
-
-- **Assignee**: @Developer
-- **Effort**: X person-days
-- **Description**: Implement [component] with TDD approach
-- **Tasks**:
-  - [ ] Task 2.2.1: Write failing tests (RED)
-  - [ ] Task 2.2.2: Implement minimum code (GREEN)
-  - [ ] Task 2.2.3: Refactor (REFACTOR)
-  - [ ] Task 2.2.4: Integration tests
-- **Acceptance Criteria**:
-  - [ ] All unit tests pass
-  - [ ] Code coverage >= 95%
-  - [ ] Design patterns followed
-
-(Continue with Story 2.3, 2.4, etc. based on design.md components)
-```
-
-### Phase 4: Release Preparation
-
-```markdown
-## Phase 4: Release Preparation (Release Preparation)
-
-**Period**: Day Y-Z
-**Effort**: X person-days
-**Status**: Not Started
-
-### Story 4.1: Production Environment Setup
-
-- **Assignee**: @InfraEngineer
-- **Effort**: X person-days
-- **Description**: Production infrastructure setup and configuration
-- **Acceptance Criteria**:
-  - [ ] Server provisioned
-  - [ ] Database configured
-  - [ ] SSL certificate configured
-  - [ ] Monitoring configured
-
-### Story 4.2: Release Documentation
-
-- **Assignee**: @PM
-- **Effort**: X person-days
-- **Description**: Release notes, manual, operation procedures
-- **Acceptance Criteria**:
-  - [ ] Release notes created
-  - [ ] User manual created
-  - [ ] Operation procedures created
-```
-
-### Phase 5: Release
-
-```markdown
-## Phase 5: Release (Release)
-
-**Period**: Day Z
-**Effort**: X person-days
-**Status**: Not Started
-
-### Story 5.1: Staging Deployment
-
-- **Assignee**: @InfraEngineer
-- **Effort**: X person-days
-- **Description**: Deploy to staging and final verification
-- **Acceptance Criteria**:
-  - [ ] Staging deployment successful
-  - [ ] Smoke tests pass
-  - [ ] Final verification completed
-
-### Story 5.2: Production Release
-
-- **Assignee**: @InfraEngineer, @PM
-- **Effort**: X person-days
-- **Description**: Production release execution
-- **Acceptance Criteria**:
-  - [ ] Production deployment successful
-  - [ ] Smoke tests pass
-  - [ ] Monitoring verified
-  - [ ] Stakeholders notified
-```
-
-## Timeline Section
-
-Include a timeline at the end:
-
-```markdown
-## Timeline (Business Days)
-
-**Assumption**: Calculated in business days (excluding weekends)
-
-### Week 1: Specification Phase
-
-Day 1 (Mon):
-
-- Story 0.1.1: Requirements Document Creation
-- Story 0.2.1: Basic Design (start)
-
-Day 2-3 (Tue-Wed):
-
-- Story 0.2.1: Basic Design (complete)
-- Technical review and PM approval
-
-### Week 2-N: Implementation Phase
-
-(Continue based on project scope)
-```
-
-## Estimate Summary Section
-
-```markdown
-## Estimate Summary
-
-| Phase                        | Story Points | Effort (days) | Stories |
-| ---------------------------- | ------------ | ------------- | ------- |
-| Phase 0.1: Requirements      | X SP         | X days        | X       |
-| Phase 0.2: Design            | X SP         | X days        | X       |
-| Phase 2: TDD Implementation  | X SP         | X days        | X       |
-| Phase 4: Release Preparation | X SP         | X days        | X       |
-| Phase 5: Release             | X SP         | X days        | X       |
-| **Total**                    | **X SP**     | **X days**    | **X**   |
-
-**Conversion Rate**: 1 SP ≈ 0.5 person-days
-```
-
-## JIRA Labels Section
-
-```markdown
-## JIRA Labels
-
-Each story is automatically assigned the following labels:
-
-- `requirements` - Phase 0.1: Requirements
-- `design` - Phase 0.2: Design
-- `test-type-selection` - Phase 0.3: Test Type Selection
-- `test-spec` - Phase 0.4: Test Specification
-- `environment-setup` - Phase 1: Environment Setup
-- `implementation` / `tdd-implementation` - Phase 2: TDD Implementation
-- `phase-a` / `pr-tests` - Phase A: PR Pre-merge Tests
-- `additional-qa` / `testing` - Phase 3: Additional QA
-- `phase-b` / `release-tests` - Phase B: Release Preparation Tests
-- `release-prep` / `release-preparation` - Phase 4: Release Preparation
-- `release` - Phase 5: Release
-```
-
-## Important Notes
-
-1. **DO NOT** use AI-DLC checkbox format (`- [ ] 1.`, `- [ ] 1.1`)
-2. **MUST** use Phase headers (`## Phase X.Y:`)
-3. **MUST** use Story headers (`### Story X.Y.Z:`)
-4. **MUST** include day numbering (Day 1, Day 2, etc.)
-5. **MUST** include effort estimates in person-days
-6. **MUST** include acceptance criteria with checkboxes
-7. Break down Phase 2 stories based on the components in design.md
-8. Ensure each Story has clear dependencies documented
-
-## Execution Steps
-
-1. Read `{{KIRO_DIR}}/specs/{{FEATURE_NAME}}/design.md`
-2. Read `{{KIRO_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`
-
-## Validation Checklist
-
-Before finalizing, verify:
-
-- [ ] Phase headers exist (Phase 0.1, 0.2, 2, 4, 5 at minimum)
-- [ ] Story headers follow format (`### Story X.Y.Z:`)
-- [ ] Day numbering is present
-- [ ] Effort estimates are included
-- [ ] Acceptance criteria use checkboxes `- [ ]`
-- [ ] No AI-DLC format (`- [ ] 1.`, `- [ ] 1.1`) is used
-- [ ] Timeline section is included
-- [ ] Estimate summary table is included

package/templates/cursor/commands/michi/confluence-sync.md

@@ -1,76 +0,0 @@
----
-name: /michi:confluence-sync
-description: GitHub の Markdown を Confluence に同期
----
-
-# Confluence同期コマンド
-
-{{DEV_GUIDELINES}}
-
-このコマンドは、GitHubで管理されている仕様書（requirements, design, tasks）をConfluenceに同期します。
-
-## 使い方
-
-```
-/michi:confluence-sync <feature_name> [doc_type]
-```
-
-**パラメータ**:
-- `feature_name`: 機能名（例: user-auth）
-- `doc_type`: ドキュメントタイプ（requirements / design / tasks）省略時は requirements
-
-**例**:
-```
-/michi:confluence-sync user-auth
-/michi:confluence-sync user-auth design
-/michi:confluence-sync user-auth tasks
-```
-
-## 実行内容
-
-1. `{{KIRO_DIR}}/project.json` からプロジェクトメタデータを読み込み
-2. `{{KIRO_DIR}}/specs/<feature>/<doc_type>.md` を読み込み
-3. Markdown → Confluence Storage Format に変換
-4. GitHub URLを埋め込み
-5. Confluenceページを作成または更新
-6. ラベル付与（プロジェクトラベル + doc_type）
-7. ステークホルダーにメンション通知
-
-## 生成されるConfluenceページ
-
-**タイトル**: `[プロジェクト名] <feature> <doc_type>`  
-**スペース**: PRD（要件・設計）/ QA（テスト）  
-**ラベル**: project:<project_id>, <doc_type>, <feature_name>, github-sync  
-
-**ページ構成**:
-- GitHub連携情報（最新版へのリンク）
-- 変換されたMarkdownコンテンツ
-- 承認マクロ（企画・部長への承認依頼）
-
-## 実装
-
-スクリプトを直接実行：
-
-```bash
-npm run confluence:sync <feature_name> [doc_type]
-```
-
-内部的に `scripts/confluence-sync.ts` を実行します。
-
-## 前提条件
-
-- `.env` ファイルに Atlassian 認証情報が設定されている
-- `{{KIRO_DIR}}/project.json` が存在する
-- 同期する Markdown ファイルが存在する
-
-## トラブルシューティング
-
-### 認証エラー
-`.env` の `ATLASSIAN_API_TOKEN` を確認してください。
-
-### ページが見つからない
-Confluence スペースキー（PRD）が正しいか確認してください。
-
-### Markdown変換エラー
-Markdown形式が正しいか確認してください。
-

package/templates/cursor/commands/michi/project-switch.md

@@ -1,69 +0,0 @@
----
-name: /michi:project-switch
-description: プロジェクトを切り替える
----
-
-# プロジェクト切り替えコマンド
-
-{{DEV_GUIDELINES}}
-
-複数プロジェクトを管理している場合、プロジェクトを切り替えるコマンドです。
-
-## 使い方
-
-```
-/michi:project-switch <project_id>
-```
-
-**パラメータ**:
-- `project_id`: プロジェクトID（例: customer-a-service-1, michi）
-
-**例**:
-```
-/michi:project-switch michi
-/michi:project-switch customer-a-service-1
-```
-
-## 実行内容
-
-1. プロジェクトIDに対応するGitHubリポジトリを特定
-2. ローカルにクローン（未クローンの場合）またはチェックアウト
-3. `{{KIRO_DIR}}/project.json` を読み込んで表示
-4. 対応するConfluenceプロジェクトページのURLを表示
-5. JIRAプロジェクトダッシュボードのURLを表示
-
-## 出力例
-
-```
-✅ プロジェクト切り替え: michi
-
-プロジェクト情報:
-  名前: Michi - Managed Intelligent Comprehensive Hub for Integration
-  JIRA: MICHI
-  Confluence Labels: project:michi, service:hub
-  ステータス: active
-  チーム: @arigatatsuya
-
-リンク:
-  📄 Confluence: https://your-domain.atlassian.net/wiki/spaces/PRD/pages/
-  🎯 JIRA Dashboard: https://your-domain.atlassian.net/jira/projects/MICHI
-  🐙 GitHub: https://github.com/sk8metalme/michi
-```
-
-## ターミナル実行
-
-```bash
-# リポジトリをクローン/チェックアウト
-cd ~/work/projects
-jj git clone https://github.com/org/<project_id>
-cd <project_id>
-
-# プロジェクト情報を表示
-cat {{KIRO_DIR}}/project.json
-```
-
-## 関連コマンド
-
-- `/michi:project-list`: すべてのプロジェクトを一覧表示
-- `/kiro:spec-status`: 現在のプロジェクトの仕様ステータスを表示（cc-sdd標準コマンド）
-

package/templates/cursor/rules/atlassian-mcp.mdc

@@ -1,188 +0,0 @@
----
-title: Atlassian MCP Integration Rules
-description: {{DEV_GUIDELINES}} for MCP integration with Confluence/JIRA
----
-
-# Atlassian MCP Integration Rules
-
-## Prerequisites
-
-Atlassian MCP server must be configured in Cursor:
-- Credentials set in `~/.cursor/mcp.json`
-
-Reference: [Atlassian MCP](https://www.atlassian.com/ja/platform/remote-mcp-server)
-
-## Available MCP Tools
-
-Cursor AI can use the following tools:
-
-### Confluence
-- `confluence_create_page`: Create page
-- `confluence_update_page`: Update page
-- `confluence_search`: Search pages
-- `confluence_get_page`: Get page
-
-### JIRA
-- `jira_create_issue`: Create issue
-- `jira_update_issue`: Update issue
-- `jira_search`: Search issues
-- `jira_get_issue`: Get issue
-
-## Workflow Integration
-
-⚠️ **Important**: **Always use REST API scripts** for page/issue creation and updates. Use MCP tools only for reference and search operations.
-
-### Requirements Phase
-
-After generating `.kiro/specs/<feature>/requirements.md`:
-
-```
-Run script (required):
-  npm run phase:run <feature> requirements
-
-Execution:
-1. Load project metadata (.kiro/project.json)
-2. Convert Markdown (markdown-to-confluence.ts)
-3. Create page via REST API (confluence-sync.ts)
-4. Auto-update spec.json
-5. Run validation
-```
-
-### Design Phase
-
-After generating `.kiro/specs/<feature>/design.md`:
-
-```
-Run script (required):
-  npm run phase:run <feature> design
-
-Execution:
-1. Create Confluence page via REST API (confluence-sync.ts)
-2. Auto-update spec.json
-3. Run validation
-```
-
-### Task Breakdown Phase
-
-After generating `.kiro/specs/<feature>/tasks.md`:
-
-```
-Run script (required):
-  npm run phase:run <feature> tasks
-
-Execution:
-1. Create Epic via REST API (jira-sync.ts)
-2. Create Stories via REST API (all stories, jira-sync.ts)
-3. Set story points
-4. Auto-update spec.json
-5. Run validation
-```
-
-### Implementation Phase
-
-Update JIRA when starting and completing implementation (MCP for single reference operations, scripts recommended for multiple updates):
-
-```
-Option 1: MCP tool (for single update)
-  jira_update_issue({
-    issue_key: "{{JIRA_PROJECT_KEY}}-123",
-    status: "In Progress"
-  })
-
-Option 2: REST API script (for bulk updates)
-  npm run jira:sync <feature>
-```
-
-## MCP Usage Guidelines
-
-### When to Use MCP
-
-✅ **Recommended (reference/search only)**:
-- Search/get Confluence pages (reference purpose)
-- Search/get JIRA issues (reference purpose)
-- Single operation information retrieval
-- Interactive information checking within Cursor AI
-
-❌ **Prohibited (creation/update)**:
-- Confluence page creation/update → **Scripts required**
-- JIRA issue creation/update → **Scripts required**
-- Bulk operations (10+ pages/issues) → **Scripts required**
-- Complex workflows → **Scripts required**
-
-### MCP vs REST API Scripts
-
-| Use Case | Method | Reason |
-|----------|--------|--------|
-| Page/Issue creation | **REST API Script** | Rate limit handling, error handling, bulk processing |
-| Page/Issue update | **REST API Script** | Rate limit handling, error handling |
-| Page/Issue search (reference) | MCP | Simple, AI integration |
-| Page/Issue get (reference) | MCP | Simple, AI integration |
-
-## Rate Limiting
-
-Atlassian rate limits vary by product (Confluence/JIRA), tenant, app context, and plan, controlled via quota/burst mode or per-minute windows.
-
-**Confluence Cloud**:
-- Migration: 6,000-12,000 requests/minute
-- General use: Quota + burst mode (~10s burst window, 1h quota window)
-
-**JIRA Cloud**:
-- Cost/quota-based limits (per app, per user, app+user)
-- Issue write limits: 20 ops/2s, 100 ops/30s
-
-Rate limit violations return `429` response with `Retry-After` and `X-RateLimit-*` headers for retry guidance.
-
-**Recommended Mitigation**:
-- Detect and honor response headers (`Retry-After`, `X-RateLimit-*`)
-- Implement exponential backoff + jitter retry
-- Use caching and batch processing
-- For frequent operations, use REST API (fine-grained control)
-
-**Official Documentation**:
-- [Confluence API Rate Limiting](https://developer.atlassian.com/cloud/confluence/rate-limiting/)
-- [JIRA API Rate Limiting](https://developer.atlassian.com/cloud/jira/platform/rate-limiting/)
-- [App Migration Rate Limiting](https://developer.atlassian.com/platform/app-migration/rate-limiting/)
-
-## Using Project Metadata
-
-### When Calling MCP Tools
-
-```typescript
-// Load project metadata
-const projectMeta = JSON.parse(
-  fs.readFileSync('.kiro/project.json', 'utf-8')
-);
-
-// Use with MCP tools
-confluence_create_page({
-  space: "PRD",
-  title: `[${projectMeta.projectName}] ...`,
-  labels: [...projectMeta.confluenceLabels, ...additionalLabels]
-});
-```
-
-## Troubleshooting
-
-### MCP Connection Error
-
-1. Restart Cursor
-2. Verify credentials in `~/.cursor/mcp.json`
-3. Check Atlassian API Token validity
-
-### Rate Limit Error
-
-Use rate-limit-ready scripts:
-```bash
-# Rate limit handling (500ms wait) implemented
-npm run confluence:sync <feature>
-npm run jira:sync <feature>
-
-# Adjust wait time (default: 500ms, in milliseconds)
-ATLASSIAN_REQUEST_DELAY=1000 npm run jira:sync <feature>
-```
-
-### Page Creation Error
-
-- Verify Confluence space exists
-- Check for duplicate page titles
-- Verify permissions