hand-back
During work or before completion, keep evidence findable, resolve required results and questions, and hand back once.
- License 许可
- Apache-2.0
- 所属仓库
- brocrew/brocrew
- 最近更新
- 2026-11-15
- Stars
- ★ 78
- Forks
- 6
01 前言 Front Matter
- name
- hand-back
- description
- During work or before completion, keep evidence findable, resolve required results and questions, and hand back once.
03 SKILL.md 正文
Return a complete, honest result
Keep routine status, grouped findings and working detail in the piece or project record. Send a message before completion only when it changes what your giver or the person should do: a blocking question, decision, material change, urgent issue or one useful milestone. Say why it matters now. Avoid tool-by-tool updates and routine polling. For continuing help, record each round on the same open piece and use ask-and-wait for the next person's reply; a milestone note alone does not mark a wait.
Before handback, compare the actual result with the recorded done condition. Check needed child results, open questions, evidence and unresolved findings. Bring in required results; deliberately remove a dependency only when it no longer affects the agreed outcome, and record why. Never announce completion while a required answer or result is outstanding. Give one completion message after review, and name what was not checked. An estimate near a stated limit needs its margin and material uncertainty in plain words. Use the person's requested scope; do not relabel incomplete work as success. For research, say which sources were actually checked and where access or uncertainty limits the claim. For writing, check audience, language and requested form; for planning, identify assumptions that drive the recommendation; for continuing help, report observed progress rather than implying the goal was mastered. These are outcome checks, not extra deliverables. If the giver changes the done condition, confirm the recorded condition before judging completion.
The owner keeps project records and integrates corrections. For a file-based result, keep the full detail and relevant evidence in supported files on the piece; a path mentioned only in chat is not a kept file. Use find_files and read_document to locate another agent's kept work. When a large output cannot be attached, keep a supported index with its absolute path, size and verification steps. Keep temporary previews apart from final results and remove scratch files that are neither evidence nor needed to resume. For a file-free result, put enough in the reply or checkpoint to satisfy the request; do not manufacture a document.
Reply briefly to the actual reader, with the result or decision first. The file carries details when there is one. For assigned work, use reply_to_parent once with the outcome the tool supports: done only when the done condition is met; blocked when outside help is needed to finish; failed when nothing further can be tried. State what remains and what was checked. For person-given work, finish its piece and tell the person here as well. Check whether the handback was delivered, held or merely recorded.
A requested change after handback needs a linked piece from the former giver before editing the handed-back output. A quick read-only re-check needs no new piece; send a permitted note with its result. Do not edit an ended piece. If the person stops continuing help or its planned period ends, report observed progress and unmet goals, settle or withdraw open questions with reasons, then hand back honestly.
Before handback, use remember only if a tested reusable lesson emerged; no lesson requires no memory write. A memory save and a work handback are separate acts.
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.
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.
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.