adr
Skill1 starsChanged 2 months agoMITView on GitHub
トレードオフを伴う決定をしたとき、「この決定をADRに残して」と言われたときに必ず使う。
97 other projects use a version of this.
Adopted by
Most recently taken up by
- lyeyixian/skillstheir own version, first seen Nov 16, 2026
- raphaeldiscky/skillstheir own version, first seen Nov 16, 2026
- zazencodes/skillstheir own version, first seen Nov 15, 2026
- timursafiullin/aodtheir own version, first seen Nov 15, 2026
- srinator22/agent-kerneltheir own version, first seen Nov 15, 2026
- GravionLabs/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use fdr, runbook and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thiagofgfSkillfdr
Use when creating, changing, reviewing, retiring, auditing, or backfilling implemented user-visible feature behavior, permissions, feature-specific rationale, tradeoffs, or relationships to architectural decisions.
Also in 3 projects that use this
AnthropicSkillrunbook
Create or update an operational runbook for a recurring task or procedure. Use when documenting a task that on-call or ops needs to run repeatably, turning tribal knowledge into exact step-by-step commands, adding troubleshooting and rollback steps to an existing procedure, or writing escalation paths for when things go wrong.
Also in 5 projects that use this
drewdrewthisSkillsweep
Search for similar patterns, anti-patterns, or issues elsewhere in the codebase after a fix or feature. Use after implementing a fix to catch the same bug in other places, or proactively to audit for a known pattern.
Also in 4 projects that use this
vndeeSkillproduct-spec
Use when starting a new feature, product, or project — before any architecture or code, to define what to build and why
Also in 3 projects that use this
montymiSkilltech-spec
Parse and review Technical Specification documents for completeness, consistency, and implementation readiness
Also in 3 projects that use this
OpenAISkillthreat-model
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Also in 6 projects that use this
Other versions97 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 97
- CrowdDotDev/crowd.dev★ 3.4ksame name
- chattocorp/chatto★ 3ksame name
- Cosmian/kms★ 378same name
- linuxfoundation/insights★ 292same name
- rvdbreemen/OTGW-firmware★ 217same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- irahardianto/awesome-agv★ 157same name
- jellydn/my-ai-tools★ 129same name
- EmeaAppGbb/spec2cloud★ 100same name
87 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 repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-checkSkill
- brainstormSkill
- branch-namingSkill
- codex-delegateSkill
- config-explainSkill
- config-setSkill
- cross-reviewSkill
- design-interviewSkill
- diagnosing-bugsSkill
- fix-ciSkill
- handoffSkill
- leakage-checkSkill
- literature-reviewSkill
- mlflow-logSkill
- multi-seedSkill
- mutation-testSkill
- paper-writingSkill
- pre-mortemSkill
- property-testSkill
- python-standardsSkill
- refactor-scoutSkill
- regression-suiteSkill
- retrospectiveSkill
- security-reviewSkill
- spec-checklistSkill
- tddSkill
The file
Files
ADR記録
設計上の重要な決定を、後から理由を追える形で記録する。
いつ書くか
- 複数の選択肢があり、どれか1つを選んだとき(トレードオフを伴う決定)
- 一度決めたら後から変更しづらい決定(データ形式、アーキテクチャ、外部依存の選定など)
- 些細な決定(変数名、フォーマットの好みなど)には書かない
進め方
- 作業スコープ配下に docs/adr/ が無ければ作成する。
- 既存のADRファイルを確認し、連番(0001, 0002, ...)の次の番号を決める。
docs/adr/NNNN-<短いタイトル>.md を以下の形式で作成する。
# NNNN. <タイトル> 日付: YYYY-MM-DD 状態: 提案中 / 承認 / 置き換え済み ## 背景 ## 検討した選択肢 ## 決定 ## 理由 ## トレードオフ- 各セクションを埋める。簡潔に、しかし将来読んだ人が納得できる粒度で書く。
注意
- 決定を覆す場合は、古いADRを削除せず「このADRはNNNNにより置き換えられた」 と追記し、新しいADRを追加する(履歴を残す)。
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.

