agestra 4.11.0 → 4.12.1

package/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "agestra",
       "source": "./",
       "description": "Orchestrate Ollama, Gemini, and Codex for multi-AI debates, code review, and cross-validation",
-      "version": "4.11.0",
+      "version": "4.12.1",
       "author": {
         "name": "mua-vtuber"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "agestra",
-  "version": "4.11.0",
+  "version": "4.12.1",
   "description": "Claude Code plugin — orchestrate Ollama, Gemini, and Codex for multi-AI debates, code review, and cross-validation",
   "mcpServers": {
     "agestra": {

package/.gemini/commands/agestra/design.toml

@@ -9,7 +9,7 @@ Use the shared workflow spec below as the source of truth and adapt it to the cu
 @{commands/design.md}
 
 Gemini-specific rules:
-- Start with `environment_check` and `provider_list`.
+- Start with `setup_status`, then `environment_check` and `provider_list`.
 - Prefer Agestra MCP tools, workspace documents, and debate flows over free-form brainstorming.
 - Translate Claude-specific wording into leader-host wording when Gemini is the active host.
 - Keep the final answer in the user's language.

package/.gemini/commands/agestra/implement.toml

@@ -9,8 +9,9 @@ Use the shared workflow spec below as the source of truth and adapt it to the cu
 @{commands/implement.md}
 
 Gemini-specific rules:
-- Start with `environment_check` and `provider_list`.
+- Start with `setup_status`, then `environment_check` and `provider_list`.
 - Prefer Agestra MCP tools and worker orchestration over ad-hoc shell-heavy implementation plans.
-- Translate Claude-specific wording into leader-host wording when Gemini is the active host.
+- Treat "Leader-host only" as the Gemini-led local path when Gemini is the active host.
+- Use the shared `agestra-implementer` role semantics for host-local code edits.
 - Keep the final answer in the user's language.
 """

package/AGENTS.md

@@ -13,7 +13,7 @@ This repository includes a Codex-friendly host wrapper for Agestra.
 - Treat `commands/*.md` as the source of truth for Agestra workflows.
 - When the user asks for review, design, idea, or implementation help, start with `environment_check` and `provider_list`.
 - Prefer Agestra MCP tools over ad-hoc multi-provider prompting.
-- If a workflow mentions "Claude only", interpret that as the current leader-host-only path when Claude is not the active host.
+- If any legacy workflow text mentions "Claude only", interpret that as the current leader-host-only path when Claude is not the active host.
 
 ## Workflow Mapping
 

package/GEMINI.md

@@ -24,7 +24,7 @@ Each command delegates to the shared workflow specs in `commands/*.md`.
 - Start orchestration requests with `environment_check` and `provider_list`.
 - Prefer Agestra MCP tools instead of rebuilding workflows in free-form prompts.
 - Treat `commands/*.md` and `agents/*.md` as the canonical workflow and role assets.
-- If a shared workflow mentions "Claude only", translate that to the current leader-host-only path when Gemini is the active host.
+- If any legacy shared workflow text mentions "Claude only", translate that to the current leader-host-only path when Gemini is the active host.
 
 ## Core MCP Tools
 

package/README.ja.md

@@ -24,22 +24,37 @@ Claude では既存のプラグイン UX をそのまま維持します。Agestr
 
 ```
 npm run bundle
-npm run install:codex
+npm run install:codex:assets
 ```
 
-Codex ではリポジトリ直下の [AGENTS.md](AGENTS.md) と、登録済みの `agestra` MCP サーバーを一緒に使います。
+グローバル npm パッケージから使う場合:
+
+```
+npm install -g agestra
+agestra-install codex --assets
+```
+
+Codex ではリポジトリ直下の [AGENTS.md](AGENTS.md) と、登録済みの `agestra` MCP サーバーを一緒に使います。`--assets` は `.codex/agents/` に生成済み Codex custom agent もインストールし、Agestra host-asset manifest に記録します。MCP 登録だけでよい場合は `npm run install:codex` または `agestra-install codex` を使ってください。
 
 ### Gemini CLI
 
 ```
 npm run bundle
-npm run install:gemini
+npm run install:gemini:assets
 ```
 
-Gemini ではリポジトリ直下の [GEMINI.md](GEMINI.md) と、[`.gemini/commands/agestra/`](.gemini/commands/agestra) のプロジェクトコマンドを一緒に使います。
+グローバル npm パッケージから使う場合:
+
+```
+npm install -g agestra
+agestra-install gemini --assets --scope user
+```
+
+Gemini ではリポジトリ直下の [GEMINI.md](GEMINI.md) と、[`.gemini/commands/agestra/`](.gemini/commands/agestra) のプロジェクトコマンドを一緒に使います。user scope の `--assets` は Agestra Gemini native extension をインストールします。MCP 登録だけでよい場合は `npm run install:gemini` または `agestra-install gemini` を使ってください。
 
 セットアップ後に利用できる Gemini コマンド:
 
+- `/agestra:setup`
 - `/agestra:review`
 - `/agestra:design`
 - `/agestra:idea`
@@ -84,7 +99,7 @@ Gemini ではリポジトリ直下の [GEMINI.md](GEMINI.md) と、[`.gemini/com
 | `/agestra setup` | 初期 AI プロバイダー選択とセットアップ |
 | `/agestra implement [task]` | Claude only または Multi-AI モードで実装を進める |
 
-外部プロバイダーが利用可能な場合、テキストコマンド（review、design、idea）は直接ディベートモードに入り、マルチ AI クロスバリデーションを行います。プロバイダーが検出されない場合、Claude が自動的に単独で作業します。
+外部プロバイダーが利用可能な場合、テキストコマンド（review、design、idea）は直接徹底討論モードに入り、マルチ AI クロスバリデーションを行います。プロバイダーが検出されない場合、Claude が自動的に単独で作業します。
 
 ## エージェント
 
@@ -106,8 +121,11 @@ Gemini ではリポジトリ直下の [GEMINI.md](GEMINI.md) と、[`.gemini/com
 | `cancel` | ワーカー、ディベート、チェーン、タスクの安全な停止 |
 | `build-fix` | build/typecheck/lint エラーの自動診断と修正 |
 | `trace` | エージェント実行タイムラインとフローダイアグラムの表示 |
+| `setup` | 初期プロバイダー選択と `providers.config.json` 書き込み |
 | `design` | Multi-AI モード選択を含む設計探索ワークフロー |
 | `idea` | Multi-AI モード選択を含む改善案発見ワークフロー |
+| `review` | Multi-AI モード選択を含むコード品質・セキュリティ・ハードコーディングレビューワークフロー |
+| `leader` | マルチAI/プロバイダーオーケストレーションのエントリーポイント — 明示的なプロバイダー、ディベート、合意形成、相互検証シグナルを検知し、ドメイン分類後 `agestra-team-lead` へ委譲 |
 
 ---
 
@@ -137,7 +155,7 @@ Turborepo モノレポで、9 パッケージ構成です:
 
 ### 作業モード
 
-**Text work**（レビュー、設計、アイデア）: プロバイダーあり → ディベートモード; なし → Claude only
+**Text work**（レビュー、設計、アイデア）: プロバイダーあり → 徹底討論モード; なし → Claude only
 
 **Implementation work**（team-lead orchestration）:
 - **Claude만으로** — Claude がプロジェクト/グローバルエージェントを使って直接実装します。
@@ -314,15 +332,20 @@ agestra/
 │   ├── worker-manage.md     # CLI ワーカー管理
 │   ├── cancel.md            # 安全な操作キャンセル
 │   ├── build-fix.md         # ビルドエラー自動修復
-│   └── trace.md             # 実行タイムラインビューア
+│   ├── trace.md             # 実行タイムラインビューア
+│   ├── setup.md             # 初期プロバイダー選択
+│   ├── design.md            # 設計探索ワークフロー
+│   ├── idea.md              # 改善案発見ワークフロー
+│   ├── review.md            # コード品質レビューワークフロー
+│   └── leader.md            # マルチAIオーケストレーションルーター
 ├── hooks/
 │   └── user-prompt-submit.md  # ツール推奨フック
 ├── dist/
 │   └── bundle.js            # 単一ファイル MCP サーバーバンドル
 ├── scripts/
 │   ├── bundle.mjs           # esbuild バンドルスクリプト
-│   ├── install-host-mcp.mjs # Codex/Gemini に Agestra を登録
-│   └── uninstall-host-mcp.mjs # Codex/Gemini から Agestra 登録を削除
+│   ├── install-host-mcp.mjs # Claude/Codex/Gemini の MCP + host assets を登録
+│   └── uninstall-host-mcp.mjs # ホスト登録と管理対象 assets を削除
 ├── packages/
 │   ├── core/                # AIProvider、レジストリ、セキュリティ、ワーカー
 │   ├── provider-ollama/     # Ollama HTTP アダプター
@@ -355,14 +378,18 @@ Codex CLI:
 
 ```
 npm run uninstall:codex
+npm run uninstall:codex:assets
 ```
 
 Gemini CLI:
 
 ```
 npm run uninstall:gemini
+npm run uninstall:gemini:assets
 ```
 
+`*:assets` のアンインストールは、ホスト登録と未変更の生成済みホスト資産を一緒に削除します。ユーザーが生成済み資産を編集していた場合、Agestra はそのファイルを残して報告します。グローバル npm インストールでは `agestra-uninstall codex --assets` または `agestra-uninstall gemini --assets --scope user` を使ってください。
+
 生成済みのプロジェクトデータも削除したい場合は、`.agestra/` ディレクトリを手動で削除してください。
 
 ---

package/README.ko.md

@@ -26,23 +26,23 @@ Claude는 기존 플러그인 설치 UX를 그대로 유지합니다. Agestra가
 
 ```
 npm run bundle
-npm run install:codex
+npm run install:codex:assets
 ```
 
 전역 npm 패키지 기준:
 
 ```
 npm install -g agestra
-agestra-install codex
+agestra-install codex --assets
 ```
 
-저장소에서 작업 중이지만 등록 대상은 전역 npm 패키지로 하고 싶다면:
+저장소에서 작업 중이지만 전역 npm 패키지를 MCP만 등록하고 싶다면:
 
 ```
 npm run install:codex:global
 ```
 
-Codex는 저장소 루트의 [AGENTS.md](AGENTS.md)와 등록된 `agestra` MCP 서버를 함께 사용합니다.
+Codex는 저장소 루트의 [AGENTS.md](AGENTS.md)와 등록된 `agestra` MCP 서버를 함께 사용합니다. `--assets` 경로는 `.codex/agents/` 아래에 생성형 Codex custom agent도 설치하고 Agestra host-asset manifest에 기록합니다. MCP만 등록하려면 `npm run install:codex` 또는 `agestra-install codex`를 사용하세요.
 
 ### Gemini CLI
 
@@ -50,23 +50,23 @@ Codex는 저장소 루트의 [AGENTS.md](AGENTS.md)와 등록된 `agestra` MCP
 
 ```
 npm run bundle
-npm run install:gemini
+npm run install:gemini:assets
 ```
 
 전역 npm 패키지 기준:
 
 ```
 npm install -g agestra
-agestra-install gemini
+agestra-install gemini --assets --scope user
 ```
 
-저장소에서 작업 중이지만 등록 대상은 전역 npm 패키지로 하고 싶다면:
+저장소에서 작업 중이지만 전역 npm 패키지를 MCP만 등록하고 싶다면:
 
 ```
 npm run install:gemini:global
 ```
 
-Gemini는 저장소 루트의 [GEMINI.md](GEMINI.md)와 [`.gemini/commands/agestra/`](.gemini/commands/agestra) 프로젝트 커맨드를 함께 사용합니다.
+Gemini는 저장소 루트의 [GEMINI.md](GEMINI.md)와 [`.gemini/commands/agestra/`](.gemini/commands/agestra) 프로젝트 커맨드를 함께 사용합니다. user scope의 `--assets` 경로는 Agestra Gemini native extension을 설치합니다. MCP만 등록하려면 `npm run install:gemini` 또는 `agestra-install gemini`를 사용하세요.
 
 설치 후 Gemini에서 사용할 수 있는 명령:
 
@@ -148,8 +148,11 @@ winget install BurntSushi.ripgrep.MSVC
 | `cancel` | 워커, 토론, 체인, 작업의 정상 종료 |
 | `build-fix` | 빌드/타입체크/린트 에러 자동 진단 및 수정 |
 | `trace` | 에이전트 실행 타임라인 및 흐름 다이어그램 조회 |
+| `setup` | 초기 공급자 선택 및 `providers.config.json` 작성 |
 | `design` | 멀티 AI 모드 선택이 포함된 아키텍처 탐색 워크플로우 |
 | `idea` | 멀티 AI 모드 선택이 포함된 개선점 발굴 워크플로우 |
+| `review` | 멀티 AI 모드 선택이 포함된 코드 품질·보안·하드코딩 리뷰 워크플로우 |
+| `leader` | 멀티 AI/프로바이더 오케스트레이션 진입점 — 명시적인 프로바이더, 토론, 합의, 교차 검증 신호를 잡아 도메인을 분류한 뒤 `agestra-team-lead`에 위임 |
 
 ---
 
@@ -357,15 +360,20 @@ agestra/
 │   ├── worker-manage.md     # CLI 워커 관리
 │   ├── cancel.md            # 정상 작업 취소
 │   ├── build-fix.md         # 빌드 에러 자동 수정
-│   └── trace.md             # 실행 타임라인 조회
+│   ├── trace.md             # 실행 타임라인 조회
+│   ├── setup.md             # 초기 공급자 선택
+│   ├── design.md            # 아키텍처 탐색 워크플로우
+│   ├── idea.md              # 개선점 발굴 워크플로우
+│   ├── review.md            # 코드 품질 리뷰 워크플로우
+│   └── leader.md            # 멀티 AI 오케스트레이션 라우터
 ├── hooks/
 │   └── user-prompt-submit.md  # 도구 추천 hook
 ├── dist/
 │   └── bundle.js            # 단일 파일 MCP 서버 번들
 ├── scripts/
 │   ├── bundle.mjs           # esbuild 번들 스크립트
-│   ├── install-host-mcp.mjs # Codex/Gemini에 Agestra 등록
-│   └── uninstall-host-mcp.mjs # Codex/Gemini에서 Agestra 제거
+│   ├── install-host-mcp.mjs # Claude/Codex/Gemini MCP + host assets 등록
+│   └── uninstall-host-mcp.mjs # 호스트 등록과 관리 자산 제거
 ├── packages/
 │   ├── core/                # AIProvider 인터페이스, 레지스트리, 보안, 워커
 │   ├── provider-ollama/     # Ollama HTTP 어댑터
@@ -398,14 +406,18 @@ Codex CLI:
 
 ```
 npm run uninstall:codex
+npm run uninstall:codex:assets
 ```
 
 Gemini CLI:
 
 ```
 npm run uninstall:gemini
+npm run uninstall:gemini:assets
 ```
 
+`*:assets` 제거 명령은 호스트 등록과 변경되지 않은 생성형 호스트 자산을 함께 제거합니다. 사용자가 생성된 자산을 수정했다면 Agestra는 삭제하지 않고 남겨둔 파일을 보고합니다. 전역 npm 설치에서는 `agestra-uninstall codex --assets` 또는 `agestra-uninstall gemini --assets --scope user`를 사용하세요.
+
 프로젝트에 생성된 데이터까지 지우려면 `.agestra/` 디렉터리를 수동으로 삭제하세요.
 
 ---

package/README.md

@@ -26,23 +26,23 @@ Repository checkout:
 
 ```
 npm run bundle
-npm run install:codex
+npm run install:codex:assets
 ```
 
 Global npm package:
 
 ```
 npm install -g agestra
-agestra-install codex
+agestra-install codex --assets
 ```
 
-If you want to register the global package while working from a repo checkout, use:
+If you want MCP-only registration of the global package while working from a repo checkout, use:
 
 ```
 npm run install:codex:global
 ```
 
-Codex uses the repository-level [AGENTS.md](AGENTS.md) instructions plus the registered `agestra` MCP server.
+Codex uses the repository-level [AGENTS.md](AGENTS.md) instructions plus the registered `agestra` MCP server. The `--assets` path also installs generated Codex custom agents under `.codex/agents/` and tracks them in the Agestra host-asset manifest. For MCP-only registration, use `npm run install:codex` or `agestra-install codex`.
 
 ### Gemini CLI
 
@@ -50,23 +50,23 @@ Repository checkout:
 
 ```
 npm run bundle
-npm run install:gemini
+npm run install:gemini:assets
 ```
 
 Global npm package:
 
 ```
 npm install -g agestra
-agestra-install gemini
+agestra-install gemini --assets --scope user
 ```
 
-If you want to register the global package while working from a repo checkout, use:
+If you want MCP-only registration of the global package while working from a repo checkout, use:
 
 ```
 npm run install:gemini:global
 ```
 
-Gemini uses the repository-level [GEMINI.md](GEMINI.md) context file plus project commands under [`.gemini/commands/agestra/`](.gemini/commands/agestra).
+Gemini uses the repository-level [GEMINI.md](GEMINI.md) context file plus project commands under [`.gemini/commands/agestra/`](.gemini/commands/agestra). The user-scope `--assets` path installs the Agestra Gemini native extension. For MCP-only registration, use `npm run install:gemini` or `agestra-install gemini`.
 
 Available Gemini commands after setup:
 
@@ -124,15 +124,16 @@ All three hosts drive the same MCP server and shared workflow specs from `comman
 | `/agestra idea [topic]` | Discover improvements by comparing with similar projects |
 | `/agestra design [subject]` | Explore architecture and design trade-offs before implementation |
 | `/agestra setup` | Initial AI provider selection and setup |
-| `/agestra implement [task]` | Execute implementation in Claude-only or Multi-AI mode |
+| `/agestra implement [task]` | Execute implementation through Leader-host-only or suggested AI distribution mode |
 
-When external providers are available, text commands (review, design, idea) go directly to debate mode for multi-AI cross-validation. When no providers are detected, Claude works alone automatically.
+When external providers are available, text commands (review, design, idea) go directly to consensus debate mode for multi-AI cross-validation. When no providers are detected, the current leader host works with its local specialist agent automatically. Implementation requests first classify the task and can ask whether to propose an AI task distribution.
 
 ## Agents
 
 | Agent | Model | Role |
 |-------|-------|------|
 | `agestra-team-lead` | Sonnet | Full orchestrator — environment check, quality-based provider routing, work mode selection, CLI worker supervision, QA loop |
+| `agestra-implementer` | Sonnet | Scoped implementation executor — code edits, test updates, local verification |
 | `agestra-reviewer` | Opus | Strict quality verifier — security, orphans, spec drift, test gaps |
 | `agestra-designer` | Opus | Architecture explorer — Socratic questioning, trade-off analysis |
 | `agestra-ideator` | Sonnet | Improvement discoverer — web research, competitive analysis |
@@ -148,8 +149,11 @@ When external providers are available, text commands (review, design, idea) go d
 | `cancel` | Graceful stop for workers, debates, chains, tasks |
 | `build-fix` | Auto-diagnose and fix build/typecheck/lint errors |
 | `trace` | View agent execution timeline and flow diagrams |
+| `setup` | Initial provider selection and `providers.config.json` write |
 | `design` | Architecture exploration workflow with multi-AI mode selection |
 | `idea` | Improvement discovery workflow with multi-AI mode selection |
+| `review` | Code quality / security / hardcoding review workflow with multi-AI mode selection |
+| `leader` | Multi-AI/provider orchestration entry — catches explicit provider, debate, consensus, or cross-validation signals, classifies the domain, and hands off to `agestra-team-lead` |
 
 ---
 
@@ -179,11 +183,11 @@ Turborepo monorepo with 9 packages:
 
 ### Work Modes
 
-**Text work** (review, design, idea): providers available → debate mode; no providers → Claude only
+**Text work** (review, design, idea): providers available → consensus debate mode; no providers → Leader-host only
 
 **Implementation work** (team-lead orchestration):
-- **Claude만으로** — Claude implements directly with project/global agents.
-- **다른 AI도 함께** — CLI workers (Codex/Gemini) do autonomous coding in isolated git worktrees, Ollama handles simple tasks, Claude supervises and merges.
+- **Leader-host only** — `agestra-implementer` applies scoped code changes; reviewer/QA verify.
+- **Suggested AI distribution** — the team lead proposes a routing table, asks for approval, then dispatches Codex/Gemini CLI workers for suitable code edits and Ollama for simple/repetitive proposal work.
 
 ---
 
@@ -349,6 +353,7 @@ agestra/
 │   ├── agestra-reviewer.md  # Strict quality verifier (Opus)
 │   ├── agestra-designer.md  # Architecture explorer (Opus)
 │   ├── agestra-ideator.md   # Improvement discoverer (Sonnet)
+│   ├── agestra-implementer.md # Scoped implementation executor (Sonnet)
 │   ├── agestra-moderator.md # Multi-mode facilitator (Sonnet)
 │   ├── agestra-qa.md        # QA verifier (Opus, no code writes)
 │   └── agestra-team-lead.md # Full orchestrator (Sonnet, no code writes)
@@ -357,15 +362,20 @@ agestra/
 │   ├── worker-manage.md     # CLI worker management
 │   ├── cancel.md            # Graceful operation cancellation
 │   ├── build-fix.md         # Build error auto-repair
-│   └── trace.md             # Execution timeline viewer
+│   ├── trace.md             # Execution timeline viewer
+│   ├── setup.md             # Initial provider selection
+│   ├── design.md            # Architecture exploration workflow
+│   ├── idea.md              # Improvement discovery workflow
+│   ├── review.md            # Code quality review workflow
+│   └── leader.md            # Multi-AI orchestration entry router
 ├── hooks/
 │   └── user-prompt-submit.md  # Tool recommendation hook
 ├── dist/
 │   └── bundle.js            # Single-file MCP server bundle
 ├── scripts/
 │   ├── bundle.mjs           # esbuild bundle script
-│   ├── install-host-mcp.mjs # Register Agestra with Codex/Gemini
-│   └── uninstall-host-mcp.mjs # Remove Codex/Gemini MCP registration
+│   ├── install-host-mcp.mjs # Register Claude/Codex/Gemini MCP + host assets
+│   └── uninstall-host-mcp.mjs # Remove host registrations and managed assets
 ├── packages/
 │   ├── core/                # AIProvider interface, registry, security, workers
 │   ├── provider-ollama/     # Ollama HTTP adapter
@@ -398,14 +408,18 @@ Codex CLI:
 
 ```
 npm run uninstall:codex
+npm run uninstall:codex:assets
 ```
 
 Gemini CLI:
 
 ```
 npm run uninstall:gemini
+npm run uninstall:gemini:assets
 ```
 
+The `*:assets` uninstall commands remove both the host registration and unchanged generated host assets. If a generated asset was edited by the user, Agestra leaves it in place and reports it. For a global npm install, use `agestra-uninstall codex --assets` or `agestra-uninstall gemini --assets --scope user`.
+
 If you also want to delete generated project data, remove the `.agestra/` directory manually.
 
 ---

package/README.zh.md

@@ -24,22 +24,37 @@ Claude 保持现有插件安装体验不变。Agestra 会在首次使用时通
 
 ```
 npm run bundle
-npm run install:codex
+npm run install:codex:assets
 ```
 
-Codex 会结合仓库根目录下的 [AGENTS.md](AGENTS.md) 与已注册的 `agestra` MCP 服务一起工作。
+使用全局 npm 包时：
+
+```
+npm install -g agestra
+agestra-install codex --assets
+```
+
+Codex 会结合仓库根目录下的 [AGENTS.md](AGENTS.md) 与已注册的 `agestra` MCP 服务一起工作。`--assets` 还会在 `.codex/agents/` 下安装生成的 Codex custom agent，并写入 Agestra host-asset manifest。只注册 MCP 时，请使用 `npm run install:codex` 或 `agestra-install codex`。
 
 ### Gemini CLI
 
 ```
 npm run bundle
-npm run install:gemini
+npm run install:gemini:assets
 ```
 
-Gemini 会结合仓库根目录下的 [GEMINI.md](GEMINI.md) 与 [`.gemini/commands/agestra/`](.gemini/commands/agestra) 项目命令一起工作。
+使用全局 npm 包时：
+
+```
+npm install -g agestra
+agestra-install gemini --assets --scope user
+```
+
+Gemini 会结合仓库根目录下的 [GEMINI.md](GEMINI.md) 与 [`.gemini/commands/agestra/`](.gemini/commands/agestra) 项目命令一起工作。user scope 的 `--assets` 会安装 Agestra Gemini native extension。只注册 MCP 时，请使用 `npm run install:gemini` 或 `agestra-install gemini`。
 
 安装后可用的 Gemini 命令：
 
+- `/agestra:setup`
 - `/agestra:review`
 - `/agestra:design`
 - `/agestra:idea`
@@ -84,7 +99,7 @@ Gemini 会结合仓库根目录下的 [GEMINI.md](GEMINI.md) 与 [`.gemini/comma
 | `/agestra setup` | 初始 AI 提供方选择与设置 |
 | `/agestra implement [task]` | 以 Claude only 或 Multi-AI 模式执行实现 |
 
-当外部提供方可用时，文本命令（review、design、idea）直接进入辩论模式，进行多 AI 交叉验证。当未检测到提供方时，Claude 自动独立工作。
+当外部提供方可用时，文本命令（review、design、idea）直接进入终极辩论模式，进行多 AI 交叉验证。当未检测到提供方时，Claude 自动独立工作。
 
 ## 代理
 
@@ -106,8 +121,11 @@ Gemini 会结合仓库根目录下的 [GEMINI.md](GEMINI.md) 与 [`.gemini/comma
 | `cancel` | 安全停止 worker、辩论、链路和任务 |
 | `build-fix` | 自动诊断并修复 build/typecheck/lint 错误 |
 | `trace` | 查看代理执行时间线与流程图 |
+| `setup` | 初始提供方选择与 `providers.config.json` 写入 |
 | `design` | 包含 Multi-AI 模式选择的架构探索工作流 |
 | `idea` | 包含 Multi-AI 模式选择的改进发现工作流 |
+| `review` | 包含 Multi-AI 模式选择的代码质量·安全·硬编码审查工作流 |
+| `leader` | 多AI/提供方编排入口 — 捕获明确的提供方、辩论、共识或交叉验证信号，进行领域分类后委托给 `agestra-team-lead` |
 
 ---
 
@@ -137,7 +155,7 @@ Gemini 会结合仓库根目录下的 [GEMINI.md](GEMINI.md) 与 [`.gemini/comma
 
 ### 工作模式
 
-**文本工作**（review、design、idea）：有提供方 → 辩论模式；无提供方 → Claude only
+**文本工作**（review、design、idea）：有提供方 → 终极辩论模式；无提供方 → Claude only
 
 **实现工作**（team-lead orchestration）：
 - **Claude만으로** — Claude 直接结合项目/全局代理完成实现。
@@ -314,15 +332,20 @@ agestra/
 │   ├── worker-manage.md     # CLI Worker 管理
 │   ├── cancel.md            # 安全取消操作
 │   ├── build-fix.md         # 构建错误自动修复
-│   └── trace.md             # 执行时间线查看器
+│   ├── trace.md             # 执行时间线查看器
+│   ├── setup.md             # 初始提供方选择
+│   ├── design.md            # 架构探索工作流
+│   ├── idea.md              # 改进发现工作流
+│   ├── review.md            # 代码质量审查工作流
+│   └── leader.md            # 多AI 编排路由器
 ├── hooks/
 │   └── user-prompt-submit.md  # 工具推荐 hook
 ├── dist/
 │   └── bundle.js            # 单文件 MCP Server bundle
 ├── scripts/
 │   ├── bundle.mjs           # esbuild bundle 脚本
-│   ├── install-host-mcp.mjs # 为 Codex/Gemini 注册 Agestra
-│   └── uninstall-host-mcp.mjs # 从 Codex/Gemini 移除 Agestra 注册
+│   ├── install-host-mcp.mjs # 注册 Claude/Codex/Gemini MCP + host assets
+│   └── uninstall-host-mcp.mjs # 移除宿主注册和受管理资产
 ├── packages/
 │   ├── core/                # AIProvider 接口、注册表、安全、worker
 │   ├── provider-ollama/     # Ollama HTTP 适配器
@@ -355,14 +378,18 @@ Codex CLI：
 
 ```
 npm run uninstall:codex
+npm run uninstall:codex:assets
 ```
 
 Gemini CLI：
 
 ```
 npm run uninstall:gemini
+npm run uninstall:gemini:assets
 ```
 
+`*:assets` 卸载命令会同时移除宿主注册和未修改的生成宿主资产。如果用户编辑过生成资产，Agestra 会保留该文件并报告。使用全局 npm 安装时，请运行 `agestra-uninstall codex --assets` 或 `agestra-uninstall gemini --assets --scope user`。
+
 如果还想删除生成的项目数据，请手动删除 `.agestra/` 目录。
 
 ---

package/agents/agestra-designer.md

@@ -23,6 +23,7 @@ description: |
   </example>
 model: opus
 color: blue
+disallowedTools: Edit, NotebookEdit
 ---
 
 <Role>

package/agents/agestra-ideator.md

@@ -23,6 +23,7 @@ description: |
   </example>
 model: sonnet
 color: green
+disallowedTools: Edit, NotebookEdit
 ---
 
 <Role>

package/agents/agestra-implementer.md

@@ -0,0 +1,76 @@
+---
+name: agestra-implementer
+description: |
+  Implementation executor. Applies scoped code changes, writes or updates tests,
+  follows existing project patterns, and verifies the result. Receives tasks from
+  the team lead; does not orchestrate other providers.
+
+  <example>
+  Context: The team lead has decomposed a task and needs a host-local executor
+  user: "이 작업은 현재 호스트 구현 에이전트가 처리해"
+  assistant: "I'll use the agestra-implementer agent to apply the scoped code changes."
+  <commentary>
+  Implementation executor — modifies code within the assigned files and verifies.
+  </commentary>
+  </example>
+model: sonnet
+color: green
+---
+
+<Role>
+You are a focused implementation executor. You receive a bounded task from the
+leader, modify the code, add or update tests when needed, run verification, and
+report exactly what changed. You are not the moderator, planner, or reviewer.
+</Role>
+
+<Operating_Principles>
+- Stay inside the assigned scope. Do not perform unrelated cleanup or broad refactors.
+- Follow existing project patterns before introducing new abstractions.
+- Treat small and simple as different concepts: a small security or concurrency change may be high-risk; a large repetitive rename may be simple.
+- Prefer tests first for behavioral changes and regressions.
+- Preserve user or other-agent changes. If a file has unrelated edits, work with them rather than reverting them.
+- Do not spawn other AI providers, run debates, or approve external worker changes. Escalate those decisions to the leader.
+</Operating_Principles>
+
+<Workflow>
+
+### Phase 1: Intake
+
+Confirm the task packet contains:
+- Task goal
+- Files allowed to modify
+- Files useful to read
+- Constraints and non-goals
+- Success criteria and verification commands
+- Design/spec reference if one exists
+
+If the task packet is too vague to implement safely, ask the leader for clarification rather than guessing.
+
+### Phase 2: Inspect
+
+Read the relevant files and identify the existing local pattern. Keep the implementation approach small and compatible with surrounding code.
+
+### Phase 3: Implement
+
+Apply the minimal code changes needed to satisfy the task. Add tests when the change affects behavior, public contracts, generated output, provider routing, orchestration, or failure handling.
+
+### Phase 4: Verify
+
+Run the narrowest useful tests first, then broader checks when the change touches shared behavior. If verification fails, diagnose and fix within the assigned scope. If the failure belongs outside the task scope, report it clearly to the leader.
+
+### Phase 5: Report
+
+Report:
+- Files changed
+- Behavior changed
+- Tests or commands run, with pass/fail status
+- Any remaining risks or follow-up decisions for the leader
+
+</Workflow>
+
+<Constraints>
+- You may edit files only for the assigned implementation task.
+- Do not accept or reject CLI worker worktrees.
+- Do not write final synthesis, debate, or approval documents.
+- Do not hide failed verification. Report it and either fix it or explain why it is outside scope.
+</Constraints>