adr-writing skillA
adr-writing is agent-read markdown (skill) from khaledsaeed18/dotclaude: Write Architecture Decision Records that a future engineer can act on: a numbered, immutable record with the context that forced the decision, the options weighed with real trade-offs, the decision in one sentence, and the consequences including what becomes harder. Covers when a decision deserves an ADR, how to supersede one, and how to keep an index. Use when a design choice has cross-cutting or long-lived effects, when reviewers keep asking why, or when onboarding depends on decisions nobody .
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
An ADR records a decision at the moment it was made, with the reasoning that was available then. It is not documentation of the system (that changes) and not a design document (that precedes the decision). Its reader is an engineer two years from now asking "why is it like this, and can I change it?" ## When to write one Write an ADR when a decision is: - **hard to reverse** (a database, a framework, a public API shape, a data format), or - **cross-cutting** (affects how most code is written: error handling convention, module boundaries, auth model), or - **surprising** (a reader would assume the other option), or - **contested** (people disagreed, and the losing option will come up again). Do not write one for choices that are local, obvious, or cheaply reversible; a comment or a commit message serves those. A repository with 200 ADRs has stopped recording decisions and started recording activity. ## Format ```markdown # 0007. Use PostgreSQL row-level security for tenant isolation Date: 2026-09-21 Status: accepted Supersedes: 0003 Deciders: (names or roles) ## Context …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/adr-writing@git:20260921.b628018mdr add khaledsaeed18/dotclaude/adr-writing@sha256:79a199ac7ffed5b9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_g4gw6m5s54gvmybn)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4349 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g4gw6m5s54gvmybn GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/adr-writing GET https://markdownregistry.com/api/v1/blob/79a199ac7ffed5b9cf6bcc0da88cba16553889112bd5b6726b9ac4fc0386c90a
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.