closing
Skill8 starsChanged 56 days agoMITView on GitHub
用于用户要求收尾、收工、归档复盘或整理交接时,支持正常结束和中途停下换任务接续;可由自然语言意图或显式 `$closing` 触发。单纯要求停止、暂停或反馈卡顿、方法错误时不触发。
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Sapere-IA/sdd-onboarding-kittheir own version, first seen Oct 13, 2026
- donatassimkus/claude-ai-skillstheir own version, first seen Jul 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Sapere-IA/sdd-onboarding-kit★ 19same name
- donatassimkus/claude-ai-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- enhance-promptSkill
- grill-requirementsSkill
- interface-designSkill
The file
Files
收尾 Closing
本目录是能力正文单一源:本文件保留必要判断,专项细则在下方按需分支。发现入口、旧Prompt只负责路由,不复制正文。
触发与边界
用户要求收尾、收工、归档复盘或整理交接时调用,无需固定口令;单纯停止、暂停、卡顿或方法错误反馈不触发。用户要求中途收尾时,停止原业务推进,只核已有成果、问题与接续,不借收尾继续修复或重试;收尾完成与业务目标完成分别判断。明确要求立即停止或跳过讨论时服从,并如实保留未处理项。
默认只读本入口,用当前对话及已核验、仍有效的资料完成下列检查;只补缺口或变化,不为收尾遍读历史、全量Skill、项目地图或治理索引。已获批同批动作直接沿用授权;规则变更、重要删除、外部发送和真实系统写入按现行边界判断。读取相关任务不自动授权发送、唤醒、创建任务、归档或定期检查。
若由已有复盘自动化调用,改读自动化分支,不套用交互收尾流程。
必要检查
检查适用事项后才能宣称完整收尾。读取Skill、完成交接或简短回复本身不证明五项均已完成;核查依据可来自本轮动作或已核验且仍有效的成果、记录与回执,不强制新表单或五段报告。
- 成果:盘点有证据的实际结果,对照本次范围与验收;计划、准备好、局部验证不冒充完成。
- 未完与阻碍:说明还差什么、风险、待确认或待验收条件。明显卡顿、返工、无效重试或重复确认,用已有证据初查,区分规则问题、AI漏读/未执行、表达含糊与工具/权限/材料限制;证据不足保留未知,不展开历史追查或专门复现。用户未要求停下,且原因明确、已有授权、影响小可验证时当场处理;复杂问题只初查并明确后续处置,已决定的接续不重复询问。
- 敏感与真实动作:核本轮涉及的密钥、隐私、外发、真实写入与删除风险;处置沿用当前规则,只展示问题或需用户处理的事项。
- 遗留与材料:核有价值经验、规则建议、方法工具改进、未完事项及已知待裁项。已落实的不重做;每项明确按授权落实、留待核、不保留或交接谁,并说明未完成部分,不以“以后再看”代替处置。核本轮过程材料与交接件是否仍有用途;没有候选不凑数。
- 接续与整体目标:核下一步、承接方、依赖和证据入口。只在已有线索表明共享目标、依赖或既有决定时读相关任务,区分本次收尾完成与整体交付完成;具体按接续分支处理。一次性事项结清即可说明无需接续。
按需读取
按实际缺口选择,可复用已读且未变的分支;不顺着链接把所有分支读完。
| 当前情形 | 读取 |
| 未完交接、共同目标、相关任务决定或依赖 | 接续与共同目标 |
| 仍有有价值内容需保存、裁决或确定去向;已明确处置且未变的遗留不触发 | 分流与落盘;已有同批授权不重复确认 |
| 产生或实际使用了过程材料、临时文件或交接件 | 材料清退;共享正本和业务原始资料不自动成为清理对象 |
| 已有自动化调用本协议 | 自动化复盘;沿用调用方的范围和授权 |
交付与成长
先说明实际完成及现在能用什么,再给影响验收或接续的未完项、限制和可定位证据。五项按适用情况核查,零结果静默带过;无须展示内部过程或泛问是否结束。有价值遗留已明确处置、接续已交代即可结束,不要求全部待办当场完成;未落盘、未验证、未获授权分别如实说明。
只有可复用的新反馈、方法或改进机会才低成本查证;Skill缺陷与执行未遵守、材料或环境问题分开。方法经验仅按当前用户已有授权保存到其指定的项目经验记录,补入既有方法记录的相关主题,已有案例只引用,同一发现不重复保存;未指定记录位置、明确只读或禁写时,仅在对话说明,不自动建库。实际留证、维护或提审时才按需读取所在项目的治理约定,无新价值不增检索、记录或后台任务;经验不自动升为规则,正式改进须用户批准,同批不重问。
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.

