dsh-omni-router 0.6.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 qwe225380
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,133 @@
+# Omni Router
+
+> GitHub: https://github.com/qwe225380/dsh-omni-router
+> [中文说明](./README.zh-CN.md)
+
+**Omni Router** 是一个 DeepSeek Harness Agent 预设，它不是一个“单一功能插件”，而是一层**智能编排层**：把复杂度路由、思维模式路由、任务类型识别、Plan Mode、项目上下文、TDD、交付门、Git 工作流等能力组合成一个统一的、自动运行的工程闭环。
+
+## Why Omni Router?
+
+单独使用 dsh-routing-suite、dsh-trio、dsh-doublecheck、superpowers-dsh 时，你需要：
+
+- 自己决定什么时候用哪个预设
+- 自己记得先出方案还是直接做
+- 自己记得要写测试、要验证、要过质量门
+- 在不同插件/预设之间手动切换
+
+使用 Omni Router 后，这些判断和编排会自动发生：
+
+```
+任务进来
+   │
+   ├─ 复杂度路由：plan / direct
+   ├─ 思维模式路由：spec / react / balanced
+   ├─ 任务类型识别：bugfix / feature / refactor / test / review
+   │
+   ├─ 复杂任务
+   │    ├─ 自动进入 Plan Mode
+   │    ├─ 自动收集项目上下文
+   │    ├─ 生成代码化方案
+   │    ├─ 注入 TDD / 交付门 / Git 工作流 / 验收清单提示
+   │    ├─ 等你确认
+   │    └─ 执行 + 验证
+   │
+   └─ 简单任务
+        └─ 直接执行 + 轻量验证
+```
+
+## Features
+
+### Core（核心，自带）
+
+- **复杂度自动路由**：简单任务直接做，复杂/模糊任务先方案。
+- **思维模式路由**：自动选择 `spec`（方案优先）/ `react`（直接执行）/ `balanced`（自动）。
+- **任务类型识别**：`bugfix` / `feature` / `refactor` / `test` / `review` / `other`。
+- **Plan Mode 集成**：复用 DSH 内置 Plan Mode，方案必须经你确认后才执行。
+- **项目上下文收集**：按任务类型挑选关键文件，生成有界上下文摘要。
+- **代码化方案模板**：目标、范围、涉及文件、步骤、接口/数据变更、测试计划、风险、兼容性、回滚、验收标准。
+- **TDD 提示**：编码任务自动提示“先写失败测试 → 实现 → 通过”。
+- **交付门提示**：完成前提示运行测试/doublecheck，防止“假完成”。
+- **Git 工作流提示**：分支/worktree、规范 commit、diff 审查。
+- **验收清单提示**：方案批准后自动用 todo 追踪验收标准。
+- **轻量验证**：简单任务改完也要求跑测试或语法检查。
+- **状态持久化**：分类/思维模式/任务类型写入会话事件，resume 可恢复。
+- **降级保护**：Plan Mode 不可用时自动限制为只读工具。
+- **可选 LLM 分类**：不确定的任务可交给模型二次判断。
+- **手动控制**：`/omni` 命令 + `omni_*` 工具。
+
+### Orchestrated（编排复用，推荐安装）
+
+| 插件 | 提供能力 | Omni Router 如何用 |
+|---|---|---|
+| [dsh-trio](https://github.com/huey1in/trio) | 浏览器自动化、MCP、GitHub/GitLab | 需要浏览器/PR/远程操作时自动可用 |
+| [dsh-doublecheck](https://github.com/PerryLink/dsh-doublecheck) | 交付质量门、验证、返工检测 | 复杂编码任务完成前提示走质量门 |
+| [superpowers-dsh](https://github.com/LayneChai/superpowers-dsh) | TDD、调试、规划、协作技能 | 编码任务自动提示加载对应技能 |
+
+> 这些不是强制依赖。装了 → 完整能力；没装 → Omni Router 核心功能依然可用。
+
+## Install
+
+### One-command install
+
+```bash
+# Linux / macOS
+./install.sh
+
+# Windows PowerShell
+./install.ps1
+
+# Cross-platform
+node scripts/install-preset.mjs
+```
+
+Then restart DSH and select **Omni Router (experimental)** in a new session.
+
+## Manual overrides
+
+- Say **“直接做”** / **“直接执行”** → force direct execution.
+- Say **“先出方案”** / **“先设计方案”** → force plan-first.
+- `/omni status` — show current routing state.
+- `/omni plan` — enter plan-first mode.
+- `/omni direct` — enter direct mode.
+- `/omni mode spec|react|balanced` — set thinking mode.
+- Model tools: `omni_status`, `omni_plan`, `omni_direct`, `omni_mode`.
+
+## Configuration
+
+```yaml
+- id: omni-router
+  name: ./src/omni-router.mjs
+  config:
+    requireConfirmation: true
+    useLLMClassification: false
+    # planFirstKeywords: [自定义, 关键词]
+    # directKeywords: [直接跑, 马上改]
+```
+
+See [docs/CONFIGURATION.md](./docs/CONFIGURATION.md) for details.
+
+## Repository structure
+
+```
+omni-router/
+├── agent.cordis.yml
+├── preset.yml
+├── src/omni-router.mjs
+├── test/omni-router.test.mjs
+├── scripts/install-preset.mjs
+├── docs/
+├── .github/workflows/ci.yml
+├── README.md
+├── README.zh-CN.md
+└── LICENSE
+```
+
+## Test
+
+```sh
+npm test
+```
+
+## License
+
+MIT

package/README.zh-CN.md

@@ -0,0 +1,133 @@
+# Omni Router
+
+> GitHub：https://github.com/qwe225380/dsh-omni-router
+> [English](./README.md)
+
+**Omni Router** 是一个 DeepSeek Harness Agent 预设，它不是一个“单一功能插件”，而是一层**智能编排层**：把复杂度路由、思维模式路由、任务类型识别、Plan Mode、项目上下文、TDD、交付门、Git 工作流等能力组合成一个统一的、自动运行的工程闭环。
+
+## 为什么需要 Omni Router？
+
+单独使用 dsh-routing-suite、dsh-trio、dsh-doublecheck、superpowers-dsh 时，你需要：
+
+- 自己决定什么时候用哪个预设
+- 自己记得先出方案还是直接做
+- 自己记得要写测试、要验证、要过质量门
+- 在不同插件/预设之间手动切换
+
+使用 Omni Router 后，这些判断和编排会自动发生：
+
+```
+任务进来
+   │
+   ├─ 复杂度路由：plan / direct
+   ├─ 思维模式路由：spec / react / balanced
+   ├─ 任务类型识别：bugfix / feature / refactor / test / review
+   │
+   ├─ 复杂任务
+   │    ├─ 自动进入 Plan Mode
+   │    ├─ 自动收集项目上下文
+   │    ├─ 生成代码化方案
+   │    ├─ 注入 TDD / 交付门 / Git 工作流 / 验收清单提示
+   │    ├─ 等你确认
+   │    └─ 执行 + 验证
+   │
+   └─ 简单任务
+        └─ 直接执行 + 轻量验证
+```
+
+## 功能
+
+### 核心能力（自带）
+
+- **复杂度自动路由**：简单任务直接做，复杂/模糊任务先方案。
+- **思维模式路由**：自动选择 `spec`（方案优先）/ `react`（直接执行）/ `balanced`（自动）。
+- **任务类型识别**：`bugfix` / `feature` / `refactor` / `test` / `review` / `other`。
+- **Plan Mode 集成**：复用 DSH 内置 Plan Mode，方案必须经你确认后才执行。
+- **项目上下文收集**：按任务类型挑选关键文件，生成有界上下文摘要。
+- **代码化方案模板**：目标、范围、涉及文件、步骤、接口/数据变更、测试计划、风险、兼容性、回滚、验收标准。
+- **TDD 提示**：编码任务自动提示“先写失败测试 → 实现 → 通过”。
+- **交付门提示**：完成前提示运行测试/doublecheck，防止“假完成”。
+- **Git 工作流提示**：分支/worktree、规范 commit、diff 审查。
+- **验收清单提示**：方案批准后自动用 todo 追踪验收标准。
+- **轻量验证**：简单任务改完也要求跑测试或语法检查。
+- **状态持久化**：分类/思维模式/任务类型写入会话事件，resume 可恢复。
+- **降级保护**：Plan Mode 不可用时自动限制为只读工具。
+- **可选 LLM 分类**：不确定的任务可交给模型二次判断。
+- **手动控制**：`/omni` 命令 + `omni_*` 工具。
+
+### 编排复用（推荐安装）
+
+| 插件 | 提供能力 | Omni Router 如何用 |
+|---|---|---|
+| [dsh-trio](https://github.com/huey1in/trio) | 浏览器自动化、MCP、GitHub/GitLab | 需要浏览器/PR/远程操作时自动可用 |
+| [dsh-doublecheck](https://github.com/PerryLink/dsh-doublecheck) | 交付质量门、验证、返工检测 | 复杂编码任务完成前提示走质量门 |
+| [superpowers-dsh](https://github.com/LayneChai/superpowers-dsh) | TDD、调试、规划、协作技能 | 编码任务自动提示加载对应技能 |
+
+> 这些不是强制依赖。装了 → 完整能力；没装 → Omni Router 核心功能依然可用。
+
+## 安装
+
+### 一键安装
+
+```bash
+# Linux / macOS
+./install.sh
+
+# Windows PowerShell
+./install.ps1
+
+# 跨平台
+node scripts/install-preset.mjs
+```
+
+安装后重启 DSH，新建会话选择 **Omni Router (experimental)**。
+
+## 手动控制
+
+- 说 **“直接做”** / **“直接执行”** → 强制直接执行。
+- 说 **“先出方案”** / **“先设计方案”** → 强制先出方案。
+- `/omni status` — 查看当前路由状态。
+- `/omni plan` — 进入方案优先模式。
+- `/omni direct` — 进入直接执行模式。
+- `/omni mode spec|react|balanced` — 设置思维模式。
+- 模型工具：`omni_status` / `omni_plan` / `omni_direct` / `omni_mode`。
+
+## 配置
+
+```yaml
+- id: omni-router
+  name: ./src/omni-router.mjs
+  config:
+    requireConfirmation: true
+    useLLMClassification: false
+    # planFirstKeywords: [自定义, 关键词]
+    # directKeywords: [直接跑, 马上改]
+```
+
+详细说明见 [docs/CONFIGURATION.md](./docs/CONFIGURATION.md)。
+
+## 仓库结构
+
+```
+omni-router/
+├── agent.cordis.yml
+├── preset.yml
+├── src/omni-router.mjs
+├── test/omni-router.test.mjs
+├── scripts/install-preset.mjs
+├── docs/
+├── .github/workflows/ci.yml
+├── README.md
+├── README.zh-CN.md
+└── LICENSE
+```
+
+## 测试
+
+```sh
+npm test
+```
+
+## 许可证
+
+MIT

package/agent.cordis.yml

@@ -0,0 +1,183 @@
+# Omni Router (experimental)
+#
+# Auto-routes the first real user task by complexity:
+#   - simple / concrete task  -> full tool catalog, direct execution
+#   - complex / ambiguous    -> built-in plan mode, structured plan, approval gate
+#
+# This preset is intentionally minimal. It reuses the host profile's installed
+# capabilities (browser/MCP/GitHub, quality gates, skills) when present and
+# degrades gracefully when absent. It does not modify other presets.
+
+# This file is an AGENT-PLANE composition. It must not own registries, sandbox,
+# persistence, or model routes; those stay in the host composition.
+
+# ── identity ────────────────────────────────────────────────────────────────
+
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    text: You are a helpful software engineer assistant.
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536
+
+# ── shell ───────────────────────────────────────────────────────────────────
+
+- id: tool-bash
+  name: '@deepseek-ai/dsh-tool-bash'
+  disabled: !!js process.platform === 'win32'
+
+- id: tool-pwsh
+  name: '@deepseek-ai/dsh-tool-pwsh'
+  disabled: !!js process.platform !== 'win32'
+
+# ── filesystem ──────────────────────────────────────────────────────────────
+
+- id: tool-fs
+  name: '@deepseek-ai/dsh-tool-fs'
+
+- id: tool-fs-search
+  name: '@deepseek-ai/dsh-tool-fs-search'
+  config:
+    sampleOverCapGlobResults: false
+
+- id: tool-str-replace-editor
+  name: '@deepseek-ai/dsh-tool-str-replace-editor'
+
+# ── background jobs ────────────────────────────────────────────────────────
+
+- id: tool-jobs
+  name: '@deepseek-ai/dsh-tool-jobs'
+
+# ── skills ──────────────────────────────────────────────────────────────────
+
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+
+- id: tool-skill
+  name: '@deepseek-ai/dsh-tool-skill'
+
+# ── goals ───────────────────────────────────────────────────────────────────
+
+- id: tool-goal
+  name: '@deepseek-ai/dsh-tool-goal'
+
+# ── plan mode + omni-router ─────────────────────────────────────────────────
+#
+# Omni Router lives in the same isolated planMode realm so it can programmatically
+# enter/leave plan mode for complex tasks.
+
+- id: planning
+  name: cordis:group
+  group: true
+  isolate:
+    planMode: true
+  config:
+    - id: plan-mode
+      name: '@deepseek-ai/dsh-plan-mode'
+      config:
+        section: |
+              You are in Omni Router plan mode. Stay in plan mode until exit_plan_mode succeeds or the user switches the session mode. Imperative language to implement changes means plan the implementation, not execute it. A user's conversational agreement — including an answer confirming something you asked — approves nothing and does not end plan mode; fold the confirmed decision into the plan and submit it through exit_plan_mode.
+
+              Explore first. Use non-mutating reads, searches, static analysis, and checks to ground the plan in the actual repository. Do not edit or write files, change configuration, run formatters or code generation that rewrites tracked files, commit, or otherwise carry out the plan.
+
+              The tool catalog stays the same across modes for request-cache stability. These plan-mode rules override any later tool description or guidance that suggests using mutation tools; those tools remain listed to keep the tool catalog unchanged. Do not use todo_write to track this planning phase: it tracks implementation after an approved plan, while the plan itself belongs in exit_plan_mode.
+
+              Produce a structured plan with these sections:
+              1. Goal — what outcome must be achieved, in one verifiable sentence.
+              2. Scope — what is in scope and what is out of scope.
+              3. Involved files / modules — which files and modules the change touches.
+              4. Implementation steps — concrete, ordered changes grouped by subsystem.
+              5. Interface / data changes — APIs, schemas, or data formats that change.
+              6. Test plan — which tests to add or update and how to verify.
+              7. Risks — likely failure modes and how they will be handled.
+              8. Compatibility / migration — backward compatibility and migration impact.
+              9. Rollback — how to revert safely if the change fails.
+              10. Acceptance criteria — observable checks that prove the work is done.
+
+              Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer.
+
+              When ready, call exit_plan_mode with the complete plan markdown, starting with a # title. Make exit_plan_mode the only and final tool call in that assistant response: it presents the plan for approval, and implementation begins only in a later step after approval. Do not paste the final plan as a plain reply or ask "should I proceed?" through prose or ask_user_question. If review rejects it, incorporate the feedback and present again. If the review channel is unavailable or aborted, stay in plan mode and ask the user to switch modes manually; do not proceed with implementation.
+
+    - id: omni-router
+      name: ./src/omni-router.mjs
+      config:
+        requireConfirmation: true
+        # planFirstKeywords: [自定义, 关键词]
+        # directKeywords: [直接跑, 马上改]
+
+# ── compaction ──────────────────────────────────────────────────────────────
+
+- id: compaction
+  name: cordis:group
+  group: true
+  isolate:
+    compaction: true
+    toolResultPruner: true
+  config:
+    - id: compaction-basic
+      name: '@deepseek-ai/dsh-compaction-basic'
+
+    - id: command-compact
+      name: '@deepseek-ai/dsh-command-compact'
+
+    - id: tool-result-pruner
+      name: '@deepseek-ai/dsh-compaction-tool-result-pruner'
+      config:
+        thresholdChars: 8192
+        headChars: 4096
+        tailChars: 1024
+
+# ── delegation and workflows ────────────────────────────────────────────────
+
+- id: delegation
+  name: cordis:group
+  group: true
+  isolate:
+    workflowEngine: true
+  config:
+    - id: tool-subagent-control
+      name: '@deepseek-ai/dsh-tool-subagent-control'
+
+    - id: tool-subagent-list-agents
+      name: '@deepseek-ai/dsh-tool-subagent-control/list-agents'
+
+    - id: tool-subagent
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: spawn
+        toolName: subagent
+        backgroundMode: continuable
+
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    - id: workflow-worker-thread
+      name: '@deepseek-ai/dsh-workflow-worker-thread'
+      config:
+        provider: spawn
+
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+
+# ── remaining model-facing rows ─────────────────────────────────────────────
+
+- id: tool-ask-user
+  name: '@deepseek-ai/dsh-tool-ask-user'
+
+- id: tool-todo
+  name: '@deepseek-ai/dsh-tool-todo'
+  config:
+    allowParallelInProgress: true
+
+- id: tool-web
+  name: '@deepseek-ai/dsh-tool-web'
+  config:
+    fetch: false
+    searchTimeoutMs: 60000

package/docs/ARCHITECTURE.md

@@ -0,0 +1,48 @@
+# 架构说明
+
+## 形态
+
+Omni Router 是一个 **DeepSeek Harness Agent 预设**，不是 bundle 插件。
+
+```
+omni-router/
+├── agent.cordis.yml          # 预设装配
+├── preset.yml                # 模式定义
+├── src/omni-router.mjs       # 核心逻辑
+├── test/omni-router.test.mjs # 单元测试
+├── scripts/install-preset.mjs
+├── docs/
+└── .github/workflows/ci.yml
+```
+
+## 核心流程
+
+```
+用户第一条消息
+   │
+   ├─ 识别复杂度（plan / direct）
+   ├─ 识别任务类型（bugfix / feature / refactor / test / review / other）
+   │
+   ├─ direct → 注入轻量验证提示 → 直接执行
+   │
+   └─ plan → 进入 Plan Mode
+        ├─ 自动收集项目上下文
+        ├─ 注入代码化方案模板
+        ├─ 注入 TDD / 交付门 / Git 工作流提示
+        ├─ 用户确认
+        └─ 执行
+```
+
+## 关键扩展点
+
+| DSH 扩展点 | 用途 |
+|---|---|
+| `session/event` | 捕获首条用户消息并分类 |
+| `system-prompt/assemble` | 注入方案模板、上下文、TDD/交付门/Git 提示 |
+| `ctx.planMode` | 进入/退出内置 Plan Mode |
+| `ctx.tools.register` | 注册 `omni_status` / `omni_plan` / `omni_direct` |
+| `ctx.commands` | 注册 `/omni` 命令 |
+
+## 状态持久化
+
+分类结果通过 `omni/router` 事件写入会话日志，resume/reload 后可恢复。

package/docs/CONFIGURATION.md

@@ -0,0 +1,28 @@
+# 配置说明
+
+Omni Router 的配置集中在 `agent.cordis.yml` 的 `omni-router` 行：
+
+```yaml
+- id: omni-router
+  name: ./src/omni-router.mjs
+  config:
+    requireConfirmation: true
+    useLLMClassification: false
+    # planFirstKeywords: [自定义, 关键词]
+    # directKeywords: [直接跑, 马上改]
+```
+
+## 配置项
+
+| 配置项 | 默认值 | 说明 |
+|---|---|---|
+| `requireConfirmation` | `true` | 复杂任务是否必须进入 Plan Mode 等待确认 |
+| `useLLMClassification` | `false` | 是否用模型对“不确定任务”做二次分类 |
+| `planFirstKeywords` | 内置关键词 | 额外触发“方案优先”的关键词 |
+| `directKeywords` | 内置关键词 | 额外触发“直接执行”的关键词 |
+
+## 手动控制
+
+- 对话中说 **“直接做”** / **“先出方案”** 可临时覆盖自动判断。
+- 使用 `/omni plan`、`/omni direct`、`/omni status`、`/omni mode spec|react|balanced` 控制。
+- 模型也可调用 `omni_mode` 工具设置思维模式。

package/docs/INSTALL.md

@@ -0,0 +1,43 @@
+# 安装指南
+
+## 环境要求
+
+- DeepSeek Harness 0.1.0-rc.6 或兼容版本
+- Node.js >= 22
+
+## 一键安装
+
+```bash
+# 从仓库根目录
+./install.sh          # Linux / macOS
+./install.ps1         # Windows PowerShell
+node scripts/install-preset.mjs  # 跨平台
+```
+
+脚本会把预设安装到：
+
+```
+~/.dsh/.agent-presets/omni-router
+```
+
+安装后：
+
+1. 完全重启 DSH。
+2. 新建空白会话。
+3. 选择 **Omni Router (experimental)**。
+4. 发送你的任务。
+
+## 手动安装
+
+```powershell
+$target = Join-Path $env:USERPROFILE '.dsh\.agent-presets\omni-router'
+if (Test-Path -LiteralPath $target) { throw "Preset already exists: $target" }
+New-Item -ItemType Directory -Force -Path (Split-Path -Parent $target) | Out-Null
+Copy-Item -Recurse -LiteralPath '.\omni-router' -Destination $target
+```
+
+## 升级
+
+```bash
+node scripts/install-preset.mjs --force
+```

package/install.ps1

@@ -0,0 +1,13 @@
+#!/usr/bin/env pwsh
+# One-command installer for Omni Router (Windows / PowerShell).
+# Usage: ./install.ps1 [-Force]
+
+param(
+  [switch]$Force
+)
+
+$ErrorActionPreference = 'Stop'
+$root = $PSScriptRoot
+$scriptArgs = @()
+if ($Force) { $scriptArgs += '--force' }
+node (Join-Path $root 'scripts/install-preset.mjs') @scriptArgs

package/install.sh

@@ -0,0 +1,14 @@
+#!/usr/bin/env sh
+# One-command installer for Omni Router (Linux / macOS).
+# Usage: ./install.sh [--force]
+
+set -e
+root="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
+args=""
+for arg in "$@"; do
+  if [ "$arg" = "--force" ]; then
+    args="$args --force"
+  fi
+done
+# shellcheck disable=SC2086
+node "$root/scripts/install-preset.mjs" $args

package/package.json

@@ -0,0 +1,36 @@
+{
+  "name": "dsh-omni-router",
+  "version": "0.6.0",
+  "description": "Omni Router - auto-routing DeepSeek Harness preset: simple tasks run directly, complex tasks plan first with approval gate, coding tasks get TDD/delivery-gate guidance.",
+  "type": "module",
+  "license": "MIT",
+  "keywords": [
+    "dsh",
+    "dsh-plugin",
+    "deepseek-harness",
+    "agent-preset",
+    "router",
+    "plan-mode",
+    "tdd"
+  ],
+  "files": [
+    "agent.cordis.yml",
+    "preset.yml",
+    "src",
+    "test",
+    "docs",
+    "README.md",
+    "README.zh-CN.md",
+    "LICENSE",
+    "install.ps1",
+    "install.sh",
+    "scripts"
+  ],
+  "scripts": {
+    "test": "node test/omni-router.test.mjs",
+    "install:preset": "node scripts/install-preset.mjs"
+  },
+  "engines": {
+    "node": ">=22"
+  }
+}

package/preset.yml

@@ -0,0 +1,3 @@
+name: Omni Router (experimental)
+description: Auto-routes tasks by complexity — simple tasks run directly, complex or ambiguous tasks enter plan mode and produce a structured plan (goal, scope, steps, risks, acceptance criteria) before execution. Reuses installed capabilities when available.
+order: 6