delegate
Hand a complete brief to a ven role (coder, worker, reviewer, verifier) as a subagent when your agent can spawn one, or as a separate pass you run yourself when it can't. Use when a ven skill says to delegate to a role, or a task splits into slices with nothing left to decide.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- delegate
- metadata
- { "layer": "L1", "license": "MIT" }
- description
- Hand a complete brief to a ven role (coder, worker, reviewer, verifier) as a subagent when your agent can spawn one, or as a separate pass you run yourself when it can't. Use when a ven skill says to delegate to a role, or a task splits into slices with nothing left to decide.
02 资源文件 4
- 参考文档references/coder.md2.0 KB
- 参考文档references/reviewer.md1.1 KB
- 参考文档references/verifier.md996 B
- 参考文档references/worker.md1.1 KB
03 SKILL.md 正文
Delegate
A role is a brief template plus a model setting. The role decides how the work is done; your brief decides what.
| Role | For | Model setting | Brief template |
|---|---|---|---|
| coder | one ticket end to end, test-first, in its own worktree | coder_model |
references/coder.md |
| worker | one fully specified edit, one slice of a fan-out, or a read-only probe | swarm_model |
references/worker.md |
| reviewer | one review lens, blind to the other lenses | coder_model; orchestrator_model for the high-risk lens |
references/reviewer.md |
| verifier | checking citations and proof claims, read-only | swarm_model |
references/verifier.md |
Read a setting with ven-profile config <setting>. inherit means your own model. The budget tier (ven-profile config budget_tier) sets effort where your agent supports it: lean low, max high, standard the default.
1. Write the brief
A brief drops to a role only when it is complete: inputs, exact files, the expected output shape, a check command from the profile, and the playbook and step for the result trailer. A brief that says "decide" or "figure out" stays with you.
Add the skills to load: the ones the calling skill names, and for each pack that ven-profile packs-for <brief files> returns, its skills.
Put the role's template first, then the brief.
2. Hand it off
Your agent can spawn subagents: spawn one per brief, independent briefs all at once. Pass the role's model unless it is inherit. A coder works in its own worktree: use your agent's worktree isolation, or git worktree add one for it and put the path in the brief. Run long briefs in the background when your agent allows it.
It can't: run each brief yourself, one at a time, as a separate pass. Before each pass, write down what you concluded so far, then work only from the brief. A reviewer pass reads the diff and its own lens, never another lens's findings. Write each pass's result in full before the next pass starts; synthesis comes after the last one.
3. Take the result
Every result ends with a VEN-RESULT trailer. Log it:
ven-decisions add --playbook <from the trailer> --step <step> --decision "<decision, or BLOCKED: question>" --evidence "<evidence>"
BLOCKED: <question>: answer it from the spec or the code, or ask the user when the call is theirs, then continue the same subagent if your agent can, so it keeps its worktree and context. Never let a role guess.DONEis a claim. Read the diff and the artifact, and check its logged verify pass (ven-decisions list), before you merge or report it.
04 同仓库更多 Skills
yeet
Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.
write-docs
Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.
why
Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.
verify
Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.
unslop
Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.
type-discipline
Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.