adr-writer
Skill0 starsChanged 5 months agoMITView on GitHub
Draft an Architecture Decision Record (ADR) — context, decision drivers, options considered with trade-offs, the decision, and its consequences. Use when capturing a significant or hard-to-reverse technical decision, or when the user says "write an ADR", "document this decision", or "why did we choose X over Y".
12 other projects use a version of this.
Adopted by
Most recently taken up by
- Mathews-Tom/armorytheir own version, first seen Nov 1, 2026
- llopresto87/Cypresstheir own version, first seen Oct 14, 2026
- mikulgohil/claude-skillstheir own version, first seen Oct 13, 2026
- GabrielHenriqueCA/cortex-aitheir own version, first seen Oct 11, 2026
- govctl-org/govctltheir own version, first seen Oct 9, 2026
- applypack/applypacktheir own version, first seen Aug 27, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- Mathews-Tom/armory★ 340same name
- govctl-org/govctl★ 276same name
- llopresto87/Cypress★ 119same name
- applypack/applypack★ 30same name
- 45ck/software-architecture-skills★ 16same name
- Ecoa-PUC-Rio/GAIDE★ 8same name
- jcarlos78/GAIDE★ 8same name
- brpaz/agent-skills★ 1same name
- GabrielHenriqueCA/cortex-ai★ 1same name
- kuju63/skills★ 0same name
2 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 repository12 other files it gives its agents.
- architecture-reviewSkill
- gcp-architectureSkill
- incident-postmortemSkill
- interview-modeSkill
- leadership-lensSkill
- learning-coachSkill
- llm-app-architectureSkill
- mlops-pipeline-reviewSkill
- ml-system-designSkill
- observability-reviewSkill
- principal-code-reviewSkill
- rag-system-designSkill
The file
Files
Architecture Decision Record
Capture why a decision was made so future maintainers understand the context, not just the outcome. Keep it short and durable.
Template
# ADR-NNN: <short title>
## Status
Proposed | Accepted | Superseded by ADR-XXX
## Context
The forces at play: requirements, constraints, scale, deadlines, team skills.
What problem are we solving and why now?
## Decision Drivers
- <driver 1, e.g. must scale to 100x>
- <driver 2, e.g. team has no Kubernetes experience>
## Options Considered
### Option A — <name>
- Pros / Cons / Cost / Risk
### Option B — <name>
- Pros / Cons / Cost / Risk
## Decision
We chose <option> because <reasoning tied to drivers>.
## Consequences
- Positive: ...
- Negative / accepted trade-offs: ...
- Follow-ups / what this commits us to: ...Guidance
- Record the options you rejected and why — that's the valuable part
- Be honest about trade-offs accepted; no decision is free
- One decision per ADR; keep it immutable, supersede rather than edit
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.