Files
STM32F4-Base/.dsh/plugins/dsh-plugin-subagent-roles/examples/delegation-prompts.md
T
wandering1 9e538d2809
CI / 静态门禁 (pre-commit) (push) Failing after 43s
CI / 主机侧单测 (MSVC) (push) Failing after 24s
feat(dsh): 门禁账本插件接入 + 角色绑定跨重启还原
二、门禁与唤醒(新插件 dsh-plugin-team-ledger 0.2.0)
宿主 Agent Teams 缺两块能力,补在独立仓
D:/Code/AI/dsh-plugin-team-ledger:

- 状态存放:<工作区>/.dsh/team/gate.jsonl 追加账本,记验收
  清单、实测证据、认领历史,跨重启存活;canonical JSON +
  fsync,坏尾行截断恢复。
- 唤醒模型:门禁推进后按事件计划唤醒下一责任人,借活体
  Lead 作 caller 走宿主 sendMessage;无定时器;30 分钟滑动
  窗口限 4 次防复活风暴。
- 验收独立性由机器强制:执行人/历史认领者不能 accept,
  checklist 逐项 passed=true 缺一不可。
- team_member_revive(Lead 专用):成员模型路由死亡后的
  复活通道——可换 provider/model,再经 subagents.sendMessage
  冷恢复唤醒,绕过宿主 roster 的 phase=active 门禁。

二、角色绑定跨重启还原(roles fork 0.5.2)
persona 与工具白名单只有运行中 agent 的内存态,宿主重启后
冷恢复的成员既无 persona 也无白名单——实测出现 doc-writer
成员带全量工具面(qq_*/ImageGen),属静默权限放大。改为
注入成功时持久化 childId -> {roleId, cwd} 到
~/.dsh/role-inject-bindings.json,并在 agent/created 时重放。
追加 team_member_rebind 补绑定,覆盖 0.5.2 之前已存在的成员。

三、配套
- .dsh/roles 八个角色白名单加入门禁工具;AGENTS.md 委派策略
  补门禁/复活/重绑三套操作口径。
- docs/环境与部署/子Agent角色自动注入实现说明.md 新增
  §5.1,记录绑定机制、存量成员缺口与「成员自省不可全信」的
  台架教训。
2026-11-16 00:42:51 +08:00

97 lines
4.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Role delegation prompts (web verifier)
English | [中文](delegation-prompts.zh.md)
> This is a template: replace the angle-bracket placeholders with your own values.
> Roles are defined in `<project>/.dsh/roles/<id>.md` (frontmatter: `provider` / `model` / `reasoningEffort` / `tools` / `maxToolCalls`; body: persona).
> Editing a role file takes effect immediately — no `dsh web` restart.
---
## 0. What you say to the main agent
**Natural trigger** — the main agent picks the role from the catalog itself:
```text
Use web-verifier to verify the changes to "<page/feature>": run <your E2E command> and report against the full-coverage criteria in <your verification SOP>. Do not drive the browser yourself.
```
**Add boundaries when they matter:**
```text
The verifier only verifies: it does not modify files and does not touch the backend. If a service needs a restart, you (the main agent) do that first.
```
---
## 1. Dispatch template (main agent → subagent)
```text
TASK — state it first: verify with a real browser that <page/feature> still works, and report full coverage.
TARGET
- Project root: <project root>
- Frontend directory: <frontend directory> (dev URL <dev URL>)
- Backend: <backend URL> — read-only for you; do not start or stop it
- Verification SOP (read it first): <project root>/.dsh/skills/<your verification skill>/SKILL.md
STEPS
1. If the project has a lease or mutex convention for shared resources (dev servers, devices): take the lock, refresh its heartbeat after every step, and release it when done. Read-only probes need no lock.
2. Read the project's own instructions (AGENTS.md and friends) and the SOP above, then confirm service state: <status command>.
3. Run the cases: cd <frontend directory> && <E2E command>. Credentials come from the project docs.
4. If the SOP asks for a "feature list → test cases" mapping table, complete it before running, and cover every interactive control on the page: search, filter and reset, every row action, and every control inside drawers and dialogs.
5. Console guard: a [Global Error] or an uncaught exception fails the run. Rate-limit noise (for example 429) may be filtered, but report it when it affects an assertion.
6. If the project is localized: switch language with the real control, assert that the interface text changes, then switch back.
ACCEPTANCE
- The result of <E2E command>, plus a per-item coverage verdict (covered / not covered) in the project's own terms.
- Anything you could not cover must be listed as an explicit "not covered" item with status WAITING; "N passed" on its own is not acceptance.
- On failure, attach reproducible evidence: DOM state, logs, screenshots, or a trace path.
FORBIDDEN
- Modifying any project file — edit/write and shell redirection are out; only the lease directory may be created.
- Starting or stopping the backend, running migrations or database resets, reading or writing the database, seeding data through curl or API calls.
- Starting another dev server or changing ports; do not bypass the project's own start script.
- Calling tools unrelated to the task (other MCP tools, delegation tools, and so on).
REPORT: 1 what you did (start with the tool name and the target path) 2 what you observed (case names, pass/fail, coverage verdict) 3 problems and suggestions 4 status: DONE or WAITING
```
---
## 2. Budgeting a role (plugin >= 0.4.0)
A role file may cap how many tool calls its child gets. Give a read-only explorer
enough to finish the inventory, and a run-time verifier far less — it mostly waits
on commands:
```yaml
---
description: Inventory a cross-cutting change (read-only)
tools: [read, grep, glob, bash]
maxToolCalls: 30 # measured in CALLS, not turns: parallel calls each count
maxToolCallsScope: delegation
onToolCallBudget: wrap-up # inject "wrap up now", then tolerate graceToolCalls more
graceToolCalls: 1
---
You are a read-only explorer. Never modify a file; report findings and open questions.
```
Rules of thumb, from real runs (a 19-call inventory and a 25-call review both blew
through a verbal "8 steps" guard that nothing enforced):
| Role type | Suggested `maxToolCalls` |
|---|---|
| Read-only exploration (>= 5 files) | 30–40 |
| Static review | 40–60 |
| Run-time verification (mostly commands) | 15–20 |
| Omitted or `0` | unlimited — the escape hatch for a very large repository |
Two things worth knowing:
- **The unit is calls, not turns.** Three parallel reads in one step are three calls,
and a call refused by policy still counts — the child already spent the decision.
- **Crossing the limit triggers**, not reaching it, and that call is stopped before it
finishes. `graceToolCalls: 0` makes `wrap-up` behave exactly like `interrupt`.