delegate
Before assigning work or choosing helpers, reuse the best-fitting profile or service, name one result owner, and choose a supported model for each handoff.
- License 许可
- Apache-2.0
- 所属仓库
- brocrew/brocrew
- 最近更新
- 2026-11-15
- Stars
- ★ 78
- Forks
- 6
01 前言 Front Matter
- name
- delegate
- description
- Before assigning work or choosing helpers, reuse the best-fitting profile or service, name one result owner, and choose a supported model for each handoff.
03 SKILL.md 正文
Give work to a fitting owner
Start with the outcome and its checkable done condition. Read relevant work and files before recreating them, and check list_profiles before choosing or creating anyone. Use the history that matters; an existing conversation does not automatically know what was said in yours. Give the owner a self-contained brief, useful inputs, scope, assumptions, output destination when needed, and the result you expect back. Keep extra detail in an input file. Follow the tool's current fields, limits, permissions and refusals. Before selecting an owner, decide what expertise the whole outcome actually needs and which capabilities are available now. A profile's name is a clue, not proof of fit: check its recent work or ask it when a material capability is uncertain. If the person's request already names an owner, use that choice within permissions unless it conflicts with the work or access needed. A busy suitable profile may still receive a piece; do not create a duplicate identity merely to avoid a queue. Use a new profile when its distinct expertise will be useful again.
Choose one owner for the whole result. The best fit is the profile that can judge and integrate it, which may be broader than any one part. The owner may assign focused parts while retaining the final decision. Name profiles for lasting expertise, not the current task, item or batch. Reuse them so their knowledge grows. Do not make numbered copies or separate profiles for differently labelled slices of the same work; put ranges in piece titles. A distinct profile is useful when recurring work needs different expertise, tools or access, or when unrelated knowledge would crowd its memory. A project lead is useful only when several owners need continuing coordination; duration or a folder alone is not a reason.
A normal profile handles judgement or work that can run side by side. Use a service for small mechanical tasks on one shared browser, device or account that cannot be used by two at once and serves many callers. A service processes one piece at a time in order; give it work like any agent, without parallel work. If services are off, read the refusal, use a suitable normal agent for permitted work, and tell the person once that Team can enable services. Do not retry a permanently refused creation. Create a new profile only when no suitable one exists and the current permissions allow it.
For specialists, keep the judgement and hand off noisy, separable work such as bulk reading, logs or mechanical tool use when expertise, context saved or speed outweighs coordination. A small task, an exact installed procedure, tightly connected steps, or an expensive handoff can stay with the specialist. BroBot routes substantive work and reviews it; it does not duplicate the owner's research or implementation. Prefer BroCrew agents so the person can see and revisit their work. A helper reports a concise result and keeps needed evidence on the piece.
At every give_work or create_agent handoff, explicitly choose a supported model and an effort level only when offered; respect the person's locked choices. Choose from known capability, cost and speed, not the model's name or your own setting. Routine extraction or mechanical work usually needs less reasoning; ordinary research and planning need proportionate effort; use higher effort for hard trade-offs, costly errors or demonstrated quality failures. Explain the choice briefly in the brief. If comparisons are uncertain, use a capable documented choice and state that uncertainty. Do not silently inherit an expensive default.
The owner combines parts, checks the outcome and handles corrections. Use split-work when the assignment needs several pieces; ask-and-wait for decisions or stalled work; hand-back before completion. If a relevant skill is unavailable, use permitted tools and report a blocking gap rather than inventing a capability.
04 同仓库更多 Skills
split-work
Before dividing an outcome, choose bounded pieces by project kind, outputs and dependencies; keep one owner responsible for integration.
remember
Before unfamiliar work, after a tested reusable lesson, or on a memory request, use permitted saved methods and memory.
hand-back
During work or before completion, keep evidence findable, resolve required results and questions, and hand back once.
build-software
Before building software or any file-changing script or command, name one owner and an independent checker and verify the result.
build-a-team
Use delegate to choose helpers.
ask-and-wait
When the person must answer or act, track the question or task, name what ends the wait, and manage the follow-up.