dsh-plugin-prompt-tool 2.1.0 → 3.0.0

package/modules/soul/module.yml

@@ -0,0 +1,311 @@
+# 灵魂架构（推送层 + 判据 + 按需条目 + 状态规则）
+# 工具面由本项目通用能力提供：module_file_read/append 读写模块私有文件，module_manifest 执行 assets/manifest.yml，module_variables 读写状态；不提供 soul 专属工具。
+# 正文放 assets/，用 templateFile 引用；运行源是本模块，soul 仓库是作者稿。
+id: soul
+name: 灵魂架构（判据与推送）
+version: 1.0.0
+engineCompat: ">=0.7.2"
+description: 灵魂架构模块（资产 + 规则）：常驻四条判据与子代理硬线，按需注入五层/ECHO/VITAL/账本，压缩后与每 12 轮各提醒一次；工具由项目内置引擎提供，本模块分发规则、资产与装配清单。
+meta:
+  source: manual
+modules:
+  - rule-engine
+  - module-file-tools
+  - module-manifest-tools
+  - module-variable-tools
+order: 10
+variables:
+  # 状态键由本模块声明；引擎只按普通模块变量处理，不认 soul 前缀。
+  plan_step: ''
+  plan_at: ''
+  check_verdict: ''
+  check_at: ''
+  check_failed: '0'
+  scaffold_done: ''
+  scaffold_root: data
+  ledger_seq: '0'
+  ledger_open: '0'
+rules:
+  - id: soul-core
+    name: 四条判据（常驻）
+    enabled: true
+    layer: runtime-context
+    if:
+      scope:
+        audience: main
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-core
+          strategy: static
+          layer: runtime-context
+          order: 132
+          params:
+            contextName: agent:soul-core
+          templateFile: ./assets/criteria.md
+
+  - id: soul-core-sub
+    name: 子代理硬线
+    enabled: true
+    layer: subagent-start
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-core-sub
+          strategy: static
+          layer: subagent-start
+          order: 216
+          templateFile: ./assets/core-hard.md
+
+  - id: soul-layers
+    name: 五层（按需）
+    enabled: true
+    layer: pre-step
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-layers
+          strategy: context-activation
+          layer: pre-step
+          order: 120
+          position: before-all
+          role: user
+          templateFile: ./assets/layers.md
+          params:
+            constant: false
+            keys: [灵魂, 五层, ECHO, VITAL, 架构]
+            secondaryKeys: []
+            selectiveLogic: AND_ANY
+            wordBoundary: ascii-token
+            activation:
+              scan: history
+              scanDepth: 6
+              selective: false
+
+  - id: soul-echo
+    name: ECHO 机制（按需）
+    enabled: true
+    layer: pre-step
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-echo
+          strategy: context-activation
+          layer: pre-step
+          order: 121
+          position: before-all
+          role: user
+          templateFile: ./assets/echo.md
+          params:
+            constant: false
+            keys: [压缩, 上下文满, 摘要, 找不回, 退化]
+            secondaryKeys: []
+            selectiveLogic: AND_ANY
+            wordBoundary: ascii-token
+            activation:
+              scan: history
+              scanDepth: 8
+              selective: false
+
+  - id: soul-vital
+    name: VITAL 机制（按需）
+    enabled: true
+    layer: pre-step
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-vital
+          strategy: context-activation
+          layer: pre-step
+          order: 122
+          position: before-all
+          role: user
+          templateFile: ./assets/vital.md
+          params:
+            constant: false
+            keys: [预算, 烧光, 打转, 空转, 该停, 阈值]
+            secondaryKeys: []
+            selectiveLogic: AND_ANY
+            wordBoundary: ascii-token
+            activation:
+              scan: history
+              scanDepth: 8
+              selective: false
+
+  - id: soul-ledger
+    name: 账本纪律（按需）
+    enabled: true
+    layer: pre-step
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-ledger
+          strategy: context-activation
+          layer: pre-step
+          order: 123
+          position: before-all
+          role: user
+          templateFile: ./assets/ledger.md
+          params:
+            constant: false
+            keys: [账本, 未结, 承诺, 只追加]
+            secondaryKeys: []
+            selectiveLogic: AND_ANY
+            wordBoundary: ascii-token
+            activation:
+              scan: history
+              scanDepth: 6
+              selective: false
+
+  - id: soul-post-compaction
+    name: 压缩后指针纪律
+    enabled: true
+    layer: system-section
+    if:
+      phase:
+        compacted: true
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-post-compaction
+          strategy: static
+          layer: system-section
+          order: 245
+          text: |-
+            压缩摘要里每条结论都要能回到原文；回不去的写成检索入口，不要写成断言。继续推理前先核对前提。
+
+  - id: soul-tick
+    name: 每 12 轮自检
+    enabled: true
+    layer: system-section
+    if:
+      count:
+        of: turn
+        every: 12
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-tick
+          strategy: static
+          layer: system-section
+          order: 246
+          text: |-
+            自检三问：压缩后丢掉的东西还能按指针找回吗？现在是不是在错误的前提上继续推理？「还能更好」和「没做完」分得开吗？
+
+  # 状态规则：变量谓词在挂载期按来源模块（soul）读取有效值。
+  # 工具主语写死 moduleId: soul；模块被复制或改名后需要同步这些正文。
+  - id: soul-plan
+    name: 计划纪律（首轮，未写计划时）
+    enabled: true
+    layer: pre-step
+    if:
+      all:
+        - variable:
+            key: plan_step
+            op: eq
+            value: ''
+        - count:
+            of: user-message
+            per: session
+            max: 1
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-plan
+          layer: pre-step
+          strategy: static
+          position: before-all
+          order: 124
+          role: user
+          text: |-
+            先定一步计划再动手：用 module_variables（moduleId: soul，scope: module）读取 plan_step 与 plan_at，
+            写入一行「下一步 + 判据」，带回 expectedRevisions；计划变了就覆盖，不要留旧计划当真相。
+            连续三步没有进展时停下来重写计划，而不是继续加动作。
+            需要看装配进度时先 module_manifest（moduleId: soul）action=next，再决定改计划还是先装配。
+
+  - id: soul-scaffold
+    name: 书房装配（首轮，未装配时）
+    enabled: true
+    layer: pre-step
+    if:
+      all:
+        - variable:
+            key: scaffold_done
+            op: eq
+            value: ''
+        - count:
+            of: user-message
+            per: session
+            max: 1
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-scaffold
+          layer: pre-step
+          strategy: static
+          position: before-all
+          order: 125
+          role: user
+          text: |-
+            书房还没装配：先 module_manifest（moduleId: soul）action=next 看第一条缺失，
+            再 action=check 看已有文件的状况，最后由用户决定是否 action=apply。
+            AGENTS.md 落在 data/AGENTS.md（模板 assets/templates/agents-template.md），已存在不覆盖，
+            它不是工作区指令文件；apply 只建目录、只落缺失文件，已存在的一律不碰；
+            装配完成后把 scaffold_done 置为 true。
+
+  - id: soul-check
+    name: 检查失败处置
+    enabled: true
+    layer: system-section
+    if:
+      variable:
+        key: check_failed
+        op: gt
+        value: '0'
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-check
+          layer: system-section
+          strategy: static
+          order: 247
+          text: |-
+            上一轮自检有失败项：先 module_manifest（moduleId: soul）action=check 重新核对，
+            把结论写进 check_verdict（ok/fail）、check_at（时间）与 check_failed（失败数），
+            再说清是哪一条、证据是什么、下一步改哪个文件或哪条规则；
+            不要用「已修复」代替重新检查，也不要把失败项藏进总结。
+
+  - id: soul-ledger-open
+    name: 未结账本提醒
+    enabled: true
+    layer: pre-step
+    if:
+      variable:
+        key: ledger_open
+        op: gt
+        value: '0'
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: soul-ledger-open
+          layer: pre-step
+          strategy: static
+          position: before-all
+          order: 126
+          role: user
+          text: |-
+            账本还有未结事项：回复里逐条收口，或说清为什么先放着。
+            需要追加时用 module_file_append（moduleId: soul，path: data/02-墨.jsonl，entry: {...}），
+            只往后加，不改旧行；收口后把 ledger_open 减到 0。

package/modules/superpowers/module.yml

@@ -0,0 +1,122 @@
+# Superpowers 引导 —— 上游 using-superpowers 的 DSH 常驻副本。
+#
+# 来源：obra/superpowers v7.0.1 的 `skills/using-superpowers/SKILL.md` 原文
+# （与 $DSH_HOME/skills/using-superpowers/SKILL.md 同源）。上游用 SessionStart
+# hook 注入整份技能正文；DSH 没有该 hook 通道，本模块把同一份正文放进常驻
+# system-section。DSH 适配只有三处：skill_search/skill_load 调用方式、
+# superpowers:<name> 前缀映射、DSH 平台适配参考文件的路径。
+#
+# Skill Routing 表按上游 README 的「The Basic Workflow」（brainstorming →
+# using-git-worktrees → writing-plans → subagent-driven-development/executing-plans
+# → test-driven-development → requesting-code-review → finishing-a-development-branch）
+# 与「Skills Library」分类整理，技能名与描述保持英文原文。
+#
+# 只进主会话：上游 <SUBAGENT-STOP> 段保留在正文里，这里再用 scope 门做硬保证。
+# 与 ponytail 的冲突：用户指令优先；要消歧就在工作台停用一个，停用即回滚。
+
+id: superpowers
+name: Superpowers 技能优先引导（bootstrap）
+version: 1.3.0
+engineCompat: ">=0.4.2"
+description: 常驻注入上游 using-superpowers 技能原文（v7.0.1）：任何回答或动作前先查技能，附技能优先级、英文路由表、红旗清单与用户指令优先级。技能正文留在技能库，本模块不分发技能文件。
+meta:
+  source: manual
+modules:
+  - rule-engine
+order: 8
+rules:
+  - id: superpowers-bootstrap
+    name: Superpowers 引导（常驻·上游原文）
+    enabled: true
+    if:
+      scope:
+        audience: main
+    layer: system-section
+    then:
+      - id: inject
+        kind: inject-text
+        config:
+          id: superpowers-bootstrap
+          strategy: static
+          layer: system-section
+          order: 210
+          text: |-
+            You have superpowers.
+
+            Below is the full content of the `using-superpowers` skill. For all other skills, use `skill_search` to find one and `skill_load` to load it by exact name. Cross-references that upstream spells `superpowers:<name>` are simply `<name>` here.
+
+            <SUBAGENT-STOP>
+            If you were dispatched as a subagent to execute a specific task, ignore this skill.
+            </SUBAGENT-STOP>
+
+            <EXTREMELY-IMPORTANT>
+            If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
+
+            IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
+
+            This is not negotiable. You cannot rationalize your way out of this.
+            </EXTREMELY-IMPORTANT>
+
+            ## The Rule
+
+            **Invoke relevant or requested skills BEFORE any response or action** — including clarifying questions, exploring the codebase, or checking files. If it turns out wrong for the situation, you don't have to use it.
+
+            **Before entering plan mode:** if you haven't already brainstormed, invoke the brainstorming skill first.
+
+            Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
+
+            ## Skill Priority
+
+            When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. Brainstorming and systematic-debugging are Superpowers' most common process skills, but the rule holds for any of them.
+
+            - "Let's build X" → superpowers:brainstorming first, then implementation skills.
+            - "Fix this bug" → superpowers:systematic-debugging first, then domain skills.
+
+            ## Skill Routing
+
+            | Task signal | Load first |
+            |---|---|
+            | Building something new; requirements still forming | `brainstorming` |
+            | Design approved; need an isolated workspace | `using-git-worktrees` |
+            | Design approved; ready to break work into tasks | `writing-plans` |
+            | Plan ready; execute task by task | `subagent-driven-development` (fresh subagent per task, review after each); `executing-plans` when inline is cheaper or no subagent tool |
+            | About to write or change implementation code | `test-driven-development` (RED-GREEN-REFACTOR) |
+            | Task boundary reached; review against the plan | `requesting-code-review` |
+            | All tasks done; merge / PR / cleanup decision | `finishing-a-development-branch` |
+            | Bug, failing test, unexplained behavior | `systematic-debugging` |
+            | About to claim the work is complete | `verification-before-completion` |
+            | Review feedback received | `receiving-code-review` |
+            | Several independent tasks that can run in parallel | `dispatching-parallel-agents` |
+            | Session misbehaved; diagnose the process | `diagnosing-superpowers` |
+            | Creating or editing a skill | `writing-skills` |
+
+            If no row matches, search with words that literally appear in the skill's name or description; an empty query lists every visible skill. When the exact name is known, `skill_load` it directly.
+
+            ## Red Flags
+
+            These thoughts mean STOP—you're rationalizing:
+
+            | Thought | Reality |
+            |---------|---------|
+            | "This is just a simple question" | Questions are tasks. Check for skills. |
+            | "I need more context first" | Skill check comes BEFORE clarifying questions. |
+            | "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
+            | "I can check git/files quickly" | Files lack conversation context. Check for skills. |
+            | "Let me gather information first" | Skills tell you HOW to gather information. |
+            | "This doesn't need a formal skill" | If a skill exists, use it. |
+            | "I remember this skill" | Skills evolve. Read current version. |
+            | "This doesn't count as a task" | Action = task. Check for skills. |
+            | "The skill is overkill" | Simple things become complex. Use it. |
+            | "I'll just do this one thing first" | Check BEFORE doing anything. |
+            | "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
+            | "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
+
+            ## Platform Adaptation
+
+            If your harness appears here, read its reference file for special instructions:
+
+            - DSH (DeepSeek Harness): `references/dsh-tools.md` in `$DSH_HOME/skills/using-superpowers/`
+
+            ## User Instructions
+
+            User instructions (CLAUDE.md, AGENTS.md, GEMINI.md, etc, direct requests) take precedence over skills, which in turn override default behavior. Only skip skill workflows or instructions when your human partner has explicitly told you to.

package/modules/tool-surface/module.yml

@@ -1,67 +1,71 @@
-# 工具面收窄 —— 常驻核心集 + dev_tool_search 按需解锁。
+# 工具面收窄 —— 常驻核心集 + tool_search 按需解锁。
 #
-# 为什么：工具面实测 **156 个工具、描述合计 46894 字符（≈12K token）**，每个请求都付，
-# 而多数请求只用到其中几个。收窄到核心集后只剩 10 个左右。
+# 为什么：工具面实测 **156 个工具、描述合计 46894 字符（约 12K token）**，每个请求都付。
+# 收窄到核心集后只剩十来个，其余按需解锁。
 #
-# 三件东西互相依赖，缺一件就退化（详见 docs/engine-reuse.md 的「工具面收窄与按需解锁」）：
-#   1. 本模块的 `narrow-tools` 规则 —— 常驻白名单 `allow` + 动态白名单 `allowFrom`
-#   2. `dev-tool-search` 组合源行 —— 唯一发现入口，模型靠它搜索并解锁
-#   3. `allowFrom` 读回 —— 解锁名写进持久 `tool/call` 参数，下次请求起生效
-# 只挂插件不配 allowFrom 的话，解锁是**一次性的**（当次请求用完即被裁）。
+# `tool-visibility` 声明目录与 SDK 正文的呈现、执行闸和发现来源。
+# 常驻集只在这里写一次；首轮提示由普通注入动作组合。
 #
-# 相位用 any 两支表达（单个 phase 节点无法表达「两个相位都命中」）：
-#   `promoted` 的缺省是 **true**（= 只匹配已晋升，不是「任意」）；而 `promoted: 'ignore'`
-#   要求同时声明只接受布尔值的 `compacted`。所以：
-#     支 1 `promoted: true`                     → 已晋升（不论压缩与否）
-#     支 2 `{compacted: true, promoted: false}`  → 压缩后未晋升
-#   **首轮（未晋升且未压缩）刻意不收窄**——先让模型看到完整目录，再随相位推进收窄；
-#   长会话必然进入上面两支，省下的正是大头。
+# 解锁的生效时机：声明在每个 model step 前重算，解锁在下一步的模型请求里已经可见。
+# `requireMatch: true` 是刻意的：任一常驻工具缺失（或模型解锁了不存在的名字）就放弃裁剪、
+# 暴露完整目录——收窄错了会让当前工作流调不到工具，比多花上下文严重。
 #
-# `requireMatch: true` 是刻意的：任一 allow 工具缺失（或模型解锁了一个不存在的名字）
-# 就放弃裁剪、暴露完整目录。宁可多给上下文，也不静默裁成空目录——收窄错了会让当前
-# 工作流调不到工具，那是比多花 token 严重得多的故障。
-#
-# 工具名必须与**实际装配名**一致：本项目 harness 是 `pwsh`（不是 `bash`）、
-# `edit` + `write`（不是 `str_replace_editor`）。写错名字的后果很隐蔽——写进 allow 的
-# 名字不存在会触发 requireMatch 的 fail-open，表现为「收窄没生效」而不是报错。
+# 工具名必须与**实际装配名**一致：本项目 harness 是 `pwsh`、`edit` + `write`；
+# `bash` 由平台各自提供——Windows 是本模块声明的 `tool-git-bash` 行（Git Bash，`bash -c`），
+# POSIX 是官方持久 bash。写错名字会触发 requireMatch 的 fail-open，表现为「收窄没生效」。
 #
 # 停用即回滚：本模块在 config.yml 的 enabled 里删掉即可，重启后工具面完全恢复。
 
 id: tool-surface
 name: 工具面收窄（核心文件与任务集）
-version: 1.0.0
-engineCompat: ">=0.4.2"
-description: 把工具面收窄到常驻核心集（pwsh/read/write/edit/glob/grep/todo_write/skill_search/skill_load/dev_tool_search），其余由 dev_tool_search 按需解锁；解锁名经 allowFrom 从持久 tool/call 参数回收，跨请求与压缩保留。实测工具描述合计 46894 字符。
+version: 2.0.0
+engineCompat: ">=0.7.2"
+description: 把工具面收窄到常驻核心集（bash/pwsh/read/write/edit/glob/grep/todo_write/skill_search/skill_load/tool_search），其余由 tool_search 按需解锁；解锁名从持久调用记录（顶层 tool/call 或 PTC tool/ptc-dispatch）参数回收，跨请求与压缩保留。
 meta:
   source: manual
 modules:
   - rule-engine
-  - dev-tool-search
+  - tool-search
+  # Windows Git Bash 适配行：以 `bash` 之名注册工具、实际执行 Git Bash。
+  # 不声明 layerSettings 覆盖 toolGitBashEnabled：能力卡默认就是 true，写出来只会让本模块
+  # 覆盖全局开关（内置模块只声明 rules/modules 的声明面契约）。
+  - tool-git-bash
 order: 7
 rules:
   - id: tool-surface-resident
     name: 工具面收窄（核心文件与任务集）
     enabled: true
-    if:
-      any:
-        - phase: { promoteOn: either, includeSubagents: true, promoted: true }
-        - phase: { promoteOn: either, includeSubagents: true, compacted: true, promoted: false }
     then:
       - id: narrow-tools
-        kind: assembly
-        target:
-          tools:
-            allow:
-              - pwsh
-              - read
-              - write
-              - edit
-              - glob
-              - grep
-              - todo_write
-              - skill_search
-              - skill_load
-              - dev_tool_search
-            # 解锁项从 dev_tool_search 的持久调用参数回收（{ tool, key } 精确匹配）。
-            allowFrom: { tool: dev_tool_search, key: toolNames }
-            requireMatch: true
+        kind: tool-visibility
+        allow:
+          - pwsh
+          - read
+          - write
+          - edit
+          - glob
+          - grep
+          - todo_write
+          - skill_search
+          - skill_load
+          - tool_search
+          # 平台各自的 bash 名：装配里没有提供方时这里就是缺失名，收窄整体失效。
+          - bash
+        discovery: { kind: tools }
+        requireMatch: true
+      - if:
+          count:
+            of: user-message
+            max: 1
+        then:
+          - id: discovery-notice
+            kind: inject-text
+            config:
+              layer: pre-step
+              strategy: placeholder
+              fill: tool-catalog
+              position: after-all
+              dedupe: session
+              text: 常驻工具：{{RESIDENT_TOOLS}}。缺少所需工具时，先用 {{DISCOVERY_TOOL}} 搜索并解锁。
+              params:
+                action: narrow-tools