@sk8metal/michi-cli 0.0.7 → 0.0.9

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

@@ -0,0 +1,76 @@
+---
+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

@@ -0,0 +1,69 @@
+---
+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

@@ -0,0 +1,188 @@
+---
+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

package/templates/cursor/rules/github-ssot.mdc

@@ -0,0 +1,151 @@
+---
+title: GitHub Single Source of Truth Rules
+description: {{DEV_GUIDELINES}} for using GitHub as SSoT and syncing with Confluence
+---
+
+# GitHub Single Source of Truth (SSoT) Rules
+
+## Basic Principles
+
+### Single Source of Truth
+- **All specifications managed in GitHub** (.kiro/specs/)
+- Confluence is **for reference and approval only** (edit only in GitHub)
+- Avoid dual management
+
+### Data Flow
+```
+GitHub (.kiro/specs/)  ← Source of Truth (editable)
+    ↓ sync
+Confluence ← View & Approval only (read-only)
+```
+
+## File Structure
+
+### GitHub Repository
+```
+.kiro/
+├── project.json          # Project metadata
+├── specs/
+│   └── <feature>/
+│       ├── requirements.md  # Requirements definition
+│       ├── design.md        # Design
+│       ├── tasks.md         # Task breakdown
+│       └── test-report.md   # Test results
+└── settings/
+    └── templates/       # Templates
+```
+
+## Workflow
+
+### 1. Generate Markdown → GitHub
+```
+Cursor: /michi:spec-requirements <feature>
+  ↓ Generate: .kiro/specs/<feature>/requirements.md
+  ↓
+jj commit -m "docs: Add requirements"
+jj git push
+```
+
+### 2. GitHub → Confluence Sync
+```
+Cursor AI (using MCP):
+  1. Get GitHub URL
+  2. Convert Markdown → Confluence Storage Format
+  3. Create page with confluence_create_page()
+  4. Embed GitHub link
+```
+
+### 3. Approval in Confluence
+- Planners/Managers review in Confluence
+- Approve via Page Properties
+- After approval → Proceed to next phase
+
+### 4. Technical Review in GitHub
+- Engineers review Markdown in GitHub
+- Comment/suggest changes in PR format (optional)
+- After merge, auto-update Confluence
+
+## Confluence Page Structure
+
+### Template Structure
+```markdown
+## GitHub Integration
+📄 Latest version managed in [GitHub](URL)
+Edit in GitHub, auto-synced to Confluence
+
+---
+
+{Converted Markdown}
+
+---
+
+## Approval
+{approval macro}
+Approvers: @Planner, @Manager
+{/approval}
+```
+
+## Review Flow Separation
+
+### Engineer Review (GitHub)
+- Target: requirements.md, design.md, tasks.md
+- Method: GitHub PR, comments
+- Focus: Technical accuracy, feasibility
+
+### Planner/Manager Review (Confluence)
+- Target: Requirements, design, estimates
+- Method: Confluence comments, approval macro
+- Focus: Business requirements, priority, budget
+
+## Update Synchronization
+
+### On GitHub Update
+```
+GitHub push
+  ↓ Webhook (optional)
+Confluence auto-update
+```
+
+### Manual Sync
+```bash
+# Run command
+/michi:confluence-sync <feature>
+
+# Or npm script
+npm run confluence:sync <feature>
+```
+
+## Benefits
+
+✅ **Version Control**: All change history in GitHub
+✅ **Zero Dual Management**: Confluence for reference only
+✅ **Engineer-Friendly**: Markdown, Git, PR
+✅ **Planner/Manager-Friendly**: Confluence's user-friendly UI
+✅ **Auto Sync**: Push = Confluence update
+✅ **Audit Trail**: GitHub as official record
+
+## Prohibited Actions
+
+❌ Direct editing in Confluence
+❌ Managing in both GitHub and Confluence
+❌ Reverse sync from Confluence to GitHub
+
+## Exception Cases
+
+Direct creation in Confluence allowed only for:
+- Meeting minutes
+- Temporary notes
+- Documents outside the project
+
+## Troubleshooting
+
+### If Confluence is outdated
+```bash
+# Manually re-sync
+/michi:confluence-sync <feature>
+```
+
+### On sync error
+1. Verify GitHub Markdown is correct
+2. Check Confluence API authentication
+3. Verify page ID is correct

package/templates/cursor/rules/multi-project.mdc

@@ -0,0 +1,81 @@
+---
+title: Multi-Project Management Rules
+description: {{DEV_GUIDELINES}} for managing multiple concurrent projects with naming conventions and workflows
+---
+
+# Multi-Project Management Rules
+
+## Project Identification
+
+### Loading Project Metadata
+- Reference `.kiro/project.json` in all operations
+- Retrieve project ID, JIRA key, and Confluence labels
+- Use project information dynamically
+
+### Example
+```typescript
+const projectMeta = JSON.parse(fs.readFileSync('.kiro/project.json', 'utf8'));
+// projectMeta.projectId
+// projectMeta.jiraProjectKey
+// projectMeta.confluenceLabels
+```
+
+## Naming Conventions
+
+### Confluence Pages
+- Format: `[{projectName}] {document_type}`
+- Example: `[Company-A-Service1] Requirements`
+- Example: `[{{PROJECT_ID}}] User Auth Design`
+
+### JIRA Epic/Story
+- Epic: `[{projectName}] {feature_name}`
+- Story: `[{projectName}] {task_name}`
+- Example: `[{{PROJECT_ID}}] User Authentication Feature`
+
+### GitHub Branches
+- Format: `{projectId}/feature/{feature_name}`
+- Example: `{{PROJECT_ID}}/feature/user-auth`
+- Example: `customer-a-service-1/feature/payment`
+
+### Label Assignment
+- Confluence: `projectMeta.confluenceLabels` + `requirements|design|tasks`
+- JIRA: `projectMeta.confluenceLabels` + feature name
+
+## Cross-Project Views
+
+### Confluence Dashboard
+- Display requirements, design, tasks across all projects
+- Filter by labels
+- Filter by status (Pending Review, Approved)
+
+### JIRA Dashboard
+- Track progress by project key
+- Filter: `project IN ({{JIRA_PROJECT_KEY}}, PRJA, PRJB)`
+- Aggregate story points
+
+## Unified Workflow
+
+Use the same workflow across all projects:
+
+1. `/michi:spec-init` → Specification initialization
+2. `/michi:spec-requirements` → Requirements definition (Confluence sync)
+3. `/michi:spec-design` → Design (Confluence sync + estimation)
+4. `/michi:spec-tasks` → Task breakdown (JIRA integration)
+5. `/michi:spec-impl` → TDD implementation
+6. GitHub PR → Review
+7. Release preparation
+
+## Project Switching
+
+When switching between multiple projects:
+
+1. Check out repository
+2. Verify `.kiro/project.json`
+3. Open corresponding Confluence/JIRA pages
+
+## Important Notes
+
+- Maintain independent `.kiro/project.json` for each project
+- Ensure JIRA project keys are unique
+- Identify projects by Confluence labels
+- Include project ID in GitHub branch names

package/scripts/setup-env.sh

@@ -1,52 +0,0 @@
-#!/bin/bash
-
-# 環境変数設定スクリプト
-# このスクリプトは.envファイルのテンプレートを作成します
-
-# 既存の.envファイルがある場合は確認
-if [ -f .env ]; then
-  echo "⚠️  .env ファイルが既に存在します"
-  read -p "上書きしますか？ (y/N): " -n 1 -r
-  echo
-  if [[ ! $REPLY =~ ^[Yy]$ ]]; then
-    echo "キャンセルしました"
-    exit 0
-  fi
-fi
-
-cat > .env << 'EOF'
-# Atlassian設定（MCP + REST API共通）
-ATLASSIAN_URL=https://your-domain.atlassian.net
-ATLASSIAN_EMAIL=your-email@company.com
-ATLASSIAN_API_TOKEN=your-token-here
-
-# GitHub設定
-GITHUB_ORG=your-org
-GITHUB_TOKEN=ghp_xxx
-GITHUB_REPO=sk8metalme/michi
-
-# Confluence共有スペース
-CONFLUENCE_PRD_SPACE=PRD
-CONFLUENCE_QA_SPACE=QA
-CONFLUENCE_RELEASE_SPACE=RELEASE
-
-# JIRAプロジェクトキー（カンマ区切り）
-JIRA_PROJECT_KEYS=MICHI,PRJA,PRJB
-
-# Slack通知用（オプション）
-SLACK_WEBHOOK_URL=https://hooks.slack.com/xxx
-EOF
-
-# セキュアなパーミッション設定（所有者のみ読み取り/書き込み可能）
-chmod 600 .env
-
-echo "✅ .env ファイルが作成されました"
-echo "✅ パーミッション 600 を設定しました（所有者のみ読み取り/書き込み可能）"
-echo ""
-echo "⚠️  重要: .env ファイルをGitにコミットしないでください"
-echo "   .gitignore で除外されていることを確認してください"
-echo ""
-echo "📝 次のステップ:"
-echo "   1. 実際の認証情報で .env の値を更新してください"
-echo "   2. セットアップ手順に従ってください"
-