oh-my-customcodex 0.5.7 → 0.5.9

package/templates/.claude/rules/SHOULD-memory-integration.md

@@ -5,7 +5,7 @@
 ## Architecture
 
 **Primary**: Native auto memory (`memory` field in agent frontmatter). No external dependencies.
-**Supplementary**: AgentMemory-compatible MCP or `omx-memory` for cross-session searchable recall; legacy `claude-mem` is fallback only.
+**Supplementary**: `omx-memory` or another AgentMemory-compatible MCP for cross-session searchable recall. Deprecated Chroma-based memory backends are not used in this project.
 
 Rule: If native auto memory can handle it, do NOT use a searchable MCP backend.
 
@@ -33,7 +33,7 @@ Agent frontmatter `memory: project|user|local` enables persistent memory:
 
 <!-- DETAIL: Backend Selection and Split-Brain Guard
 
-Prefer MCP tools named `memory_search`, `memory_add`, `observation_add`, and `memory_read`. Treat `chroma_query_documents`, `chroma_add_documents`, and `chroma_get_documents` as legacy `claude-mem` fallbacks.
+Prefer MCP tools named `memory_search`, `memory_add`, `observation_add`, and `memory_read`. Do not call deprecated Chroma memory tools or wrappers in this project.
 
 If both backend families are available, warn before writing. Dual-write is acceptable only during an explicit migration window; outside that window, choose one canonical searchable backend and record which one was used in the session summary.
 
@@ -332,8 +332,8 @@ User signals session end
        2. Update native auto-memory (MEMORY.md)
        3. Return formatted summary to orchestrator
   → Orchestrator performs MCP saves directly:
-       1. searchable memory save (AgentMemory-compatible or omx-memory, if available via ToolSearch)
-       2. legacy claude-mem save only when it is the configured fallback
+       1. searchable memory save (omx-memory or AgentMemory-compatible backend, if available via ToolSearch)
+       2. deprecated Chroma memory backends are skipped by project policy
        (episodic-memory auto-indexes after session — no action needed)
   → Orchestrator confirms to user
 ```
@@ -355,7 +355,6 @@ MCP tools (searchable memory backends, episodic-memory) are **orchestrator-scope
 |--------|-------|------|--------|----------|
 | Native auto-memory | sys-memory-keeper | Write | Update MEMORY.md with session learnings | Yes |
 | AgentMemory-compatible / omx-memory | Orchestrator | `memory_add` or `observation_add` | Save session summary with project, tasks, decisions | No (best-effort) |
-| legacy claude-mem | Orchestrator | `chroma_add_documents` or compatible save wrapper | Fallback searchable save when no preferred backend exists | No (best-effort) |
 | episodic-memory | Automatic | (auto-indexed) | No action needed — conversations are indexed automatically after session ends | N/A |
 -->
 

package/templates/.claude/skills/de-lead-routing/SKILL.md

@@ -61,24 +61,17 @@ Check if Agent Teams is available (`OMCODEX_AGENT_TEAMS=1` or TeamCreate/SendMes
 | Cross-tool data quality analysis | Agent Teams |
 | Quick DAG/model validation | Agent Tool |
 
-### Step 2: Codex-Exec Hybrid (Code Generation)
+### Step 2: External Interop Guidance (Code Generation)
 For **new pipeline code**, **DAG scaffolding**, or **SQL model generation**:
 
-1. Check `/tmp/.codex-env-status-*` for codex, gemini, and rtk availability
-2. If codex available AND task involves new file creation → automatically delegate to `/codex-exec` for scaffolding:
-   - Display: `[Codex Hybrid] Delegating to codex-exec...`
-   - codex-exec generates initial code (strength: fast generation)
-   - Selected DE expert reviews and refines codex output (strength: reasoning, quality)
-3. If codex unavailable but gemini available → delegate to `/gemini-exec` for scaffolding:
-   - Display: `[Gemini Hybrid] Delegating to gemini-exec...`
-   - gemini-exec generates initial code
-   - Selected DE expert reviews and refines output
-4. If RTK available (`RTK=available` in env status) → optionally wrap DE expert output through RTK to reduce token consumption by 60-90%:
+1. Use the selected DE expert as the default implementation path.
+2. If the native Claude Code plugin `openai/codex-plugin-cc` is explicitly installed and requested, it may provide Codex interop for scaffolding before expert review.
+3. If RTK is available (`RTK=available` in env status), optionally wrap DE expert output through `rtk-exec` to reduce token consumption by 60-90%:
    - Display: `[RTK Proxy] Token optimization active via rtk-exec`
    - RTK acts as a transparent proxy — no change to expert selection
-5. If none available → display `[External CLI] Unavailable — proceeding with {expert} directly` and use DE expert directly
+4. Otherwise display `[External CLI] Not requested — proceeding with {expert} directly` and use the expert directly.
 
-**Suitable**: New DAG files, dbt model scaffolding, SQL template generation
+**Suitable for optional plugin interop**: New DAG files, dbt model scaffolding, SQL template generation
 **Unsuitable**: Existing pipeline modification, architecture decisions, data quality analysis
 
 ### Step 3: Expert Selection

package/templates/.claude/skills/dev-lead-routing/SKILL.md

@@ -104,24 +104,17 @@ Check if Agent Teams is available (`OMCODEX_AGENT_TEAMS=1` or TeamCreate/SendMes
 | Cross-layer debugging (FE + BE + DB) | Agent Teams |
 | Simple file search/validation | Task Tool |
 
-### Step 2: Codex-Exec Hybrid (Implementation Tasks)
+### Step 2: External Interop Guidance (Implementation Tasks)
 For **new file creation**, **boilerplate**, or **test code generation**:
 
-1. Check `/tmp/.codex-env-status-*` for codex, gemini, and rtk availability
-2. If codex available AND task involves new file creation → automatically delegate to `/codex-exec` for scaffolding:
-   - Display: `[Codex Hybrid] Delegating to codex-exec...`
-   - codex-exec generates initial code (strength: fast generation)
-   - Selected Claude expert reviews and refines codex output (strength: reasoning, quality)
-3. If codex unavailable but gemini available → delegate to `/gemini-exec` for scaffolding:
-   - Display: `[Gemini Hybrid] Delegating to gemini-exec...`
-   - gemini-exec generates initial code
-   - Selected Claude expert reviews and refines output
-4. If RTK available (`RTK=available` in env status) → optionally wrap Claude expert output through RTK to reduce token consumption by 60-90%:
+1. Use the selected expert agent as the default implementation path.
+2. If the native Claude Code plugin `openai/codex-plugin-cc` is explicitly installed and requested, it may provide Codex interop for scaffolding before expert review.
+3. If RTK is available (`RTK=available` in env status), optionally wrap expert output through `rtk-exec` to reduce token consumption by 60-90%:
    - Display: `[RTK Proxy] Token optimization active via rtk-exec`
    - RTK acts as a transparent proxy — no change to expert selection
-5. If none available → display `[External CLI] Unavailable — proceeding with {expert} directly` and use Claude expert directly
+4. Otherwise display `[External CLI] Not requested — proceeding with {expert} directly` and use the expert directly.
 
-**Suitable**: New file creation, boilerplate, scaffolding, test code
+**Suitable for optional plugin interop**: New file creation, boilerplate, scaffolding, test code
 **Unsuitable**: Existing code modification, architecture decisions, bug fixes
 
 ### Step 3: Expert Agent Selection

package/templates/.claude/skills/intent-detection/SKILL.md

@@ -262,14 +262,12 @@ english:
 ```
 Research intent detected (confidence >= 70%)
     ↓
-Check Codex CLI availability
-    ├─ Available (codex binary + OPENAI_API_KEY)
-    │   → Use codex-exec skill with --effort xhigh
-    │   → Prompt: "Research and analyze: {user_request}"
-    │   → Returns: structured findings for orchestrator
-    └─ Unavailable
-        → Fall back to Claude's WebFetch/WebSearch
-        → Orchestrator handles directly or via general-purpose agent
+Use the research workflow or researcher/expert agents
+    ├─ Native Claude Code plugin `openai/codex-plugin-cc` explicitly installed/requested
+    │   → Optional Codex interop may assist analysis
+    └─ Otherwise
+        → Use existing expert agents, researcher, WebFetch/WebSearch, or RTK paths
+        → Orchestrator handles directly or via specialist agent
 ```
 
 ### Confidence Scoring
@@ -288,6 +286,6 @@ Check Codex CLI availability
 ├── Input: "{user input}"
 ├── Workflow: research-workflow
 ├── Confidence: {percentage}%
-├── Method: codex-exec (xhigh) | WebFetch fallback
+├── Method: research workflow | researcher/expert agent | optional Codex plugin when requested
 └── Reason: {explanation}
 ```

package/templates/.claude/skills/memory-management/SKILL.md

@@ -7,15 +7,14 @@ user-invocable: false
 
 ## Purpose
 
-Provide memory persistence operations using native `MEMORY.md` first, then a searchable MCP backend for cross-session retrieval. Prefer an AgentMemory-compatible or `omx-memory` backend exposing `memory_search`, `memory_add`, and `observation_add`; use legacy `claude-mem` only as a fallback when that is the configured backend.
+Provide memory persistence operations using native `MEMORY.md` first, then a searchable MCP backend for cross-session retrieval. Prefer `omx-memory` or another AgentMemory-compatible backend exposing `memory_search`, `memory_add`, and `observation_add`. Deprecated Chroma memory backends are not used in this project.
 
 ## Backend Order
 
 1. Native auto-memory: compact durable facts in `MEMORY.md`.
-2. AgentMemory-compatible MCP or `omx-memory`: cross-session search, shared observations, and temporal recall.
-3. Legacy `claude-mem`: fallback only when the project still exposes Chroma tools.
+2. `omx-memory` or AgentMemory-compatible MCP: cross-session search, shared observations, and temporal recall.
 
-When both legacy `claude-mem` and an AgentMemory-compatible backend are active, warn about split-brain storage. Dual-write is allowed only during an explicit migration window.
+If multiple searchable backends are active, choose the configured canonical backend and record it in the session summary. Do not dual-write unless a migration window is explicitly documented.
 
 ## Operations
 
@@ -37,7 +36,6 @@ steps:
   3. Store in configured backend:
      - Prefer memory_add for session summaries
      - Use observation_add for atomic behavioral or project observations
-     - Legacy fallback: chroma_add_documents
      - Include metadata
 ```
 
@@ -53,7 +51,6 @@ steps:
      - Include date for temporal searches
   2. Search configured backend:
      - Prefer memory_search
-     - Legacy fallback: chroma_query_documents
      - Request top N results
   3. Format results:
      - Sort by relevance
@@ -68,7 +65,7 @@ operation: get
 description: Retrieve specific memory by ID
 steps:
   1. Prefer memory_read or memory_search by ID
-  2. Legacy fallback: chroma_get_documents with ID
+  2. Fall back to `memory_search` with the ID when direct read is unavailable
   3. Return full document content
 ```
 
@@ -80,8 +77,6 @@ steps:
 # Always include project name
 memory_search({ query: "my-project {search_terms}", limit: 8 })
 
-# Legacy fallback
-chroma_query_documents(["my-project {search_terms}"])
 
 # Examples:
 memory_search({ query: "my-project authentication flow", limit: 5 })
@@ -91,8 +86,8 @@ memory_search({ query: "my-project 2025-01-24 memory system", limit: 5 })
 ### Get by ID
 
 ```python
-# When you have a specific document ID and only legacy tools are available
-chroma_get_documents(ids=["document_id"])
+# When you have a specific document ID
+memory_read({ id: "document_id" })
 ```
 
 ## Document Format
@@ -219,7 +214,7 @@ recall_errors:
 
 | Capability | Searchable MCP | MemKraft |
 |-----------|-----------|----------|
-| Session persistence | ✅ (Chroma) | ✅ (Markdown) |
+| Session persistence | ✅ (approved searchable backend) | ✅ (Markdown) |
 | Entity tracking | ❌ | ✅ (person/org/concept) |
 | Source attribution | ❌ | ✅ (`[Source: who, when, how]`) |
 | Auto-maintenance | ❌ | ✅ (Dream Cycle) |

package/templates/.claude/skills/memory-recall/SKILL.md

@@ -8,7 +8,7 @@ user-invocable: true
 
 # Memory Recall Skill
 
-Search and recall relevant memories from native `MEMORY.md` plus the configured searchable MCP backend. Prefer AgentMemory-compatible or `omx-memory` tools (`memory_search`, `memory_read`); fall back to legacy `claude-mem` Chroma tools only when those are the configured backend.
+Search and recall relevant memories from native `MEMORY.md` plus the configured searchable MCP backend. Prefer `omx-memory` or AgentMemory-compatible tools (`memory_search`, `memory_read`). Deprecated Chroma memory backends are not used in this project.
 
 ## Parameters
 
@@ -35,7 +35,7 @@ Search and recall relevant memories from native `MEMORY.md` plus the configured
 
 2. Search configured backend
    ├── Prefer memory_search
-   └── Legacy fallback: chroma_query_documents
+   └── Report backend unavailable when no approved memory MCP is configured
 
 3. Format results
    ├── Sort by relevance score

package/templates/.claude/skills/memory-save/SKILL.md

@@ -9,7 +9,7 @@ user-invocable: true
 
 # Memory Save Skill
 
-Save current session context to native memory and the configured searchable MCP backend for persistence across context compaction. Prefer AgentMemory-compatible or `omx-memory` tools (`memory_add`, `observation_add`); fall back to legacy `claude-mem` only when that is the configured backend.
+Save current session context to native memory and the configured searchable MCP backend for persistence across context compaction. Prefer `omx-memory` or AgentMemory-compatible tools (`memory_add`, `observation_add`). Deprecated Chroma memory backends are not used in this project.
 
 ## Options
 
@@ -38,7 +38,7 @@ Save current session context to native memory and the configured searchable MCP
 3. Store in configured backend
    ├── Prefer memory_add for summaries
    ├── Prefer observation_add for atomic learnings
-   └── Legacy fallback: chroma_add_documents
+   └── Skip searchable save when no approved backend is configured
 
 4. Report result
 ```

package/templates/.claude/skills/peer-messaging/SKILL.md

@@ -17,7 +17,7 @@ Enables cross-session coordination between multiple GPT Codex + OMX sessions thr
 |-------|-----------|-------|----------|
 | Intra-session agents | Agent Teams (R018) | TeamCreate, SendMessage | Single session multi-agent collaboration |
 | Cross-session instances | claude-peers-mcp | list_peers, send_message | Multi-terminal/project real-time coordination |
-| Cross-session memory | claude-mem | save_memory, search | Async memory persistence |
+| Cross-session memory | omx-memory / AgentMemory-compatible MCP | memory_add, memory_search | Async memory persistence |
 
 > **Important**: R018's `SendMessage` and claude-peers-mcp's `send_message` are different tools with different scopes. Do not confuse them.
 
@@ -54,6 +54,6 @@ claude mcp add claude-peers-mcp -- npx claude-peers-mcp
 ## Integration
 
 - Works with R018 Agent Teams (different scope, complementary)
-- Works with claude-mem (async vs sync messaging)
+- Works with omx-memory or AgentMemory-compatible memory backends (async vs sync messaging)
 - Works with `omcodex:status` (peer discovery)
 - Broker runs on localhost:7899 (SQLite-backed)

package/templates/.claude/skills/research/SKILL.md

@@ -167,17 +167,8 @@ Batch 3: T9, T10            (Innovation)
 
 Before starting verification rounds, check codex availability:
 
-```bash
-# Run this check once before Phase 2 begins
-which codex &>/dev/null && [ -n "$OPENAI_API_KEY" ]
-# Exit 0 → codex available: enable dual-model verification (opus + codex)
-# Exit 1 → codex unavailable: display notice and proceed with opus-only
-```
-
-If unavailable, display: `[Phase 2] Codex unavailable — opus-only verification`
-
 ```
-Team findings ──→ opus 4.6 verification ──→ codex-exec xhigh verification (if available)
+Team findings ──→ opus 4.6 verification ──→ optional plugin-assisted verification
        │                                              │
        └── Contradiction detected? ── YES ──→ Round N+1
                                       NO  ──→ Consensus reached → Phase 3
@@ -185,8 +176,7 @@ Team findings ──→ opus 4.6 verification ──→ codex-exec xhigh verific
 
 Each round:
 1. **opus 4.6**: Deep reasoning verification — checks logical consistency, identifies gaps, challenges assumptions
-2. **codex-exec xhigh** (when available): Independent code-level verification — validates technical claims, tests feasibility
-   - If unavailable: display `[Phase 2] Round {N}: Codex unavailable, proceeding with opus verification only`
+2. **Optional Codex interop**: Use native Claude Code plugin `openai/codex-plugin-cc` only when explicitly installed/requested; otherwise use researcher or RTK-backed local evidence gathering.
 3. **Contradiction resolution**: Reconcile divergent findings between teams and verifiers
 4. **Convergence check**: All major claims verified with no outstanding contradictions → proceed
 
@@ -319,16 +309,11 @@ Round N:
           - Internal consistency (breadth ↔ depth alignment)
           - Cross-domain consistency (security ↔ architecture)
           - Evidence quality (claims without backing)
-  Step 2: codex-exec validates technical claims (when available):
-          a. Invoke: /codex-exec with findings from all teams
-          b. Prompt:  "Validate technical claims: {findings}.
-                       Check code patterns, benchmark reproducibility,
-                       dependency resolution."
-          c. Effort:  --effort xhigh
-          d. Parse:   contradictions → merge with opus findings
-          e. On timeout/error: log "[Phase 2] Round {N}: codex-exec error — {reason},
-                                continuing with opus results only"
-     If unavailable: log "[Phase 2] Round {N}: Codex unavailable, proceeding with opus verification only"
+  Step 2: Optional plugin-assisted validation (only if `openai/codex-plugin-cc` is explicitly installed/requested):
+          a. Validate technical claims against code patterns, benchmark reproducibility,
+             and dependency resolution.
+          b. Parse contradictions → merge with opus findings.
+          c. On unavailable plugin or error: log "[Phase 2] Round {N}: optional Codex interop unavailable — continuing with opus/researcher results".
   Step 3: Compile contradiction list
           - 0 contradictions → CONVERGED
           - >0 contradictions → feedback to relevant teams → Round N+1
@@ -410,7 +395,7 @@ This advisory is informational only and does not block execution.
 
 | Scenario | Fallback |
 |----------|----------|
-| codex-exec unavailable | opus-only verification (still min 2 rounds) |
+| Optional Codex plugin unavailable | opus/researcher verification (still min 2 rounds) |
 | Agent Teams unavailable | Standard Agent tool with R009 batching |
 | Partial team failure | Synthesize from available results, note gaps in report |
 | GitHub issue creation fails | Output report to conversation only |

package/templates/.claude/skills/roundtable-debate/SKILL.md

@@ -12,7 +12,7 @@ version: 1.0.0
 
 ## Purpose
 
-Run a bounded debate when convergence would hide useful disagreement. Unlike `agora`, which drives toward consensus, this workflow preserves minority positions and requires explicit justification before dismissing them.
+Run a bounded debate when convergence would hide useful disagreement. Use this workflow when debate should preserve minority positions and require explicit justification before dismissing them.
 
 ## When To Use
 
@@ -54,11 +54,10 @@ Hard cap: two debate rounds. If the decision still depends on missing facts, sto
 {adopt | defer | reject | gather-more-evidence}
 ```
 
-## Relationship To Agora
+## Relationship To Other Review Workflows
 
 | Workflow | Goal | Best For |
 |----------|------|----------|
-| `agora` | adversarial consensus | release gates, spec approval |
 | `roundtable-debate` | dissent preservation | ambiguous strategy, architectural tradeoffs |
 
-Use `agora --anti-groupthink` when you need consensus plus explicit dissent handling.
+Use `roundtable-debate` when current guidance needs adversarial review plus explicit dissent handling.

package/templates/.claude/skills/structured-dev-cycle/SKILL.md

@@ -93,15 +93,12 @@ A PreToolUse hook in `.codex/hooks/hooks.json` checks this marker and blocks Wri
 └── Output: Implementation complete
 ```
 
-**Codex-Exec Hybrid Option**: When entering Stage 3:
-1. Check `/tmp/.codex-env-status-*` for codex CLI availability
-2. If available AND task involves new file creation → automatically delegate scaffolding to `/codex-exec`:
-   - Display: `[Codex Hybrid] Delegating scaffolding to codex-exec...`
-   - codex-exec generates initial code (strength: fast generation)
-   - Claude expert reviews and refines codex output (strength: reasoning, quality)
-3. If unavailable → display `[Codex] Unavailable — proceeding with Claude experts directly` and proceed with standard implementation via Claude experts
-
-Suitable for codex hybrid: new files, boilerplate, test stubs, scaffolding
+**Optional Codex Plugin Interop**: When entering Stage 3:
+1. Use domain expert agents as the default implementation path.
+2. If the native Claude Code plugin `openai/codex-plugin-cc` is explicitly installed and requested, it may provide Codex interop for new-file scaffolding before expert review.
+3. Otherwise display `[Codex Plugin] Not requested — proceeding with expert agents directly` and proceed with standard implementation.
+
+Suitable for optional plugin interop: new files, boilerplate, test stubs, scaffolding
 Not suitable: modifying existing code, architecture-dependent changes
 
 **Exit criteria**: All planned files created/modified, tests written.
@@ -157,7 +154,7 @@ The stage marker file (`/tmp/.codex-dev-stage`) is read by a PreToolUse hook tha
 For complex tasks, Agent Teams is **preferred** when available (R018):
 - Plan: architect agent
 - Verify: reviewer agent(s) — multi-model-verification via Agent Teams
-- Implement: domain expert agent (+ codex-exec hybrid if available)
+- Implement: domain expert agent (+ optional `openai/codex-plugin-cc` interop only when explicitly installed/requested)
 - Compound: QA agent
 
 When Agent Teams is enabled AND task involves 3+ agents or review→fix cycles, using Agent Teams is MANDATORY per R018.

package/templates/AGENTS.md.en

@@ -110,7 +110,6 @@ NO EXCEPTIONS. NO EXCUSES.
 | `/omcustomcodex:npm-version` | Manage semantic versions |
 | `/omcustomcodex:npm-audit` | Audit dependencies |
 | `/omcustomcodex-release-notes` | Generate release notes from git history |
-| `/codex-exec` | Execute Codex CLI prompts |
 | `/optimize-analyze` | Analyze bundle and performance |
 | `/optimize-bundle` | Optimize bundle size |
 | `/optimize-report` | Generate optimization report |
@@ -134,7 +133,7 @@ project/
 |   +-- hooks/                   # Hook scripts (security, validation, HUD)
 |   +-- contexts/                # Context files (ecomode)
 +-- .agents/
-|   +-- skills/                  # Installed skills (123 directories)
+|   +-- skills/                  # Installed skills (120 directories)
 +-- guides/                      # Reference docs (51 topics)
 ```
 

package/templates/AGENTS.md.ko

@@ -110,7 +110,6 @@ oh-my-customcodex로 구동됩니다.
 | `/omcustomcodex:npm-version` | 시맨틱 버전 관리 |
 | `/omcustomcodex:npm-audit` | 의존성 감사 |
 | `/omcustomcodex-release-notes` | 릴리즈 노트 생성 (git 히스토리 기반) |
-| `/codex-exec` | Codex CLI 프롬프트 실행 |
 | `/optimize-analyze` | 번들 및 성능 분석 |
 | `/optimize-bundle` | 번들 크기 최적화 |
 | `/optimize-report` | 최적화 리포트 생성 |
@@ -134,7 +133,7 @@ project/
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
 +-- .agents/
-|   +-- skills/                  # 설치된 스킬 (123 디렉토리)
+|   +-- skills/                  # 설치된 스킬 (120 디렉토리)
 +-- guides/                      # 레퍼런스 문서 (51 토픽)
 ```
 

package/templates/CLAUDE.md

@@ -102,7 +102,7 @@ oh-my-customcodex로 구동됩니다.
 | 개발 | `/omcustomcodex:goal`, `/dev-review`, `/dev-refactor`, `/sdd-dev`, `/structured-dev-cycle` | 목표 실행, 코드 리뷰, 리팩토링, SDD |
 | 검증 | `/omcustomcodex:sauron-watch`, `/deep-verify`, `/adversarial-review` | R017 검증, 릴리즈 품질, 보안 리뷰 |
 | 릴리즈 | `/pipeline auto-dev`, `/omcustomcodex-release-notes`, `/release-plan` | 자동 개발, 릴리즈 노트 |
-| 리서치 | `/research`, `/scout`, `/deep-plan`, `/omcustomcodex:agora` | 병렬 분석, URL 평가, 연구 계획 |
+| 리서치 | `/research`, `/scout`, `/deep-plan`, `/roundtable-debate` | 병렬 분석, URL 평가, 토론형 검증 |
 | 메모리 | `/memory-save`, `/memory-recall` | 세션 메모리 관리 |
 | 시스템 | `/token-efficiency-audit`, `/pre-generation-arch-check`, `/omcustomcodex:lists`, `/omcustomcodex:status`, `/omcustomcodex:help` | 토큰 효율/아키텍처 감사, 전체 목록, 상태, 도움말 |
 
@@ -119,7 +119,7 @@ project/
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
 +-- .agents/
-|   +-- skills/                  # 스킬 (123 디렉토리)
+|   +-- skills/                  # 스킬 (120 디렉토리)
 +-- guides/                      # 레퍼런스 문서 (51 토픽)
 ```
 

package/templates/CLAUDE.md.en

@@ -112,7 +112,6 @@ NO EXCEPTIONS. NO EXCUSES.
 | `/omcustomcodex:npm-version` | Manage semantic versions |
 | `/omcustomcodex:npm-audit` | Audit dependencies |
 | `/omcustomcodex-release-notes` | Generate release notes from git history |
-| `/codex-exec` | Execute Codex CLI prompts |
 | `/optimize-analyze` | Analyze bundle and performance |
 | `/optimize-bundle` | Optimize bundle size |
 | `/optimize-report` | Generate optimization report |
@@ -133,7 +132,7 @@ project/
 +-- AGENTS.md                    # Entry point
 +-- .codex/
 |   +-- agents/                  # Subagent definitions (50 files)
-|   +-- skills/                  # Skills (123 directories)
+|   +-- skills/                  # Skills (120 directories)
 |   +-- rules/                   # Global rules (22 files)
 |   +-- hooks/                   # Hook scripts (security, validation, HUD)
 |   +-- contexts/                # Context files (4 files)

package/templates/CLAUDE.md.ko

@@ -112,7 +112,6 @@ oh-my-customcodex로 구동됩니다.
 | `/omcustomcodex:npm-version` | 시맨틱 버전 관리 |
 | `/omcustomcodex:npm-audit` | 의존성 감사 |
 | `/omcustomcodex-release-notes` | 릴리즈 노트 생성 (git 히스토리 기반) |
-| `/codex-exec` | Codex CLI 프롬프트 실행 |
 | `/optimize-analyze` | 번들 및 성능 분석 |
 | `/optimize-bundle` | 번들 크기 최적화 |
 | `/optimize-report` | 최적화 리포트 생성 |
@@ -133,7 +132,7 @@ project/
 +-- AGENTS.md                    # 진입점
 +-- .codex/
 |   +-- agents/                  # 서브에이전트 정의 (50 파일)
-|   +-- skills/                  # 스킬 (123 디렉토리)
+|   +-- skills/                  # 스킬 (120 디렉토리)
 |   +-- rules/                   # 전역 규칙 (22 파일)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (4 파일)

package/templates/README.md

@@ -46,7 +46,7 @@ templates/
 +-- workflows/                        # project-level pipeline definitions
 +-- .claude/
 |   +-- agents/                       # agent definitions (50 files)
-|   +-- skills/                       # skill modules (123 SKILL.md files)
+|   +-- skills/                       # skill modules (120 SKILL.md files)
 |   +-- rules/                        # global rules (22 files)
 |   +-- hooks/                        # hook registry and scripts (40 scripts)
 |   +-- contexts/                     # context files
@@ -65,7 +65,7 @@ The counts below should stay aligned with `templates/manifest.json`, README comp
 
 Flat agent definition files. During Codex installation these land under `.codex/agents/`.
 
-### Skills (123)
+### Skills (120)
 
 `templates/.claude/skills/*/SKILL.md`
 

package/templates/guides/agentmemory-migration/measure-step-zero.md

@@ -1,120 +1,20 @@
-# AgentMemory 마이그레이션 — 단계 0: MEASURE (사용 빈도 측정)
+# External Memory Migration — Retired Measurement Plan
 
-> **목적**: Phase 1 (COEXIST) 진입 전, claude-mem skill 실제 호출 빈도 데이터를 수집하여 가설 기반 자산 처리표를 검증한다.
-> **관련 이슈**: #1169 본문 조치 5
-> **참고 메모리**: `feedback_claude_mem_maintenance`, `project_sequencing_alpha_beta_gamma`
+> **Status**: Retired by #1426. The project no longer measures or operates the deprecated Chroma-based memory plugin.
+> **Current policy**: Native auto-memory is primary; `omx-memory` or an AgentMemory-compatible MCP may be used only as an approved searchable supplement.
 
----
+## Decision
 
-## 1. 목적
+The previous measurement-first migration plan is obsolete. The project no longer needs usage baselining for the deprecated plugin because that backend is no longer an accepted dependency.
 
-AgentMemory 마이그레이션 계획(`feedback_claude_mem_maintenance.md`)에는 12개 claude-mem skill의 처리 방향이 가설로 기재되어 있다. 특히 폐기 후보 5종(`make-plan`, `do`, `babysit`, `wowerpoint`, `knowledge-agent`, `pathfinder`)은 "미사용 또는 저빈도"라는 가정 위에 놓여 있다.
+## Replacement Workflow
 
-이 단계에서는 실측 데이터로 가설을 검증한다. 데이터 없이 Phase 1에 진입하면:
-- 실제로 자주 쓰이던 skill을 폐기하여 사용자 워크플로우가 깨질 수 있다.
-- 자산 처리표 재설계 비용이 Phase 2~3로 이월된다.
+1. Keep durable agent facts in native `MEMORY.md` files.
+2. Use `memory_search`, `memory_read`, `memory_add`, or `observation_add` only when an approved searchable backend is configured.
+3. Skip searchable persistence when no approved backend is available; do not install or invoke deprecated Chroma memory tooling.
+4. Record memory-backend decisions in R011 and the session summary.
 
----
+## Verification
 
-## 2. 실행 방법
-
-```bash
-# 기본 실행 (최근 7일, 리포트를 ~/.claude/measure-claude-mem-usage-YYYY-MM-DD.md 에 저장)
-bash scripts/measure-claude-mem-usage.sh
-
-# 최근 14일 스캔
-bash scripts/measure-claude-mem-usage.sh --days 14
-
-# 출력 경로 지정
-bash scripts/measure-claude-mem-usage.sh --output ~/Documents/claude-mem-usage.md
-
-# 헤더 없이 실행 (CI/파이프라인 삽입용)
-bash scripts/measure-claude-mem-usage.sh --quiet
-```
-
-### 스캔 대상 경로
-
-| 경로 | 설명 |
-|------|------|
-| `~/.claude-mem/archives/` | claude-mem MCP 아카이브 (`.jsonl`, `.json`) |
-| `~/.claude/projects/*/session-*.jsonl` | Claude Code 세션 로그 |
-
-둘 중 하나가 없어도 스크립트는 조용히 skip하고 나머지를 스캔한다.
-
----
-
-## 3. 1주 수집 계획
-
-| 시점 | 작업 |
-|------|------|
-| **Day 1** | 첫 측정 — 베이스라인 (`--days 7` 기준 기존 archives 기반) |
-| **Day 4** | 중간 측정 — 추이 확인 (`--days 4`) |
-| **Day 7** | 최종 측정 — 자산 처리표 재검토 및 Phase 1 GO/NO-GO 결정 |
-
-세 시점 모두 `--output` 경로를 달리 지정하여 비교 가능한 파일로 보관한다:
-
-```bash
-bash scripts/measure-claude-mem-usage.sh --output ~/.claude/claude-mem-day1.md
-bash scripts/measure-claude-mem-usage.sh --days 4 --output ~/.claude/claude-mem-day4.md
-bash scripts/measure-claude-mem-usage.sh --days 7 --output ~/.claude/claude-mem-day7.md
-```
-
----
-
-## 4. 해석 기준
-
-| 호출 수 | 신호 | 권장 조치 |
-|---------|------|----------|
-| **0** | 미사용 | 폐기 안전 — 1주 후 처리 결정 |
-| **1-3** | 가끔 사용 | wrapper 또는 대체 도구 매핑 필요 |
-| **4+** | 정기 사용 | 폐기 시 대체 도구 명확화 필수 |
-
-폐기 후보 5종 기준 예상:
-- `make-plan`, `do`, `babysit` → 0 예상 (native AgentMemory로 대체 완료)
-- `wowerpoint`, `knowledge-agent`, `pathfinder` → 0~1 예상 (특수 목적 skill)
-
-실측값이 예상과 다를 경우 자산 처리표를 수정한 후 Phase 1에 진입한다.
-
----
-
-## 5. 결과 활용
-
-### 5-1. #1169에 리포트 첨부
-
-```bash
-gh issue comment 1169 --body-file ~/.claude/claude-mem-day7.md
-```
-
-### 5-2. 자산 처리표 갱신
-
-`.claude/agent-memory/sys-memory-keeper/feedback_claude_mem_maintenance.md` 내 "처리 방향" 열을 실측값 기반으로 업데이트한다.
-
-### 5-3. Phase 1 GO/NO-GO 결정
-
-| 조건 | 결정 |
-|------|------|
-| 폐기 후보 모두 호출 수 0 | GO — Phase 1 진입 |
-| 폐기 후보 중 1개 이상 호출 수 1-3 | CONDITIONAL GO — 대체 도구 매핑 완료 후 진입 |
-| 폐기 후보 중 1개 이상 호출 수 4+ | NO-GO — 처리표 재설계 후 재측정 |
-
----
-
-## 6. 한계 및 주의사항
-
-| 항목 | 설명 |
-|------|------|
-| archives 미존재 | `~/.claude-mem/archives/` 없으면 카운트 0 (정상 — silent skip) |
-| 세션 로그 형식 변경 | Claude Code 업데이트로 `session-*.jsonl` 구조가 변경되면 grep 패턴 수정 필요 |
-| claude-mem MCP telemetry 미사용 | 외부 도구 의존 최소화 원칙에 따라 MCP 자체 지표는 사용하지 않음 |
-| grep 기반 측정 | 같은 파일에 skill 이름이 여러 줄 등장하면 복수 카운트됨 (과대 계산 가능성) |
-| macOS/Linux 호환 | `stat` 옵션 차이를 스크립트 내에서 자동 처리 (`-f %m` vs `-c %Y`) |
-
----
-
-## 7. 참고
-
-- **이슈**: [#1169](../../.github/ — `gh issue view 1169`)
-- **자산 처리표**: `.claude/agent-memory/sys-memory-keeper/feedback_claude_mem_maintenance.md`
-- **시퀀싱 메모리**: `.claude/agent-memory/mgr-creator/project_sequencing_alpha_beta_gamma.md` (또는 해당 메모리 파일)
-- **스크립트**: `scripts/measure-claude-mem-usage.sh`
-- **Phase 1 가이드**: `guides/agentmemory-migration/` (이 디렉토리에 추가 예정)
+- Repository search should not find active instructions for removed memory-plugin names or plugin-specific tool calls.
+- Memory skills must mention native memory and approved searchable MCP tools, not legacy plugin-specific commands.