@sk8metal/michi-cli 0.0.9 → 0.1.0

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

@@ -0,0 +1,354 @@
+---
+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/cline/rules/atlassian-integration.md

@@ -0,0 +1,36 @@
+# Atlassian Integration Rules
+
+## Confluence Integration
+
+### Page Creation Format
+- Title: `[{{PROJECT_ID}}] {document_type}`
+- Labels: Use {{KIRO_DIR}}/project.json `confluenceLabels`
+- Space: Reference environment variables (CONFLUENCE_PRD_SPACE, etc.)
+
+### Content Sync
+- Source: GitHub {{KIRO_DIR}}/specs/
+- Destination: Confluence pages
+- Sync tool: `npm run confluence:sync`
+
+## JIRA Integration
+
+### Issue Creation Format
+- Summary: `[{{JIRA_KEY}}] {title}`
+- Project Key: Use {{KIRO_DIR}}/project.json `jiraProjectKey`
+- Labels: Derived from Confluence labels
+
+### Workflow
+1. Generate specs in GitHub
+2. Create JIRA epics/stories
+3. Link Confluence pages to JIRA issues
+
+## Environment Variables
+
+Required variables (from .env):
+- `ATLASSIAN_URL`
+- `ATLASSIAN_EMAIL`
+- `ATLASSIAN_API_TOKEN`
+- `JIRA_PROJECT_KEYS`
+- `CONFLUENCE_PRD_SPACE`
+- `CONFLUENCE_QA_SPACE`
+- `CONFLUENCE_RELEASE_SPACE`

package/templates/cline/rules/michi-core.md

@@ -0,0 +1,56 @@
+# Michi Core Principles
+
+## Development Guidelines
+{{DEV_GUIDELINES}}
+
+## Language
+All generated documents should be in: **{{LANG_CODE}}**
+
+Reference the language field in {{KIRO_DIR}}/project.json.
+
+## Single Source of Truth (SSoT)
+
+### GitHub as SSoT
+- **All specifications are managed in GitHub** ({{KIRO_DIR}}/specs/)
+- Confluence is **reference and approval only** (editing is GitHub only)
+- Avoid duplicate management
+
+### Data Flow
+```
+GitHub ({{KIRO_DIR}}/specs/)  ← Source of truth (editable)
+    ↓ sync
+Confluence ← Display and approval (read-only)
+```
+
+## Multi-Project Management
+
+### Project Identification
+- All operations reference {{KIRO_DIR}}/project.json
+- Dynamically use project ID, JIRA key, Confluence labels
+- Project ID: {{PROJECT_ID}}
+
+### Naming Conventions
+
+#### Confluence Pages
+- Format: `[{projectName}] {document_type}`
+- Example: `[{{PROJECT_ID}}] Requirements`
+
+#### JIRA Epic/Story
+- Format: `[{JIRA_KEY}] {title}`
+- Use project metadata from {{KIRO_DIR}}/project.json
+
+## Project Structure
+
+- Project metadata: {{KIRO_DIR}}/project.json
+- Specifications: {{KIRO_DIR}}/specs/
+- Templates: {{KIRO_DIR}}/settings/templates/
+- Steering: {{KIRO_DIR}}/steering/
+- Rules: {{AGENT_DIR}}/rules/
+
+## Best Practices
+
+1. **Always reference project.json** for project-specific metadata
+2. **Use SSoT principle** - Edit in GitHub, reference in Confluence
+3. **Follow naming conventions** for consistency
+4. **Generate specs incrementally** - Requirements → Design → Tasks
+5. **Commit frequently** to GitHub

package/templates/codex/AGENTS.override.md

@@ -0,0 +1,277 @@
+# AGENTS.override.md - Michi Project Extensions
+
+このファイルはcc-sddのAGENTS.mdを拡張し、Michi固有のワークフローとルールを追加します。
+
+## Michi Overview
+
+**Michi**は、AI駆動開発を支援するプロジェクト管理・ドキュメント管理フレームワークです。Claude Code、Cursor、Codex CLI、Claude Agent SDKと統合し、効率的な開発フローを実現します。
+
+- **Repository**: https://github.com/sk8metalme/michi
+- **Documentation**: `docs/user-guide/`
+- **License**: MIT
+
+---
+
+## Michi-Specific Workflows
+
+### 1. Confluence Integration
+
+#### Confluence同期コマンド
+```bash
+/prompts:confluence-sync FEATURE=<機能名>
+```
+
+#### 必要な環境変数
+```bash
+ATLASSIAN_URL=https://your-domain.atlassian.net
+ATLASSIAN_EMAIL=your-email@example.com
+ATLASSIAN_API_TOKEN=your-api-token
+```
+
+#### プロジェクト設定
+`.kiro/project.json`に以下を設定：
+```json
+{
+  "confluenceSpaceKey": "YOUR_SPACE",
+  "confluenceLabels": ["ai-development", "michi"]
+}
+```
+
+#### 同期対象
+- 要件定義書（requirements.md）→ Confluenceページ
+- 設計書（design.md）→ Confluenceページ
+- タスク一覧（tasks.md）→ Confluenceページ（オプション）
+
+---
+
+### 2. JIRA Integration
+
+#### プロジェクトキー設定
+`.kiro/project.json`の`jiraProjectKey`を使用してJIRAチケットを管理：
+```json
+{
+  "jiraProjectKey": "MYPROJ"
+}
+```
+
+#### リリース管理
+- JIRAでリリースバージョンを作成
+- Confluenceでリリース手順書を管理
+- GitHub Releasesと連携
+
+---
+
+### 3. Multi-Language Support
+
+Michiは以下の言語とビルドツールをサポート：
+
+| 言語 | ビルドツール | テストコマンド |
+|------|------------|---------------|
+| Node.js/TypeScript | npm | `npm test` |
+| Java | **Gradle のみ** | `./gradlew test` |
+| PHP | Composer | `composer test` |
+
+**重要:** Javaプロジェクトでは**Gradleのみ**を使用してください。Mavenは使用しません。
+
+---
+
+### 4. Test Strategy - Master Test Approach
+
+Michiは**マスタテスト方式**を採用しています：
+
+#### 基本原則
+- テストは常に最新の仕様を反映（phase-0、phase-1のような履歴管理はしない）
+- 仕様変更時は既存のテストファイルを更新
+- テスト実行時間を一定に保つ
+
+#### Phase構成
+- **Phase A**: PR時に自動実行
+  - Unit tests
+  - Lint
+  - Build
+- **Phase B**: リリース前に手動実行
+  - Integration tests
+  - E2E tests
+  - Performance tests
+  - Security tests
+
+#### テストカバレッジ
+- 目標: **95%以上**
+- テストは仕様として扱う
+- 実装に合わせてテストを変更しない（仕様通りでない場合のみ修正）
+
+---
+
+### 5. CI/CD Integration
+
+#### サポート対象
+- **GitHub Actions**
+- **Screwdriver**
+
+#### 推奨ワークフロー
+```yaml
+# .github/workflows/ci.yml
+name: CI
+on: [pull_request]
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - name: Run Phase A Tests
+        run: |
+          npm install
+          npm run test:unit
+          npm run lint
+          npm run build
+```
+
+---
+
+### 6. Release Flow
+
+#### セマンティックバージョニング
+```
+v<major>.<minor>.<patch>
+例: v1.2.3
+```
+
+#### リリース手順
+1. **Confluenceでリリース手順書作成**
+   - テンプレート: `.kiro/templates/release-procedure.md`
+2. **JIRAでリリースチケット起票**
+   - チケットタイプ: Release
+   - バージョン: 自動生成
+3. **GitHub Releaseの作成**
+   - リリースノート自動生成
+   - タグ付け
+
+---
+
+## Coding Standards
+
+### TypeScript/Node.js
+- **Style Guide**: Airbnb JavaScript Style Guide準拠
+- **Linter**: ESLint
+- **Formatter**: Prettier
+- **Type Checking**: `tsc --noEmit`
+
+### Java (Gradle)
+- **Style Guide**: Google Java Style Guide
+- **Build Tool**: Gradle 8.x
+- **Test Framework**: JUnit 5
+- **Coverage**: JaCoCo
+
+### PHP
+- **Style Guide**: PSR-12
+- **Build Tool**: Composer
+- **Test Framework**: PHPUnit
+- **Static Analysis**: PHPStan
+
+---
+
+## File Structure Standards
+
+### .kiro/ Directory
+```
+.kiro/
+├── project.json              # プロジェクトメタデータ
+├── specs/                    # 機能仕様（cc-sdd管理）
+│   └── {feature}/
+│       ├── requirements.md
+│       ├── design.md
+│       ├── tasks.md
+│       └── spec.json
+├── steering/                 # AI指導ルール（cc-sdd管理）
+│   ├── structure.md
+│   ├── tech.md
+│   └── product.md
+└── settings/                 # 共通ルール（cc-sdd管理）
+```
+
+### Michi Extensions
+```
+.kiro/
+├── project.json              # ⭐ Michi固有
+└── templates/                # ⭐ Michi固有
+    ├── confluence-page.md
+    ├── jira-ticket.md
+    └── release-procedure.md
+```
+
+---
+
+## Security Policy
+
+### 環境変数管理
+- **絶対禁止**: APIキー、トークンのハードコード
+- **推奨**: `.env`ファイル + `.gitignore`
+- **CI/CD**: GitHub Secrets / Screwdriver Secrets
+
+### 依存関係管理
+- 定期的な脆弱性スキャン（`npm audit`, `snyk`）
+- 依存ライブラリの最小化
+- 信頼できるソースからのみダウンロード
+
+---
+
+## Workflow Integration
+
+### cc-sdd + Michi 連携フロー
+
+1. **プロジェクト初期化**
+   ```bash
+   # cc-sddインストール
+   npx cc-sdd@latest --codex --lang ja
+
+   # Michi拡張インストール
+   npx michi setup --codex
+   ```
+
+2. **仕様作成（cc-sdd）**
+   ```bash
+   /kiro:spec-init FEATURE=user-auth
+   /kiro:spec-requirements FEATURE=user-auth
+   /kiro:spec-design FEATURE=user-auth
+   ```
+
+3. **Confluence同期（Michi）**
+   ```bash
+   /prompts:confluence-sync FEATURE=user-auth
+   ```
+
+4. **実装とテスト（cc-sdd + TDD）**
+   ```bash
+   /kiro:spec-tasks FEATURE=user-auth
+   /kiro:spec-impl FEATURE=user-auth
+   ```
+
+5. **検証（cc-sdd）**
+   ```bash
+   /kiro:validate-impl FEATURE=user-auth
+   ```
+
+---
+
+## Communication Guidelines
+
+### 日本語優先
+- コミュニケーションは日本語を基本とする
+- 技術用語は適切に英語/日本語を使い分ける
+
+### 質問と確認
+- 不明な点は必ず質問し精度を高めることを最優先する
+- AskUserQuestionツールを積極的に活用
+
+---
+
+## Reference Links
+
+- [Michi Documentation](https://github.com/sk8metalme/michi/tree/main/docs)
+- [cc-sdd Documentation](https://github.com/gotalab/cc-sdd)
+- [Confluence API](https://developer.atlassian.com/cloud/confluence/rest/v2/)
+- [JIRA API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/)
+
+---
+
+**Note**: このファイルはCodex CLIの`AGENTS.md`を上書き（override）するものではなく、cc-sddの基本ルールに**追加**される形で適用されます。