architecture-decision-record
Skill11 starsChanged 27 days agoMITView on GitHub
已有具体技术决策，需要判断是否记录 ADR，或创建、更新、替代 ADR 时使用。
13 other projects use a version of this.
Adopted by
Most recently taken up by
- vinayagrw/claude-skillstheir own version, first seen Nov 1, 2026
- Future-CX/AI-Architecture-Toolkittheir own version, first seen Nov 1, 2026
- Amazon-Quick/Amazon-Quick-official-catalogtheir own version, first seen Oct 28, 2026
- PL-Coding-GmbH/Skillstheir own version, first seen Oct 25, 2026
- fattain-naime/engineering-docstheir own version, first seen Oct 24, 2026
- kesslernity/awesome-mistral-vibe-skillstheir own version, first seen Oct 20, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Amazon-Quick/Amazon-Quick-official-catalog★ 50same name
- PL-Coding-GmbH/Skills★ 18same name
- kesslernity/awesome-copilot-agent-skills★ 16same name
- z-Zihan/Evir★ 11same name
- Future-CX/AI-Architecture-Toolkit★ 8same name
- fattain-naime/engineering-docs★ 6same name
- affectionatec/agentic-engineering★ 5same name
- dss-time/repo-doctor-skills★ 1same name
- FullFran/Agent-skills-POC★ 1same name
- kesslernity/awesome-mistral-vibe-skills★ 1same name
3 more not listed
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 repository20 other files it gives its agents.
- absorb-skillSkill
- agent-healthSkill
- benchmark-checklistSkill
- brainstormingSkill
- codecov-coverageSkill
- frontend-design-reviewSkill
- gh-stackSkill
- linux-performance-analysisSkill
- loop-on-ciSkill
- pull-requestSkill
- requesting-code-reviewSkill
- runtime-verificationSkill
- shared-memorySkill
- show-meSkill
- simplifySkill
- systematic-debuggingSkill
- technical-writingSkill
- test-scenariosSkill
- writing-plansSkill
- x-tweet-fetcherSkill
The file
Files
架构决策记录
记录已经有足够上下文的决策，不替代前期架构探索。
是否值得记录
满足以下任意两项时，默认建议写 ADR：
- 有多个认真考虑过的备选方案
- 接受了真实且非平凡的成本
- 决策不容易回滚或会约束未来设计
- 只看代码无法理解为什么没有选择另一个方案
单点 bugfix、机械迁移、命名样式调整、沿用既有约定，或尚未形成选择时不写 ADR。理由较轻时放进 PR 正文、设计文档或代码注释。
评估模式
结论：建议写 ADR / 不建议写 ADR
满足标准：<编号>
依据：<真实备选、约束和代价>
建议标题：<如适用>创建流程
- 收集决策背景、驱动因素、真实备选、最终选择、正负影响及 issue/PR/代码证据。
- 检查仓库现有 ADR 目录和格式；有现行约定时优先沿用。
- 默认路径为
docs/adr/NNNN-<slug>.md，编号取现有最大值加一，slug 使用小写短横线。 - 使用 ADR 模板，删除不适用的占位内容，不虚构备选或验证结果。
- 检查新决策是否明确替代旧 ADR。范围只是补充或局部扩展时不要标记替代。
- 创建后复读事实、状态、链接、负面影响和替代关系。
更新与替代
已接受 ADR 应保留历史。只有新决策明确反转或替换旧选择时，才把旧 ADR 状态更新为：
status: 被 ADR-NNNN 替代标题相似或治理范围重叠只算候选，不足以自动替代。证据模糊时报告候选并保持旧文件不变。
写作约束
- 一个 ADR 只记录一个决策
- 只写真实考虑过的方案
负面影响必须写明接受的成本- 语言保持事实性，不写宣传口吻
- 信息缺失时明确记录 gap
输出
ADR: <path / 未创建>
标题：<标题>
状态：<状态>
替代记录：无 / ADR-NNNN
已知缺口：<缺口>
验证：<检查>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.