@hawk2048/oh-my-dsh 0.2.1 → 0.3.2

package/agent.cordis.yml

@@ -0,0 +1,288 @@
+# The `oh-my-dsh` agent preset: the standard coding agent, plus an
+# orchestration vocabulary layered over DSH's native primitives.
+#
+# It is a copy of `standard` with two changes:
+#   1. a persona that names the oh-my-dsh orchestration modes, and
+#   2. `skill-filesystem` configured to bundle the omd-* skills that travel
+#      with this preset (resolved via `baseUrl`, so the root follows wherever
+#      the preset is installed).
+#
+# Everything else — tools, groups, realms, compaction, plan mode — is the
+# `standard` composition unchanged. The orchestration is SKILLS, not new
+# machinery: the Plan/Execute/Review/Verify pipeline, Team, Autopilot, Ralph,
+# Ralplan, Research, Autoresearch, and Ultragoal all map onto the native
+# `workflow` / `subagent` / `ralph` / `goal` tools already mounted below.
+
+# ── identity ────────────────────────────────────────────────────────────────
+
+# The preset's own persona, shadowing the deployment default for this agent.
+# `{{model}}` resolves from the agent's own route. The working directory is NOT a
+# prompt variable: current DSH registers only `provider` and `model`, and injects
+# the working directory as its own runtime-context section. A `cwd` reference here
+# fails prompt assembly for the whole turn, so leave it out.
+# The row uses the `prefix:` key. `text:` is an older key the persona row's schema
+# no longer accepts — it is dropped, and a required `prefix` then fails the mount.
+- id: persona
+  name: '@deepseek-ai/dsh-persona'
+  config:
+    prefix: >-
+      You are a coding agent powered by the {{model}} model, running on the oh-my-dsh
+      orchestration layer of the DeepSeek Harness.
+      oh-my-dsh maps a multi-agent orchestration vocabulary onto DSH's native primitives:
+      the canonical Plan → Execute → Review → Verify pipeline, Team (staged
+      plan→prd→exec→verify→fix pipeline), Autopilot (one lead agent driving a goal to
+      completion), Ralph (persistent verify/fix loops, no silent partials), Deep Interview
+      (Socratic requirement clarification), Ralplan (consensus planning via multi-perspective
+      deliberation), Research (sourced investigation), Autoresearch (evaluator-driven
+      improvement loop), Ultragoal (durable multi-goal workflow with checkpointed artifacts),
+      and HUD (inline dsh-ui progress dashboards). Prompt-trigger disciplines also ship as
+      skills — pyramid (answer-first MECE structured expression: conclusion in the first line,
+      3–5 mutually exclusive points per level, every layer supporting the one above), tdd
+      (red-green-refactor), deepsearch (codebase-focused lookup), deep-analyze
+      (multi-angle evidence-backed analysis), ultrathink (exhaustive reasoning before acting),
+      ai-slop-cleaner (strip AI filler) — plus doctor (self-check the install), and utility
+      disciplines: debug (reproduce→isolate→fix→verify), release (version→changelog→tag→artifact),
+      remember (durable cross-session notes), cancel (cleanly halt an in-flight mode), minimal-code-discipline
+      (smallest correct diff / YAGNI), external-context (pull in URLs/docs/issues), visual-verdict
+      (structured screenshot QA), skillify (extract a reusable skill), wiki (markdown knowledge
+      base), and help (usage index). Load the matching omd-* skill before entering a mode; default
+      to leading each report with its conclusion (omd-pyramid lists the exceptions);
+      prefer parallel subagent
+      delegation, and drive every long-running objective through the goal tools rather than a single turn.
+
+- id: agent-instructions
+  name: '@deepseek-ai/dsh-agent-instructions'
+  config:
+    maxBytes: 65536
+
+# ── shell ───────────────────────────────────────────────────────────────────
+
+# `shell-env` stays in the HOST composition: `apps/cli/src/web.ts` injects it to
+# publish `DSH_WEB_URL`/`DSH_WEB_MODE`, and a host row that injects a service is
+# the criterion for host-plane ownership — injection resolves before any session
+# exists, so there is no agent to key by. Behind a preset realm those variables
+# never reached the model's shell at all. Both shell tools consume the host
+# registry from here; their executors (`bash-sandbox`/`pwsh-sandbox`) are
+# host-plane too.
+- 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 ──────────────────────────────────────────────────────────────
+
+# Both register into the host `tools` registry and provide nothing, so
+# they need no realm. The `fs` service and its policy stay in the host.
+- id: tool-fs
+  name: '@deepseek-ai/dsh-tool-fs'
+
+- id: tool-fs-search
+  name: '@deepseek-ai/dsh-tool-fs-search'
+  config:
+    sampleOverCapGlobResults: false
+
+# ── background jobs ────────────────────────────────────────────────────────
+
+# Only the model-facing controls. The task REGISTRY stays on the host plane:
+# its producers sit outside any realm this file could put it in — `tool-bash`
+# above resolves it with `ctx.get`, and an entry-local realm here is invisible
+# to every sibling row, so `run_in_background` would answer "background jobs
+# unavailable" while these controls sat in the catalog. The registry is keyed by
+# owning agent anyway, so one host instance serves every session. What a preset
+# chooses is whether its agent can collect and stop background work at all.
+- id: tool-jobs
+  name: '@deepseek-ai/dsh-tool-jobs'
+
+# ── skills ──────────────────────────────────────────────────────────────────
+
+# The skill REGISTRY lives in the host composition and is layered per scope:
+# these rows register into THIS preset's layer of it, so they need no realm.
+# `skill-filesystem` contributes local-root discovery for agents on this preset,
+# plus the omd-* orchestration skills bundled in this preset's own `skills/`
+# directory (`baseUrl` is the preset's directory, so the root follows the
+# install). `tool-skill` gives the catalog and loader; the merged catalog also
+# carries whatever the deployment registered globally (repository plugins).
+- id: skill-filesystem
+  name: '@deepseek-ai/dsh-skill-filesystem'
+  config:
+    customSkillDirs:
+      - !!js "process.getBuiltinModule('node:url').fileURLToPath(new URL('skills/', baseUrl))"
+
+- id: tool-skill
+  name: '@deepseek-ai/dsh-tool-skill'
+
+# ── goals ───────────────────────────────────────────────────────────────────
+
+# The goal service and session driver stay on the host plane, where the Gateway
+# can resolve them. The human command and model-facing tool register into this
+# preset's scoped layers.
+- id: command-goal
+  name: '@deepseek-ai/dsh-command-goal'
+
+# oh-my-dsh slash commands (/omd-plan /omd-execute /omd-review /omd-verify
+# /omd-team /omd-autopilot /omd-ralph /omd-deep-interview /omd-ralplan
+# /omd-research /omd-autoresearch /omd-ultragoal /omd-pyramid): a preset-shipped ESM producer
+# — the relative `name` resolves against the preset's own directory. Each handler
+# submits a user message that steers the model into the matching omd-* skill,
+# then returns a direct UI acknowledgement.
+- id: command-omd
+  name: './commands/omd-commands.mjs'
+
+- id: tool-goal
+  name: '@deepseek-ai/dsh-tool-goal'
+
+# ── plan mode ───────────────────────────────────────────────────────────────
+
+# Plan state is per-agent by nature, so an entry-local realm is not a
+# workaround here — it is the correct lifetime.
+- 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 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. Prefer existing functions and patterns over new machinery.
+
+              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.
+
+              Resolve discoverable facts by inspection. Use ask_user_question only for user-owned choices or material ambiguity that inspection cannot answer. Do not ask the user where code lives or how current behavior works when you can find out.
+
+              Make the plan decision-complete: state the goal and success criteria; group implementation changes by subsystem; identify public API, schema, and data-flow changes; cover edge cases, failure modes, tests, acceptance criteria, and explicit assumptions. Keep it concise enough to review but detailed enough that another engineer can implement it without making design decisions.
+
+              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.
+
+# ── compaction ──────────────────────────────────────────────────────────────
+
+# `compaction-basic` reads `toolResultPrune` through `ctx.get`, so the pruner must
+# share this realm rather than sit outside it.
+#
+# `tokenMeter` is deliberately NOT in this realm: the meter stays on the HOST
+# plane, and the rows here resolve that one instance. It takes no configuration,
+# keys every fold by Session, and owns the context-meter projection units the
+# browser reads for every session — behind a realm those units would come and go
+# with whichever presets happen to be mounted. What a preset chooses is whether
+# its agent compacts at all, which is `compaction-basic` below.
+- 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 ────────────────────────────────────────────────
+
+# The `subagents` registry and its spawn/fork backends live in the HOST
+# composition: the registry is a process singleton whose cross-session queries
+# the api-proxy serves to the browser, and a provider name may only be
+# registered once. This preset contributes the delegation TOOLS, which resolve
+# that host registry.
+#
+# `workflows` is different — nothing outside an agent reads it — so every row
+# that reaches it shares one entry-local realm here, and a consumer left
+# outside would resolve a host registry this preset does not populate.
+- 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
+        modelSelectionSettings: true
+        backgroundMode: continuable
+
+    # Fork omits model selection so provider/model stay equal to the parent and
+    # the inherited history remains eligible for KV Cache reuse. This preset
+    # keeps fork continuable; parent and child inherit the same messaging tool,
+    # while the parent id and return guidance follow the inherited history.
+    - id: tool-subagent-fork
+      name: '@deepseek-ai/dsh-tool-subagent'
+      config:
+        provider: fork
+        toolName: subagent_fork
+        backgroundMode: continuable
+
+    # Production dsh does not install these optional providers. Install the
+    # matching Bundle in this Profile and restart the Host, then copy this
+    # preset and remove `disabled` from the matching tool row. Host availability
+    # alone grants no tool.
+    - id: tool-subagent-codex
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: codex
+        toolName: subagent_codex
+        backgroundMode: one-shot
+        maxDepth: provider-managed
+
+    - id: tool-subagent-claude-code
+      name: '@deepseek-ai/dsh-tool-subagent'
+      disabled: true
+      config:
+        provider: claude-code
+        toolName: subagent_claude_code
+        backgroundMode: one-shot
+        maxDepth: provider-managed
+
+    - id: workflow-worker-thread
+      name: '@deepseek-ai/dsh-workflow-worker-thread'
+      config:
+        provider: spawn
+
+    - id: tool-workflow
+      name: '@deepseek-ai/dsh-tool-workflow'
+
+    - id: tool-ralph
+      name: '@deepseek-ai/dsh-tool-ralph'
+      config:
+        subagentProvider: spawn
+        maxRounds: 64
+
+# ── 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
+
+# The `web` service and its search provider stay in the host composition; only
+# the model-facing tool is per-session.
+- id: tool-web
+  name: '@deepseek-ai/dsh-tool-web'
+  config:
+    fetch: true
+    searchTimeoutMs: 60000

package/commands/omd-commands.mjs

@@ -1,141 +1,150 @@
-// oh-my-dsh 斜杠命令生产者。
-// 注册 plan/execute/review/verify/team/autopilot/ralph/deep-interview/ralplan/research/autoresearch/ultragoal 十二条人类命令。
-// 每条 handler 把任务作为一条用户消息提交给模型（唤醒模型并让它加载对应
-// omd-* skill），然后返回一条直接 UI 确认（不进入模型请求）。
-//
-// 说明：本文件作为 preset 内置插件被 Loader 以 ESM 方式加载；为避免依赖
-// harness 内部包（本地 preset 目录无法走 node_modules 向上解析），这里手工
-// 构造 UserMessage，而不是 import createUserMessage。
-
-export const name = 'omd-commands'
-export const inject = ['commands']
-
-let seq = 0
-function messageId() {
-  seq += 1
-  return 'omd-' + Date.now().toString(36) + '-' + seq.toString(36) + '-' + Math.random().toString(36).slice(2, 10)
-}
-
-function userMessage(text) {
-  return {
-    role: 'user',
-    source: { kind: 'user' },
-    content: [{ type: 'text', text }],
-    id: messageId(),
-  }
-}
-
-const MODES = [
-  {
-    name: 'omd-plan',
-    description: '规划：先探索，产出带依赖与验收标准的实现计划（不写代码）',
-    hint: '<任务>',
-    label: '规划',
-    skill: 'omd-plan',
-    build: (t) => `请加载 omd-plan skill，对以下任务先探索再产出带依赖与验收标准的实现计划（不写代码），并用 HUD 输出计划概览：${t}`,
-  },
-  {
-    name: 'omd-execute',
-    description: '执行：按计划实现，多文件改动委托并行子代理，琐碎改动直接做',
-    hint: '<任务>',
-    label: '执行',
-    skill: 'omd-execute',
-    build: (t) => `请加载 omd-execute skill，按已确认的计划实现以下任务（多文件改动委托并行 subagent，琐碎改动直接做），并用 HUD 输出进度：${t}`,
-  },
-  {
-    name: 'omd-review',
-    description: '评审：独立评审改动，产出缺陷清单（不自我背书）',
-    hint: '<任务>',
-    label: '评审',
-    skill: 'omd-review',
-    build: (t) => `请加载 omd-review skill，对以下改动作独立评审（用评审 subagent 产出 issues 清单，不自我背书），并用 HUD 输出评审结果：${t}`,
-  },
-  {
-    name: 'omd-verify',
-    description: '验证：跑测试/构建，对照验收标准收集证据，失败则迭代',
-    hint: '<任务>',
-    label: '验证',
-    skill: 'omd-verify',
-    build: (t) => `请加载 omd-verify skill，对以下任务跑测试/构建并对照验收标准收集证据（失败则回 execute/review 迭代），并用 HUD 输出验证结果：${t}`,
-  },
-  {
-    name: 'omd-team',
-    description: '团队分阶段流水线（规划→规格→实现→验证→修复）',
-    hint: '<任务>',
-    label: '团队流水线',
-    skill: 'omd-team',
-    build: (t) => `请加载 omd-team skill，用 Team 分阶段流水线编排完成以下任务，各阶段用 HUD 输出进度：${t}`,
-  },
-  {
-    name: 'omd-autopilot',
-    description: '自动驾驶：单个主控代理把目标持续做到已验证完成',
-    hint: '<目标>',
-    label: '自动驾驶',
-    skill: 'omd-autopilot',
-    build: (t) => `请加载 omd-autopilot skill，用 Autopilot 模式把以下目标持续做到已验证完成，并用 HUD 输出进度：${t}`,
-  },
-  {
-    name: 'omd-ralph',
-    description: '拉夫持久验证循环：完整完成并验证到全绿，不留静默半成品',
-    hint: '<目标>',
-    label: '拉夫循环',
-    skill: 'omd-ralph',
-    build: (t) => `请加载 omd-ralph skill，用 Ralph 持久验证循环完成以下目标直到全绿，并用 HUD 输出进度：${t}`,
-  },
-  {
-    name: 'omd-deep-interview',
-    description: '深度访谈：写代码前用苏格拉底式追问澄清需求',
-    hint: '<主题>',
-    label: '深度访谈',
-    skill: 'omd-deep-interview',
-    build: (t) => `请加载 omd-deep-interview skill，对以下想法做深度访谈澄清需求，先收敛出规格再动手：${t}`,
-  },
-  {
-    name: 'omd-ralplan',
-    description: '共识规划：多视角并行规划 + 结构化审议，收敛出共识计划',
-    hint: '<描述>',
-    label: '共识规划',
-    skill: 'omd-ralplan',
-    build: (t) => `请加载 omd-ralplan skill，对以下描述做多视角并行规划 + 结构化审议，收敛出共识计划，并用 HUD 输出草案/分歧/裁决概览：${t}`,
-  },
-  {
-    name: 'omd-research',
-    description: '调研：查证一个开放问题，返回有来源依据的结论',
-    hint: '<问题>',
-    label: '调研',
-    skill: 'omd-research',
-    build: (t) => `请加载 omd-research skill，对以下问题做有据调研（并行研究子代理 + 每条结论标注来源），并用 HUD 输出调研结论与来源：${t}`,
-  },
-  {
-    name: 'omd-autoresearch',
-    description: '自动调研改进：评估器驱动的有界改进循环，持续改进到达标',
-    hint: '<任务>',
-    label: '自动调研',
-    skill: 'omd-autoresearch',
-    build: (t) => `请加载 omd-autoresearch skill，对以下任务做评估器驱动的有界改进循环直到达标，并用 HUD 输出轮次/评分/差距：${t}`,
-  },
-  {
-    name: 'omd-ultragoal',
-    description: '持久多目标：拆解多子目标，带 checkpoint 工件与台账，可恢复可审计',
-    hint: '<目标>',
-    label: '持久目标',
-    skill: 'omd-ultragoal',
-    build: (t) => `请加载 omd-ultragoal skill，把以下大目标拆成多子目标、带 checkpoint 工件与台账持续推进，并用 HUD 输出子目标进度：${t}`,
-  },
-]
-
-export function apply(ctx) {
-  for (const mode of MODES) {
-    ctx.commands.register({
-      name: mode.name,
-      description: mode.description,
-      input: { hint: mode.hint },
-      handler: (invocation) => {
-        const task = (invocation.rawInput || '').trim()
-        if (!task) return { kind: 'error', text: `用法：/${mode.name} ${mode.hint}` }
-        invocation.agent.followup(userMessage(mode.build(task)))
-        return { kind: 'success', text: `${mode.label}已启动：${task}` }
-      },
-    })
-  }
-}
+// oh-my-dsh 斜杠命令生产者。
+// 注册 13 条人类命令：12 条编排命令（plan/execute/review/verify/team/autopilot/ralph/
+// deep-interview/ralplan/research/autoresearch/ultragoal）+ pyramid（金字塔结构化表达）表达纪律命令。
+// 每条 handler 把任务作为一条用户消息提交给模型（唤醒模型并让它加载对应
+// omd-* skill），然后返回一条直接 UI 确认（不进入模型请求）。
+//
+// 说明：本文件作为 preset 内置插件被 Loader 以 ESM 方式加载；为避免依赖
+// harness 内部包（本地 preset 目录无法走 node_modules 向上解析），这里手工
+// 构造 UserMessage，而不是 import createUserMessage。
+
+export const name = 'omd-commands'
+export const inject = ['commands']
+
+let seq = 0
+function messageId() {
+  seq += 1
+  return 'omd-' + Date.now().toString(36) + '-' + seq.toString(36) + '-' + Math.random().toString(36).slice(2, 10)
+}
+
+function userMessage(text) {
+  return {
+    role: 'user',
+    source: { kind: 'user' },
+    content: [{ type: 'text', text }],
+    id: messageId(),
+  }
+}
+
+const MODES = [
+  {
+    name: 'omd-plan',
+    description: '规划：先探索，产出带依赖与验收标准的实现计划（不写代码）',
+    hint: '<任务>',
+    label: '规划',
+    skill: 'omd-plan',
+    build: (t) => `请加载 omd-plan skill，对以下任务先探索再产出带依赖与验收标准的实现计划（不写代码），并用 HUD 输出计划概览：${t}`,
+  },
+  {
+    name: 'omd-execute',
+    description: '执行：按计划实现，多文件改动委托并行子代理，琐碎改动直接做',
+    hint: '<任务>',
+    label: '执行',
+    skill: 'omd-execute',
+    build: (t) => `请加载 omd-execute skill，按已确认的计划实现以下任务（多文件改动委托并行 subagent，琐碎改动直接做），并用 HUD 输出进度：${t}`,
+  },
+  {
+    name: 'omd-review',
+    description: '评审：独立评审改动，产出缺陷清单（不自我背书）',
+    hint: '<任务>',
+    label: '评审',
+    skill: 'omd-review',
+    build: (t) => `请加载 omd-review skill，对以下改动作独立评审（用评审 subagent 产出 issues 清单，不自我背书），并用 HUD 输出评审结果：${t}`,
+  },
+  {
+    name: 'omd-verify',
+    description: '验证：跑测试/构建，对照验收标准收集证据，失败则迭代',
+    hint: '<任务>',
+    label: '验证',
+    skill: 'omd-verify',
+    build: (t) => `请加载 omd-verify skill，对以下任务跑测试/构建并对照验收标准收集证据（失败则回 execute/review 迭代），并用 HUD 输出验证结果：${t}`,
+  },
+  {
+    name: 'omd-team',
+    description: '团队分阶段流水线（规划→规格→实现→验证→修复）',
+    hint: '<任务>',
+    label: '团队流水线',
+    skill: 'omd-team',
+    build: (t) => `请加载 omd-team skill，用 Team 分阶段流水线编排完成以下任务，各阶段用 HUD 输出进度：${t}`,
+  },
+  {
+    name: 'omd-autopilot',
+    description: '自动驾驶：单个主控代理把目标持续做到已验证完成',
+    hint: '<目标>',
+    label: '自动驾驶',
+    skill: 'omd-autopilot',
+    build: (t) => `请加载 omd-autopilot skill，用 Autopilot 模式把以下目标持续做到已验证完成，并用 HUD 输出进度：${t}`,
+  },
+  {
+    name: 'omd-ralph',
+    description: '拉夫持久验证循环：完整完成并验证到全绿，不留静默半成品',
+    hint: '<目标>',
+    label: '拉夫循环',
+    skill: 'omd-ralph',
+    build: (t) => `请加载 omd-ralph skill，用 Ralph 持久验证循环完成以下目标直到全绿，并用 HUD 输出进度：${t}`,
+  },
+  {
+    name: 'omd-deep-interview',
+    description: '深度访谈：写代码前用苏格拉底式追问澄清需求',
+    hint: '<主题>',
+    label: '深度访谈',
+    skill: 'omd-deep-interview',
+    build: (t) => `请加载 omd-deep-interview skill，对以下想法做深度访谈澄清需求，先收敛出规格再动手：${t}`,
+  },
+  {
+    name: 'omd-ralplan',
+    description: '共识规划：多视角并行规划 + 结构化审议，收敛出共识计划',
+    hint: '<描述>',
+    label: '共识规划',
+    skill: 'omd-ralplan',
+    build: (t) => `请加载 omd-ralplan skill，对以下描述做多视角并行规划 + 结构化审议，收敛出共识计划，并用 HUD 输出草案/分歧/裁决概览：${t}`,
+  },
+  {
+    name: 'omd-research',
+    description: '调研：查证一个开放问题，返回有来源依据的结论',
+    hint: '<问题>',
+    label: '调研',
+    skill: 'omd-research',
+    build: (t) => `请加载 omd-research skill，对以下问题做有据调研（并行研究子代理 + 每条结论标注来源），并用 HUD 输出调研结论与来源：${t}`,
+  },
+  {
+    name: 'omd-autoresearch',
+    description: '自动调研改进：评估器驱动的有界改进循环，持续改进到达标',
+    hint: '<任务>',
+    label: '自动调研',
+    skill: 'omd-autoresearch',
+    build: (t) => `请加载 omd-autoresearch skill，对以下任务做评估器驱动的有界改进循环直到达标，并用 HUD 输出轮次/评分/差距：${t}`,
+  },
+  {
+    name: 'omd-ultragoal',
+    description: '持久多目标：拆解多子目标，带 checkpoint 工件与台账，可恢复可审计',
+    hint: '<目标>',
+    label: '持久目标',
+    skill: 'omd-ultragoal',
+    build: (t) => `请加载 omd-ultragoal skill，把以下大目标拆成多子目标、带 checkpoint 工件与台账持续推进，并用 HUD 输出子目标进度：${t}`,
+  },
+  {
+    name: 'omd-pyramid',
+    description: '金字塔表达：把内容重组为结论先行 + MECE 分组 + 层层支撑',
+    hint: '<内容或主题>',
+    label: '金字塔表达',
+    skill: 'omd-pyramid',
+    build: (t) => `请加载 omd-pyramid skill，用金字塔原理（结论先行、以上统下、归类分组 MECE、逻辑递进，必要时 SCQA 开场）重组以下内容的表达，并用 HUD 输出结构对照：${t}`,
+  },
+]
+
+export function apply(ctx) {
+  for (const mode of MODES) {
+    ctx.commands.register({
+      name: mode.name,
+      description: mode.description,
+      input: { hint: mode.hint },
+      handler: (invocation) => {
+        const task = (invocation.rawInput || '').trim()
+        if (!task) return { kind: 'error', text: `用法：/${mode.name} ${mode.hint}` }
+        invocation.agent.followup(userMessage(mode.build(task)))
+        return { kind: 'success', text: `${mode.label}已启动：${task}` }
+      },
+    })
+  }
+}

package/cordis.patch.yml

@@ -1,20 +1,20 @@
-# oh-my-dsh bundle patch: the composition layer this bundle contributes when a
-# profile lists it. `dsh plugin add` appends this layer after @deepseek-ai/dsh-base
-# and before the user's own overrides.
-#
-# - command-omd (insert) registers the 12 /omd-* slash commands into the host
-#   `commands` registry, so every session in the profile sees them.
-# - skill-filesystem (override by id) adds this package's `skills/` to the base
-#   host skill-filesystem via customSkillDirs and re-enables the row (the Web app
-#   ships the base row disabled because presets own local discovery). Overriding
-#   by id keeps a single "filesystem" provider; customSkillDirs is additive over
-#   the default roots, so project and user skills keep working alongside omd's.
-- insert:
-    - id: command-omd
-      name: '@hawk2048/oh-my-dsh/commands'
-
-- id: skill-filesystem
-  disabled: false
-  config:
-    customSkillDirs:
-      - !!js "process.getBuiltinModule('node:url').fileURLToPath(new URL('skills/', baseUrl))"
+# oh-my-dsh bundle patch: the composition layer this bundle contributes when a
+# profile lists it. `dsh plugin add` appends this layer after @deepseek-ai/dsh-base
+# and before the user's own overrides.
+#
+# - command-omd (insert) registers the 13 /omd-* slash commands into the host
+#   `commands` registry, so every session in the profile sees them.
+# - skill-filesystem (override by id) adds this package's `skills/` to the base
+#   host skill-filesystem via customSkillDirs and re-enables the row (the Web app
+#   ships the base row disabled because presets own local discovery). Overriding
+#   by id keeps a single "filesystem" provider; customSkillDirs is additive over
+#   the default roots, so project and user skills keep working alongside omd's.
+- insert:
+    - id: command-omd
+      name: '@hawk2048/oh-my-dsh/commands'
+
+- id: skill-filesystem
+  disabled: false
+  config:
+    customSkillDirs:
+      - !!js "process.getBuiltinModule('node:url').fileURLToPath(new URL('skills/', baseUrl))"

package/index.js

@@ -1,8 +1,8 @@
-// oh-my-dsh bundle entry.
-//
-// The bundle is a composition layer (`cordis.patch.yml`), not a top-level
-// plugin; its capability modules live under ./commands and its skills under
-// ./skills. This entry exists so the package resolves as a module for the
-// patch rows that reference `oh-my-dsh/commands`; it intentionally exports
-// nothing.
-export {}
+// oh-my-dsh bundle entry.
+//
+// The bundle is a composition layer (`cordis.patch.yml`), not a top-level
+// plugin; its capability modules live under ./commands and its skills under
+// ./skills. This entry exists so the package resolves as a module for the
+// patch rows that reference `oh-my-dsh/commands`; it intentionally exports
+// nothing.
+export {}