chore(rebar): Pier_T_rebar 작업 폴더 초기 구성 및 외부 의존 파일 통합

- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환 - Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용 - pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관) - worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md) - D:\Rhino-MCP 경로 참조를 새 위치로 치환 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-28 11:20:18 +09:00
commit 964a841de1
@@ -0,0 +1,324 @@
+---
+name: agent-version-analysis
+classification: workflow
+classification-reason: Orchestrates multi-phase research and analysis pipeline independent of model capability
+deprecation-risk: none
+description: |
+  CC CLI version upgrade impact analysis — research changes, analyze hmcmkit impact, generate report.
+  Triggers: agent-version-analysis, CC upgrade, version analysis, Agent 버전 분석, 버전 영향.
+argument-hint: "[from_version] [to_version]"
+user-invocable: true
+
+agents:
+  research: hmcmkit:agent-version-researcher
+  analyze: hmcmkit:hmcmkit-impact-analyst
+  brainstorm: null
+  report: hmcmkit:report-generator
+  default: null
+
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Glob
+  - Grep
+  - Bash
+  - Task
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
+  - AskUserQuestion
+  - Agent
+  - WebSearch
+  - WebFetch
+
+imports:
+  - ${PLUGIN_ROOT}/templates/agent-version-analysis.template.md
+  - ${PLUGIN_ROOT}/templates/plan-plus.template.md
+  - ${PLUGIN_ROOT}/templates/report.template.md
+
+next-skill: pdca plan
+pdca-phase: null
+task-template: "[CC-Version-Analysis] CC v{from} → v{to}"
+
+hooks:
+  Stop:
+    - type: command
+      command: "node ${HMCMKIT_PLUGIN_ROOT}/scripts/unified-stop.js"
+      timeout: 10000
+---
+
+# CC Version Analysis — Antigravity Platform CLI 버전 영향 분석 워크플로우
+
+> CC CLI 버전 업그레이드 시 hmcmkit plugin에 대한 영향을 체계적으로 조사, 분석하고
+> 개선 기회를 도출하는 전문 워크플로우 스킬.
+
+## Overview
+
+이 스킬은 CC CLI의 새 버전이 출시되었을 때 다음을 자동화합니다:
+
+1. **Phase 1 (Research)**: CC 변경사항 심층 조사
+2. **Phase 2 (Analyze)**: hmcmkit 아키텍처 영향 분석
+3. **Phase 3 (Brainstorm)**: Plan Plus 브레인스토밍으로 개선안 도출
+4. **Phase 4 (Report)**: 종합 영향 분석 보고서 작성
+
+**Agent Team 구성**:
+- `agent-version-researcher`: Agent 버전 변경사항 외부 조사
+- `hmcmkit-impact-analyst`: hmcmkit 내부 아키텍처 영향 분석
+- `report-generator`: 최종 보고서 생성
+
+## HARD-GATE
+
+<HARD-GATE>
+Do NOT skip any phase. Each phase produces artifacts that feed into the next.
+Do NOT generate the final report without completing Research and Analysis phases.
+Do NOT implement any ENH items — this skill is analysis-only.
+All documents MUST be written in Korean (한국어).
+</HARD-GATE>
+
+## Invocation
+
+```
+/agent-version-analysis                    # Auto-detect: installed vs latest
+/agent-version-analysis 2.1.78 2.1.85     # Specific version range
+/agent-version-analysis to 2.1.85         # From current installed to target
+```
+
+## Process Flow
+
+```
+┌─────────────────────────────────────────────────────┐
+│                CC Version Analysis                   │
+├─────────────────────────────────────────────────────┤
+│                                                      │
+│  Phase 0: Setup & Version Detection                  │
+│  ├── Detect installed CC version (ai-agent --version)  │
+│  ├── Determine target version (args or latest)       │
+│  ├── Create Task tracking structure                  │
+│  └── Load previous analysis from memory              │
+│                                                      │
+│  Phase 1: Research (agent-version-researcher agent)     │
+│  ├── Official docs (code.ai-agent.com)                 │
+│  ├── GitHub (anthropics/ai-agent-code)                 │
+│  │   ├── Releases & changelog                        │
+│  │   ├── Issues (open & recently closed)             │
+│  │   ├── PRs (merged in version range)               │
+│  │   └── Commits (significant changes)               │
+│  ├── npm registry (@anthropic-ai/ai-agent-code)        │
+│  ├── Technical blogs & community                     │
+│  └── Output: CC Change Report (structured)           │
+│                                                      │
+│  Phase 2: Analyze (hmcmkit-impact-analyst agent)        │
+│  ├── Map CC changes → hmcmkit components                │
+│  ├── Identify ENH opportunities                      │
+│  ├── File impact matrix                              │
+│  ├── Philosophy compliance check                     │
+│  ├── Test impact assessment                          │
+│  └── Output: hmcmkit Impact Analysis (structured)       │
+│                                                      │
+│  Phase 3: Brainstorm (Plan Plus methodology)         │
+│  ├── Intent discovery (핵심 목표/리스크/기회)         │
+│  ├── Alternative exploration                         │
+│  ├── YAGNI review (각 ENH 필요성 검증)               │
+│  ├── Priority assignment (P0~P3)                     │
+│  └── Output: Prioritized ENH roadmap                 │
+│                                                      │
+│  Phase 4: Report Generation                          │
+│  ├── Merge all phase outputs                         │
+│  ├── Generate from template                          │
+│  │   (agent-version-analysis.template.md)               │
+│  ├── Save to docs/04-report/features/                │
+│  ├── Update MEMORY.md (version history)              │
+│  └── Output: Final Impact Report (Korean)            │
+│                                                      │
+└─────────────────────────────────────────────────────┘
+```
+
+## Phase Details
+
+### Phase 0: Setup & Version Detection
+
+```
+1. Detect installed CC version:
+   $ ai-agent --version
+
+2. Determine target version:
+   - If args provided: use specified versions
+   - If no args: search for latest available version
+
+3. Create Task structure:
+   TaskCreate: "[CC-Version-Analysis] CC v{from} → v{to}"
+     ├── Task: "Phase 1: CC 변경사항 조사"
+     ├── Task: "Phase 2: hmcmkit 영향 분석"
+     ├── Task: "Phase 3: Plan Plus 브레인스토밍"
+     └── Task: "Phase 4: 보고서 작성"
+
+4. Load previous analysis context:
+   - Read memory/cc_version_history_*.md
+   - Read last ENH number from MEMORY.md
+   - Read existing PDCA status from .hmcmkit/state/pdca-status.json
+```
+
+### Phase 1: Research (Agent: agent-version-researcher)
+
+**Input**: from_version, to_version
+**Output**: Structured CC Change Report
+
+Launch the `agent-version-researcher` agent with:
+```
+Research CC CLI changes from v{from} to v{to}.
+Sources: official docs, GitHub (issues/PRs/releases), npm, blogs.
+Categorize by: Breaking/Feature/Fix/Performance/SystemPrompt/Hook/Config.
+Rate impact: HIGH/MEDIUM/LOW.
+Flag hmcmkit-relevant changes.
+Output structured markdown tables.
+```
+
+**Parallel research tasks** (when using Agent Team):
+- Task 1: GitHub releases + changelog
+- Task 2: GitHub issues (open + recently closed)
+- Task 3: Official docs changes
+- Task 4: System prompt diff analysis
+
+### Phase 2: Analyze (Agent: hmcmkit-impact-analyst)
+
+**Input**: Phase 1 CC Change Report
+**Output**: hmcmkit Impact Analysis
+
+Launch the `hmcmkit-impact-analyst` agent with:
+```
+Analyze hmcmkit impact from these CC changes: {phase1_output}
+Map each change to hmcmkit components (agents/skills/hooks/lib/scripts).
+Identify ENH opportunities starting from ENH-{last+1}.
+Check philosophy compliance (Automation First, No Guessing, Docs=Code).
+Assess test impact per ENH.
+```
+
+**Analysis scope**:
+- 29 agents: frontmatter compatibility
+- 31 skills: allowed-tools, hooks compatibility
+- 12 hook events: new events, changed behavior
+- 210 lib exports: API compatibility
+- 50 scripts: stdin/stdout protocol
+- 1,186 TCs: test coverage gaps
+
+### Phase 3: Brainstorm (Plan Plus Methodology)
+
+**Input**: Phase 2 Impact Analysis
+**Output**: Prioritized ENH Roadmap
+
+Apply Plan Plus brainstorming phases:
+
+#### 3.1 Intent Discovery
+Ask and answer:
+- 이 CC 업그레이드에서 hmcmkit이 얻을 수 있는 최대 가치는?
+- 놓치면 안 되는 critical change는?
+- 기존 workaround를 대체할 수 있는 native 기능은?
+
+#### 3.2 Alternative Exploration
+For each HIGH/MEDIUM ENH:
+- 구현 방법 A vs B vs C 비교
+- 최소 구현 (MVP) vs 완전 구현 trade-off
+- 다른 ENH와의 의존성/시너지
+
+#### 3.3 YAGNI Review
+Each ENH must pass:
+- ✅ 현재 사용자가 실제로 필요로 하는가?
+- ✅ 구현하지 않으면 어떤 문제가 발생하는가?
+- ✅ 다음 Agent 버전에서 더 나은 방법이 나올 가능성은?
+- ❌ YAGNI fail → P3 강등 또는 제거
+
+#### 3.4 Priority Assignment
+Final priority based on:
+- P0: Core PDCA workflow 직접 개선 또는 known pain point 해결
+- P1: 중요한 새 기능 활성화 또는 major DX 개선
+- P2: Nice-to-have, 문서 업데이트
+- P3: Cosmetic, minor optimization, future consideration
+
+### Phase 4: Report Generation
+
+**Input**: All phase outputs
+**Output**: Final Korean report in docs/
+
+1. **Generate report** from `agent-version-analysis.template.md`
+2. **Save to**: `docs/04-report/features/cc-v{from}-v{to}-impact-analysis.report.md`
+3. **Also create Plan** (if ENH count > 0):
+   `docs/01-plan/features/cc-v{from}-v{to}-impact-analysis.plan.md`
+4. **Update MEMORY.md**:
+   - CC version history section
+   - ENH number range
+   - Consecutive compatible releases count
+   - Open/closed GitHub issues
+5. **Update memory file**: `memory/cc_version_history_v{from}_v{to}.md`
+
+## Task Management Protocol
+
+All work MUST be tracked via Task Management System:
+
+```
+[CC-Version-Analysis] CC v{from} → v{to}          # Parent task
+├── [Research] Phase 1: CC 변경사항 조사             # agent-version-researcher
+│   ├── GitHub releases 조사
+│   ├── GitHub issues 조사
+│   ├── 공식 문서 변경 조사
+│   └── 시스템 프롬프트 변경 분석
+├── [Analyze] Phase 2: hmcmkit 영향 분석                # hmcmkit-impact-analyst
+│   ├── 컴포넌트 매핑
+│   ├── ENH 기회 식별
+│   ├── 파일 영향 매트릭스
+│   └── 철학 준수 검증
+├── [Brainstorm] Phase 3: 브레인스토밍               # Plan Plus
+│   ├── 의도 탐색
+│   ├── 대안 탐색
+│   └── YAGNI 검토
+└── [Report] Phase 4: 보고서 작성                    # report-generator
+    ├── 템플릿 기반 보고서 생성
+    ├── MEMORY.md 업데이트
+    └── 최종 검토
+```
+
+## Agent Team Configuration
+
+When invoked with CTO Team (`/pdca team`):
+
+| Role | Agent | Model | Task |
+|------|-------|-------|------|
+| Lead | cto-lead | leader-agent | Overall orchestration |
+| Researcher | agent-version-researcher | leader-agent | Phase 1: CC research |
+| Analyst | hmcmkit-impact-analyst | leader-agent | Phase 2: hmcmkit analysis |
+| Reporter | report-generator | helper-agent | Phase 4: Report writing |
+
+**Parallel execution**:
+- Phase 1 tasks can run in parallel (GitHub, docs, npm)
+- Phase 2 depends on Phase 1 completion
+- Phase 3 depends on Phase 2 completion
+- Phase 4 depends on Phase 3 completion
+
+## Quality Checklist
+
+Before completing, verify:
+
+- [ ] All CC changes from version range are captured
+- [ ] Every change has impact classification (HIGH/MEDIUM/LOW)
+- [ ] Every ENH has priority (P0/P1/P2/P3)
+- [ ] Philosophy compliance checked for all ENH items
+- [ ] File impact matrix is complete
+- [ ] Test impact assessed for all ENH items
+- [ ] Report is written in Korean
+- [ ] MEMORY.md is updated
+- [ ] Task tracking shows all items completed
+- [ ] Executive Summary includes 4-perspective value table
+
+## Previous Analysis Reference
+
+This skill builds on established analysis patterns:
+- `docs/04-report/features/ai-agent-code-v2172-impact-analysis.report.md`
+- `docs/04-report/features/ai-agent-code-v2178-impact-analysis.report.md`
+- `memory/cc_version_history_v2134_v2172.md`
+
+Always read previous reports first to maintain consistency in:
+- ENH numbering (continue from last used number)
+- Report structure and depth
+- Consecutive compatible release tracking
+- GitHub issues monitoring continuity