closeout-report-drafting
Skill3 starsChanged 8 days agoApache-2.0View on GitHub
当活干完要写收口报告或回执、单做完准备交板、要向总监或拍板人汇报这单做成了什么、拿不准该写报告还是交接件、收口时上下文太大,或报告被退回要重写时使用。凡遇到这些情况,先读本 skill 再动手:按固定四块骨架交子代理起草,本体只用命令核哈希、数字与文件名,篇幅按字符量。
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-session-observabilitySkill
- context-guard-hooksSkill
- contract-and-test-infraSkill
- doc-pointer-checkSkill
- engineering-pitfalls-checklistSkill
- first-window-requirementsSkill
- frontend-integration-preflightSkill
- hive-dispatchSkill
- legacy-project-onboardingSkill
- memory-index-foldingSkill
- memory-writingSkill
- merge-and-deploySkill
- open-source-preflightSkill
- pointer-handoffSkill
- repo-scale-reportingSkill
- shared-checkout-safetySkill
- short-book-draftingSkill
- subtraction-reviewSkill
- ticket-desk-usageSkill
- top-audit-dispatchSkill
- verify-agent-claimsSkill
- window-handoff-draftingSkill
- zero-window-taskbook-draftingSkill
The file
Files
这个 skill 是干什么的(人话)
这个 skill 帮你在一件活做完时写出一份短、能逐条核对的收口报告。报告只有四块:一句结论、发生了什么、要别人接着做的事、三个收尾问题。起草交给助手,你只拿记录核数字和名字,不重写。不用它,报告容易写成流水账,数字没人核,后续也没人接。
分类
分类:单独装即可用
用前填这几个名字
- {{章程目录}}:各位章程所在的根目录,收口报告落在它下面的「<位名>/回执/」;例:
_office - {{拍板人}}:唯一有最终裁定权的人的称谓;例:设计者
- {{裁定簿路径}}:登记裁定的总账文件;例:
_office/裁定簿.md - {{收口报告字数上限}}:收口报告全文最多多少字(按字符计);例:6000
什么时候用
- 一张 0 号包干单、甲档或乙档单做完,要交回收口报告。
- 活做到头了,拿不准该写收口报告还是交接件(做完写报告,做不完写交接件)。
- 收口时本窗上下文已很大,或要读的对账表、进度件很大,得把起草交出去。
- 报告被退回,说标题不对、篇幅超限或数字对不上,要重写。
步骤
读本目录 references/closeout-steps.md 照做;要抄的骨架、「写 / 不写」表和量字符的命令在本目录 references/closeout-report-template.md。
- 判该不该写:做完才写,做不完改写交接件。
- 定谁起草:交子代理做,平台没有子代理就自己做;本体只核。
- 抄模板骨架,四个标题逐字照写。
- 逐块按模板「写 / 不写」表填。
- 收尾三问答全。
- 把不进报告的内容挪走。
- 按字符量篇幅。
- 落盘。
- 本体用命令核哈希、数字、文件名。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

