technical-design-review
Skill220 starsChanged 8 days agoMITView on GitHub
只读审验当前冻结设计的覆盖、契约、依据和失败恢复,返回可定位发现;不代作者修订或声称独立性。
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- capability-evaluationSkill
- code-implementationSkill
- code-reviewSkill
- conclusion-challengeSkill
- delivery-planningSkill
- docker-build-isolationSkill
- document-maintenanceSkill
- document-reviewSkill
- evidence-collectionSkill
- evidence-diagnosisSkill
- java-build-isolationSkill
- java-spring-checkSkill
- module-planningSkill
- principle-reviewSkill
- requirement-clarificationSkill
- semantic-reviewSkill
- sql-reviewSkill
- task-executionSkill
- technical-designSkill
- verificationSkill
- workspace-isolationSkill
The file
Files
目的:将冻结候选和风险适配成有边界的专业审验回执。
适用于:需求、候选与作者来源明确的专业设计审验。
技术方案专业复核
输入与方法来源
接收责任 Agent 给出的当前目标、来源/候选、读写集、预算、验收及恢复点。方法单源:
- design-inputs
- design-review
适配步骤
- 消费输入原子核当前候选、需求、作者来源、允许读集和真实上下文;核工具提供的哈希也不能代语义判断。
- 消费复核原子按风险检查当前来源、契约、保持项、异常与恢复,主动找反例;抽查列盲区,必要阻断未闭不签就绪。
- 用复核记录模板记录候选、发现 ID、原始证据、影响、关闭标准和真实执行方式。
- 返回新候选上的失效项复核;不改被审正文、不自行认领作者整改为关闭,不自动调用外部角色。
输出与边界
返回当前候选、方法覆盖、来源/假设、实际检查与未验、阻塞及下一责任。文档保存沿现有文档维护职责;Skill 不自行选择或启动上层流程。角色负责结论、授权和交接,工具不签语义或业务通过。
返回:Skills。
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.

