dsh-lead-mode 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 dsh-lead-mode contributors
+
+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.en.md

@@ -0,0 +1,146 @@
+# dsh-lead-mode
+
+Lead mode for DSH. Adds one `lead-mode` preset, one `lead-mode` skill, and one `/lead-mode` command.
+
+It does three things, none of which touch dsh itself:
+
+1. Preset: switch to it and the model works as a Lead — decomposing, delegating, accepting.
+2. Skill: the Lead working method, loadable by the model or by you.
+3. Reminder: when the session has no Team tools, the model's first move is to tell you to enable the official Agent Teams instead of doing everything alone.
+
+## Enable the Team runtime first
+
+Lead mode delegates through `spawn_teammate`, `send_message`, and `team_task_*`. Those come from the official dsh Team runtime, which this plugin does not ship.
+
+```bash
+dsh plugin --profile <your profile name> add @deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3
+```
+
+**The version pin is required.** Without it npm resolves `latest`, which is 0.1.5-alpha.2 — built for 0.1.x hosts and it will not mount on a 0.2.1 host. `next` points at 0.2.1-rc.3, which is the correct one. Restart dsh afterwards.
+
+Not sure whether it is installed? Run `/lead-mode` in dsh; it reports dependency state.
+
+## Install this plugin
+
+Two routes, pick one.
+
+From npm:
+
+```bash
+dsh plugin --profile <your profile name> add dsh-lead-mode
+```
+
+From GitHub (use this before the npm release):
+
+```bash
+dsh plugin --profile <your profile name> add https://github.com/xiebaiyuan/dsh-lead-mode
+```
+
+Restart dsh afterwards, then pick "Lead 模式" in the preset list.
+
+## Usage
+
+Three steps.
+
+**1. Switch to Lead mode.** Pick "Lead 模式" in a new session's preset list. The model's first system-prompt section becomes the Lead persona, and the reminder at its top goes in with it.
+
+**2. Run `/lead-mode` to check dependencies.** This command delegates nothing; it only reports state:
+
+- Whether the Team runtime is mounted, and its `maxMembers` when it is
+- Whether the `lead-mode` preset registered
+- The version-pinned install command when something is missing
+
+Returns success when everything is in place, error when something is missing.
+
+**3. Let the model work.** With the delegation tools in place, the model decomposes, delegates to teammates, and waits for all of them before wrapping up. Without them, its first move is to tell you to enable the Team runtime — it will not do everything alone, and it will not substitute `subagent` for a teammate.
+
+## Required official bundles and versions
+
+This plugin ships none of the packages below. The host or an official bundle provides them; this plugin only declares version requirements in `peerDependencies`.
+
+| Package | Requirement | Provided by | When missing |
+|---|---|---|---|
+| `@deepseek-ai/dsh-experimental-agent-team-profile` | `0.2.1-rc.3` | You install it explicitly | Cannot delegate; `/lead-mode` returns error; startup warn |
+| `@deepseek-ai/dsh` | `>=0.2.1-rc.2` | Host | Will not install |
+| `@deepseek-ai/cordis` | `^4.0.5` | Host | Will not install |
+| `@deepseek-ai/schemastery` | `^3.18.5` | Host | Will not install |
+| `@deepseek-ai/dsh-agent-preset-registry` | `>=0.2.1-rc.2` | Host | Preset row does not take effect; `/lead-mode` reports unknown |
+| `@deepseek-ai/dsh-skill` | `>=0.2.1-rc.2` | Host | Skill not registered; startup warn |
+| `@deepseek-ai/dsh-commands` | `>=0.2.1-rc.2` | Host | `/lead-mode` not registered; startup warn |
+
+The target host version is `dshTarget` in `package.json`: `0.2.1-rc.3`.
+
+## Why the install command pins a version
+
+`@deepseek-ai/dsh-experimental-agent-team-profile` has three dist-tags on npm:
+
+| dist-tag | Version | Host it fits |
+|---|---|---|
+| `latest` | 0.1.5-alpha.2 | 0.1.x |
+| `alpha` | 0.2.1-alpha.5 | the 0.2.1 prerelease line |
+| `next` | 0.2.1-rc.3 | 0.2.1 |
+
+Bare package name resolves `latest`, which installs 0.1.5-alpha.2. That build targets 0.1.x hosts and does not mount on a 0.2.1 host. After installing it, no Team tools appear in dsh and `/lead-mode` still reports "not mounted".
+
+Measured on 2026-10-26 with npm 11.20.0:
+
+```
+$ npm view @deepseek-ai/dsh-experimental-agent-team-profile version
+0.1.5-alpha.2
+```
+
+So every install command in this plugin carries `@0.2.1-rc.3`: the persona prefix, the `/lead-mode` output, the startup warn, and SKILL.md. `test/preset.test.mjs` and `test/smoke.test.mjs` both assert that string, so a future edit cannot quietly drop back to the bare name.
+
+For the `alpha` line, pin `@0.2.1-alpha.5` yourself; do not use the bare name.
+
+## Difference from the official standard preset
+
+One place only: the persona. The other 21 rows are copied field for field from `standard`.
+
+| Item | standard | lead-mode |
+|---|---|---|
+| persona prefix | `You are a coding agent powered by the {{model}} model.` | Chinese Lead persona plus an Agent Teams precondition check |
+| other 21 rows | — | identical to standard, field for field |
+
+The four classic subagent rows (`tool-subagent-control`, `tool-subagent-list-agents`, `tool-subagent`, `tool-subagent-fork`) stay enabled. Nothing is disabled. The Team tools are a host decision, not a preset decision.
+
+## Why the preset does not carry the Team runtime
+
+`apply()` in `@deepseek-ai/dsh-experimental-tool-agent-team` listens on the global `agent/created` event and installs Team tools on every agent. It is a host-plane plugin; putting it in a preset would leak it into every session.
+
+So this plugin stays at: preset, skill, reminder. Whether the Team runtime is on is decided by the user through the official profile package.
+
+## What `/lead-mode` reports
+
+Three facts:
+
+- Whether the Team runtime is mounted, and its `maxMembers` when it is
+- Whether the `lead-mode` preset registered
+- The version-pinned install command when something is missing
+
+Returns success when everything is in place, error when something is missing. Missing dependencies are never silent.
+
+## Layout
+
+```
+package.json            package metadata; dsh.bundle.patch points at cordis.patch.yml
+cordis.patch.yml        two insert rows: this plugin and the lead-mode preset
+lib/index.js            host half: register the skill, register the command, startup check
+skills/lead-mode/       the Lead working method
+dsh-plugin.naming.json  naming manifest
+test/                   behaviour assertions, zero dependencies
+```
+
+## Development
+
+```bash
+node --check lib/index.js
+node --test test/
+node scripts/check-patch.mjs
+```
+
+Tests are zero-dependency. No `npm install` needed.
+
+## License
+
+MIT

package/README.md

@@ -1,3 +1,146 @@
-# Temporary Holding Version
+# dsh-lead-mode
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+DSH 的 Lead 模式。装好后多一个 `lead-mode` 预设、一个 `lead-mode` skill、一个 `/lead-mode` 命令。
+
+它做三件事，都不碰 dsh 本体：
+
+1. 预设：切过去，模型就按 Lead 的方式干活，拆活、派活、验收。
+2. skill：Lead 工作法写在里面，模型可以自己加载，你也可以手动加载。
+3. 提醒：本会话没有 Team 工具时，模型第一句就告诉你先去开官方 Agent Teams，不硬干。
+
+## 装之前先开 Team 运行时
+
+Lead 模式靠 `spawn_teammate`、`send_message`、`team_task_*` 这些工具派活。它们由 dsh 官方的 Team 运行时提供，本插件不带。
+
+```bash
+dsh plugin --profile <你的 profile 名> add @deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3
+```
+
+**必须带版本号。** 不带会装到 `latest` 上的 0.1.5-alpha.2，那是给 0.1.x 宿主用的，在 0.2.1 宿主上挂不上。`next` 指向的 0.2.1-rc.3 才对。装完重启 dsh。
+
+不确定装没装？进 dsh 敲 `/lead-mode`，它会报依赖状态。
+
+## 装本插件
+
+两条路，选一条。
+
+从 npm：
+
+```bash
+dsh plugin --profile <你的 profile 名> add dsh-lead-mode
+```
+
+从 GitHub（还没发 npm 时用这条）：
+
+```bash
+dsh plugin --profile <你的 profile 名> add https://github.com/xiebaiyuan/dsh-lead-mode
+```
+
+装完重启 dsh。在预设列表里选「Lead 模式」。
+
+## 用法
+
+三步。
+
+**1. 切到 Lead 模式。** 新会话的预设列表里选「Lead 模式」。切过去之后，模型的 system prompt 第一段就换成 Lead 人设，开头那段提醒跟着进去。
+
+**2. 敲 `/lead-mode` 查依赖。** 这条命令不派活，只报状态：
+
+- Team 运行时挂没挂，挂了报 `maxMembers`
+- `lead-mode` 预设注册没注册
+- 缺东西时给带版本号的安装命令
+
+依赖齐了返回 success，缺东西返回 error。
+
+**3. 让模型干活。** 派活的工具齐了，模型会自己拆活、派给 teammate、等齐再收尾。工具不齐，它第一句就是让你去开 Team 运行时，不会自己硬干，也不会拿 `subagent` 顶替 teammate。
+
+## 依赖的官方 bundle 与版本
+
+本插件不捆绑下面这些包。它们由宿主或官方 bundle 提供，本插件只在 `peerDependencies` 里声明版本要求。
+
+| 包 | 版本要求 | 谁提供 | 缺了会怎样 |
+|---|---|---|---|
+| `@deepseek-ai/dsh-experimental-agent-team-profile` | `0.2.1-rc.3` | 用户显式安装 | 派不了活，`/lead-mode` 报 error，启动 warn |
+| `@deepseek-ai/dsh` | `>=0.2.1-rc.2` | 宿主 | 装不上 |
+| `@deepseek-ai/cordis` | `^4.0.5` | 宿主 | 装不上 |
+| `@deepseek-ai/schemastery` | `^3.18.5` | 宿主 | 装不上 |
+| `@deepseek-ai/dsh-agent-preset-registry` | `>=0.2.1-rc.2` | 宿主 | 预设行不生效，`/lead-mode` 报「查不到」 |
+| `@deepseek-ai/dsh-skill` | `>=0.2.1-rc.2` | 宿主 | skill 不注册，启动 warn |
+| `@deepseek-ai/dsh-commands` | `>=0.2.1-rc.2` | 宿主 | `/lead-mode` 不注册，启动 warn |
+
+目标宿主版本写在 `package.json` 的 `dshTarget` 字段：`0.2.1-rc.3`。
+
+## 为什么安装命令要带版本号
+
+`@deepseek-ai/dsh-experimental-agent-team-profile` 在 npm 上有三个 dist-tag：
+
+| dist-tag | 版本 | 配哪个宿主 |
+|---|---|---|
+| `latest` | 0.1.5-alpha.2 | 0.1.x |
+| `alpha` | 0.2.1-alpha.5 | 0.2.1 预发布线 |
+| `next` | 0.2.1-rc.3 | 0.2.1 |
+
+裸写包名，npm 解析 `latest`，装到 0.1.5-alpha.2。这个版本是给 0.1.x 宿主用的，在 0.2.1 宿主上挂不上。装完 dsh 里看不到 Team 工具，`/lead-mode` 还是报「未挂载」。
+
+实测（2026-10-26，npm 11.20.0）：
+
+```
+$ npm view @deepseek-ai/dsh-experimental-agent-team-profile version
+0.1.5-alpha.2
+```
+
+所以本插件里所有出现安装命令的地方都带 `@0.2.1-rc.3`：persona prefix、`/lead-mode` 输出、启动 warn、SKILL.md。`test/preset.test.mjs` 与 `test/smoke.test.mjs` 都断言这个字符串在，防止以后被改回裸包名。
+
+要装 `alpha` 线的话自己换成 `@0.2.1-alpha.5`，别用裸名。
+
+## 与官方 standard 预设的差异
+
+只有 persona 一处。其余 21 行逐字段照抄 `standard`。
+
+| 项 | standard | lead-mode |
+|---|---|---|
+| persona prefix | `You are a coding agent powered by the {{model}} model.` | 中文 Lead 人设 + Agent Teams 前置检查 |
+| 其余 21 行 | — | 与 standard 逐字段相同 |
+
+classic subagent 四行（`tool-subagent-control`、`tool-subagent-list-agents`、`tool-subagent`、`tool-subagent-fork`）保持启用，没有禁用。Team 工具由 host 决定，不由预设决定。
+
+## 为什么预设里不塞 Team 运行时
+
+`@deepseek-ai/dsh-experimental-tool-agent-team` 的 `apply()` 监听全局 `agent/created`，给每一个 agent 装 Team 工具。它是 host 平面的插件，放进预设会漏到所有会话。
+
+所以本插件的定位是：预设 + skill + 提醒。开不开 Team 运行时，用户用官方 profile 包决定。
+
+## `/lead-mode` 输出什么
+
+三条信息：
+
+- Team 运行时在不在，在的话报 `maxMembers`
+- `lead-mode` 预设注册没有
+- 缺东西时给带版本号的安装命令
+
+依赖齐了返回 success，缺东西返回 error。缺东西不会静默。
+
+## 目录
+
+```
+package.json          包元数据，dsh.bundle.patch 指向 cordis.patch.yml
+cordis.patch.yml      两行 insert：本插件 + lead-mode 预设
+lib/index.js          host 半边：注册 skill、注册命令、启动自检
+skills/lead-mode/     Lead 工作法正文
+dsh-plugin.naming.json  命名清单
+test/                 行为断言，零依赖
+```
+
+## 开发
+
+```bash
+node --check lib/index.js
+node --test test/*.test.mjs
+node scripts/check-patch.mjs
+```
+
+测试零依赖，不用 `npm install`。`test/` 目录形式只在 Node 22+ 被接受，Node 20 会用 glob 展开。
+
+## License
+
+MIT

package/cordis.patch.yml

@@ -0,0 +1,170 @@
+# dsh-lead-mode bundle patch
+#
+# Two inserts.
+#
+# 1. `dsh-lead-mode` — this plugin's own host half. It registers the `lead-mode`
+#    runtime skill, the `/lead-mode` slash command, and the startup check that
+#    warns when the Team runtime is missing. The loader id equals the package
+#    name, matching `dsh-plugin.naming.json` (`names.loaderIds`).
+# 2. `preset-lead-mode` — the `lead-mode` agent preset. Its `config.plugins`
+#    mirrors the official `standard` preset row for row; the only difference is
+#    the persona prefix, which switches the session into Lead mode and states
+#    the Agent Teams prerequisite up front.
+#
+# This plugin does NOT mount the Team runtime. `@deepseek-ai/dsh-experimental-tool-agent-team`
+# listens on the global `agent/created` event and installs Team tools on every
+# agent, so it belongs to the host plane, not to a preset row. Users turn it on
+# with the official profile package:
+#
+#   dsh plugin --profile <name> add @deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3
+#
+# The version pin matters: bare `npm i` resolves `latest`, which is 0.1.5-alpha.2
+# and does not mount on a 0.2.1 host. `next` points at 0.2.1-rc.3.
+- insert:
+    - id: dsh-lead-mode
+      name: 'dsh-lead-mode'
+    - id: preset-lead-mode
+      name: '@deepseek-ai/dsh-agent-preset'
+      config:
+        id: lead-mode
+        name: Lead 模式
+        description: 拆活、派活、验收。需要先开 dsh 官方 Agent Teams。
+        order: 5
+        plugins:
+          - id: persona
+            name: '@deepseek-ai/dsh-persona'
+            config:
+              prefix: |
+                你是 Lead，负责拆活、派活、验收。动手的活尽量派出去。
+
+                开工第一件事：检查本会话有没有 spawn_teammate、send_message、team_task_create、team_task_update 这些工具。
+
+                没有的话，停下。只做一件事：告诉用户去开 dsh 官方的 Agent Teams，命令是
+
+                    dsh plugin --profile <你的 profile 名> add @deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3
+
+                不带版本号会装到 0.1.5-alpha.2，和 0.2.1 宿主对不上。装完重启 dsh。
+
+                这是本插件存在的主要理由。没有这些工具，你派不了活。不要自己硬干，不要假装能派活，也不要拿 subagent 凑数顶替 teammate。
+
+                有这些工具，就按 Lead 工作法干活：
+
+                - 派活自包含。teammate 看不到你的上下文，把目标、约束、验收标准、已知失败、绝对路径都写进 prompt。
+                - 写作用域不重叠。一人一块文件。分不开的活排成依赖。
+                - 共享任务走 list、get、claim（带 revision）、干、complete。
+                - 等齐必需的 teammate 再给最终答复。等之前先 list_agents 确认有人 running。
+                - 最终验证自己做：跑测试、看 diff、核数字。不要只信回报。
+          - id: agent-instructions
+            name: '@deepseek-ai/dsh-agent-instructions'
+            config:
+              maxBytes: 65536
+          - id: time-context
+            name: '@deepseek-ai/dsh-time-context'
+          - 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'
+          - 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-jobs
+            name: '@deepseek-ai/dsh-tool-jobs'
+          - id: tool-schedule
+            name: '@deepseek-ai/dsh-tool-schedule'
+          - id: skill-filesystem
+            name: '@deepseek-ai/dsh-skill-filesystem'
+          - id: tool-skill
+            name: '@deepseek-ai/dsh-tool-skill'
+          - id: command-goal
+            name: '@deepseek-ai/dsh-command-goal'
+          - id: tool-goal
+            name: '@deepseek-ai/dsh-tool-goal'
+          - 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 the user approves your plan through exit_plan_mode or 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.
+          - 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
+          - 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
+              - id: tool-subagent-fork
+                name: '@deepseek-ai/dsh-tool-subagent'
+                config:
+                  provider: fork
+                  toolName: subagent_fork
+              - id: workflow-ptc
+                name: '@deepseek-ai/dsh-workflow-ptc'
+                config:
+                  provider: spawn
+              - id: tool-workflow
+                name: '@deepseek-ai/dsh-tool-workflow'
+          - 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: true
+              searchTimeoutMs: 60000
+          - id: present
+            name: '@deepseek-ai/dsh-tool-present'
+          - id: tool-plugin-manager
+            name: '@deepseek-ai/dsh-plugin-manager/tools'
+            disabled: true
+          - id: tool-plugin-market
+            name: '@deepseek-ai/dsh-plugin-market/tools'
+            disabled: true

package/lib/index.js

@@ -0,0 +1,197 @@
+/**
+ * dsh-lead-mode host half.
+ *
+ * Three jobs: register the `lead-mode` runtime skill, register the `/lead-mode`
+ * slash command, and warn at startup when the Team runtime is absent.
+ *
+ * The plugin declares no `inject` of its own. Each surface waits for its own
+ * service through `ctx.inject()`, so a host missing `dsh-skill` still mounts the
+ * row and still gets the command. That is why registration is not guarded by a
+ * one-shot `ctx.get()`: a plain null check at apply time would lose the surface
+ * for good if the service fiber activates later in the boot order.
+ *
+ * @module dsh-lead-mode
+ */
+import { readFileSync } from 'node:fs'
+import { fileURLToPath } from 'node:url'
+
+/** Cordis plugin name. */
+export const name = 'lead-mode'
+
+/** Profile package that provides the Team runtime, pinned to the rc.3 line. */
+const TEAM_PROFILE_PACKAGE = '@deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3'
+
+/** Install command shown in every reminder. */
+const ENABLE_COMMAND = `dsh plugin --profile <你的 profile 名> add ${TEAM_PROFILE_PACKAGE}`
+
+/** Why the version pin matters, repeated wherever the command appears. */
+const VERSION_NOTE = '不带版本号会装到 0.1.5-alpha.2，和 0.2.1 宿主对不上。'
+
+/** Absolute path of the bundled skill body. */
+const SKILL_URL = new URL('../skills/lead-mode/SKILL.md', import.meta.url)
+
+/** Skill name shared by the file on disk, the runtime registration, and the naming manifest. */
+const SKILL_NAME = 'lead-mode'
+
+/** Command name shared by the registration and the naming manifest. */
+const COMMAND_NAME = 'lead-mode'
+
+/** Preset id declared in `cordis.patch.yml`. */
+const PRESET_ID = 'lead-mode'
+
+/**
+ * Read the bundled skill file and split off its YAML frontmatter.
+ *
+ * The runtime skill registry wants `description` as its own field, so the body
+ * handed to it must not repeat the frontmatter block. Reading synchronously
+ * keeps `apply` synchronous; the file is a few kilobytes shipped inside this
+ * package, so there is no I/O worth deferring.
+ *
+ * @returns the frontmatter description and the markdown body.
+ */
+function readBundledSkill() {
+  const path = fileURLToPath(SKILL_URL)
+  const raw = readFileSync(path, 'utf8')
+  const match = /^---\r?\n([\s\S]*?)\r?\n---\r?\n?/.exec(raw)
+  if (match === null) throw new Error(`${path} has no YAML frontmatter`)
+  const description = /^description:\s*(.+)$/m.exec(match[1])
+  if (description === null) throw new Error(`${path} frontmatter has no description`)
+  const content = raw.slice(match[0].length).trim()
+  if (content.length === 0) throw new Error(`${path} has an empty body`)
+  return { description: description[1].trim(), content, path }
+}
+
+/**
+ * Report whether the Team runtime is mounted.
+ *
+ * `agentTeams` is provided by `@deepseek-ai/dsh-experimental-agent-team`. Its
+ * absence is the normal state for a host that never installed the official
+ * profile package, so the check reads without throwing.
+ *
+ * @param ctx - a context that can resolve host services.
+ * @returns the mount state and, when present, the configured member cap.
+ */
+function teamRuntimeState(ctx) {
+  const agentTeams = ctx.get('agentTeams')
+  if (agentTeams === undefined) return { mounted: false }
+  return { mounted: true, maxMembers: agentTeams.config?.maxMembers }
+}
+
+/**
+ * Report whether the `lead-mode` preset reached the preset registry.
+ *
+ * The preset row lives in `cordis.patch.yml`; reading the registry back turns a
+ * broken row into a diagnostic instead of a silent no-op. An absent registry
+ * reports as `unknown` rather than `missing`, because this plugin cannot tell
+ * the two apart from here.
+ *
+ * @param ctx - a context that can resolve host services.
+ * @returns `present`, `missing`, or `unknown`.
+ */
+async function presetState(ctx) {
+  const registry = ctx.get('agentPresets')
+  if (registry === undefined) return 'unknown'
+  const presets = await registry.list()
+  return presets.some((preset) => preset.id === PRESET_ID) ? 'present' : 'missing'
+}
+
+/**
+ * Render the preset state as the sentence the command output uses.
+ *
+ * @param state - a value returned by `presetState`.
+ * @returns one Chinese sentence.
+ */
+function describePreset(state) {
+  if (state === 'present') return '已注册'
+  if (state === 'missing') return '未注册（cordis.patch.yml 里的 lead-mode 预设行没有生效）'
+  return '查不到（agentPresets 服务不在）'
+}
+
+/**
+ * Build the `/lead-mode` report.
+ *
+ * @param ctx - a context that can resolve host services.
+ * @returns a command result reporting dependency state and the install command.
+ */
+async function report(ctx) {
+  const team = teamRuntimeState(ctx)
+  const preset = await presetState(ctx)
+  const lines = []
+
+  if (team.mounted) {
+    const cap = team.maxMembers === undefined ? '' : `（maxMembers ${team.maxMembers}）`
+    lines.push(`Team 运行时：已挂载${cap}`)
+  } else {
+    lines.push('Team 运行时：未挂载')
+  }
+  lines.push(`lead-mode 预设：${describePreset(preset)}`)
+
+  if (team.mounted && preset === 'present') {
+    lines.push('')
+    lines.push('依赖齐了。切到 Lead 模式这个预设就能派活。')
+    return { kind: 'success', text: lines.join('\n') }
+  }
+
+  lines.push('')
+  if (!team.mounted) {
+    lines.push('缺 Team 运行时。装官方 profile 包：')
+    lines.push('')
+    lines.push(`    ${ENABLE_COMMAND}`)
+    lines.push('')
+    lines.push(`${VERSION_NOTE}装完重启 dsh。`)
+  }
+  if (preset === 'missing') {
+    lines.push('lead-mode 预设行没生效。检查 dsh 是否把这个包加进了 profile 的 bundle 列表。')
+  }
+  return { kind: 'error', text: lines.join('\n') }
+}
+
+/**
+ * Register the skill, the command, and the startup check.
+ *
+ * @param ctx - the plugin context.
+ */
+export function apply(ctx) {
+  const warn = (message) => ctx.logger.warn(message)
+
+  ctx.inject(['skills'], (skillsCtx) => {
+    let skill
+    try {
+      skill = readBundledSkill()
+    } catch (error) {
+      warn(`[lead-mode] 读不到 skills/lead-mode/SKILL.md，lead-mode skill 没注册：${String(error)}`)
+      return
+    }
+    skillsCtx.skills.register({
+      name: SKILL_NAME,
+      description: skill.description,
+      content: skill.content,
+      // `source` is required by the registry's load-time validation but is NOT
+      // defaulted by `register()`: `validateRuntimeSkill` (register) checks only
+      // name, description and invocation, while `validateDefinition` (load)
+      // throws unless `source` is a string. Omitting it registers fine and then
+      // fails every `skill` tool call with `source must be a string`.
+      source: 'dsh-lead-mode/skills/lead-mode/SKILL.md',
+      path: skill.path,
+      invocation: { modelInvocable: true, userInvocable: true },
+    })
+  })
+
+  ctx.inject(['commands'], (commandsCtx) => {
+    commandsCtx.commands.register({
+      name: COMMAND_NAME,
+      description: '检查 Lead 模式依赖是否就绪',
+      handler: () => report(commandsCtx),
+    })
+  })
+
+  if (ctx.get('skills') === undefined) {
+    warn('[lead-mode] skills 服务不在，lead-mode skill 暂时没注册。它会等 dsh-skill 挂载后再注册；一直不出现就检查 dsh-skill 是否装好。')
+  }
+  if (ctx.get('commands') === undefined) {
+    warn('[lead-mode] commands 服务不在，/lead-mode 命令暂时没注册。它会等 dsh-commands 挂载后再注册。')
+  }
+  if (ctx.get('agentTeams') === undefined) {
+    warn(`[lead-mode] 没检测到 Team 运行时（agentTeams 服务）。Lead 模式能切，但派不了活。装官方 profile 包：${ENABLE_COMMAND}。${VERSION_NOTE}`)
+  }
+}

package/package.json

@@ -1,6 +1,51 @@
 {
   "name": "dsh-lead-mode",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.1.0",
+  "description": "Lead 模式：一个 agent 预设、一个 skill、两条依赖提醒。预设与官方 standard 的差异只有 persona 一处。",
+  "type": "module",
+  "main": "lib/index.js",
+  "exports": {
+    ".": "./lib/index.js",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "lib",
+    "skills",
+    "cordis.patch.yml",
+    "README.md",
+    "README.en.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=20",
+    "dsh": ">=0.2.1-rc.2"
+  },
+  "dshTarget": "0.2.1-rc.3",
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  },
+  "keywords": [
+    "deepseek-harness",
+    "dsh",
+    "dsh-plugin",
+    "dshtag",
+    "agent-teams",
+    "agent-preset",
+    "lead-mode"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/xiebaiyuan/dsh-lead-mode.git"
+  },
+  "license": "MIT",
+  "peerDependencies": {
+    "@deepseek-ai/cordis": "^4.0.5",
+    "@deepseek-ai/dsh": ">=0.2.1-rc.2",
+    "@deepseek-ai/schemastery": "^3.18.5",
+    "@deepseek-ai/dsh-agent-preset-registry": ">=0.2.1-rc.2",
+    "@deepseek-ai/dsh-skill": ">=0.2.1-rc.2",
+    "@deepseek-ai/dsh-commands": ">=0.2.1-rc.2"
+  }
+}

package/skills/lead-mode/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: lead-mode
+description: Lead 工作法。当你要拆活、派活给 teammate、用共享任务板协作，或验收多路并行产出时用。
+---
+
+# Lead 工作法
+
+你是 Lead。你拆活、派活、验收。动手的活尽量派出去，别自己一个人干完。
+
+## 开工先确认能不能派活
+
+检查本会话有没有这些工具：`spawn_teammate`、`send_message`、`list_agents`、`wait_agent`、`team_task_create`、`team_task_update`。
+
+没有就停下。只做一件事：让用户去开 dsh 官方 Agent Teams，命令是
+
+```
+dsh plugin --profile <你的 profile 名> add @deepseek-ai/dsh-experimental-agent-team-profile@0.2.1-rc.3
+```
+
+不带版本号会装到 0.1.5-alpha.2，和 0.2.1 宿主对不上。
+
+不要自己硬干，也不要假装能派活。
+
+## 开工前对齐三件事
+
+派活之前先把这三件事写清楚，用户点头再动手：
+
+1. 目标是什么。
+2. 这次改动动哪些东西。
+3. 什么叫完成。写成能判定的验收标准，不要写「跑通就行」。
+
+目标或指令有疑问先问用户。别自己挑一个解释就开始干。
+
+## 派活必须自包含
+
+teammate 看不到你的上下文。它能看到的只有你写的那段 prompt。
+
+派活时把这些写全：
+
+- 目标、约束、验收标准
+- 已知的失败现象和报错原文
+- 相关文件路径，用绝对路径
+- 环境坑，比如本机 `diff` 是坏的要用 `/usr/bin/diff`
+
+派活 prompt 里写「按刚才说的做」等于没派。它不知道「刚才」。
+
+## 写作用域不重叠
+
+两个 teammate 同时改一个文件，改动会互相覆盖，而且谁都发现不了。
+
+派活前先分好文件归属，一人一块。分不开的活排成依赖，用 `team_task_create` 的 `blocked_by` 串起来。
+
+写作用域有重叠时，在 task 描述里写明重叠在哪、谁先谁后。别指望 teammate 自己协调。
+
+## 共享任务流程
+
+每个活都是一个共享任务。流程固定：
+
+1. `team_task_list` 看有哪些活、哪个 ready。
+2. `team_task_get` 读完整规格。
+3. `team_task_update` 带当前 `revision` 执行 `claim`。
+4. 干活。
+5. `team_task_update` 用最新 `revision` 执行 `complete`。
+
+`revision` 不对就是有人在你之前改过这条 task。重新 `get` 一次再操作，别硬顶。
+
+task 描述就是完整规格。规格写细一点，teammate 少问一轮。
+
+## 等 teammate 的规矩
+
+`wait_agent` 前先 `list_agents`，确认有人正在 running。没人在跑，`wait_agent` 立刻返回 noProgress，白等。
+
+没人在跑就先 `send_message` 唤醒，再等。
+
+`inactive` 只说明当前没有 turn 在执行，不代表活干完了、也不代表失败。看 task 状态判断。
+
+## 给最终答复前
+
+- 必需的 teammate 都等齐了再答。没等齐就说「还在跑」，别把半成品当结论。
+- 最终验证自己做：跑测试、看 diff、核数字。不要只信 teammate 的回报。
+- 回报里有「已通过」「已修复」这类话，去核证据。核不到就写「未验证」。
+- 偏离规格的地方单独列出来，别混在成功清单里。
+
+## 回报怎么写
+
+结论在前。文件清单、验收输出、偏离规格三块分开。
+
+没实测的数字不写精确值。不知道就写「未验证」。