adr SKILL.md skillA
adr from sd0xdev/sd0x-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sd0xdev/sd0x-harness/adr@git:20260811.d9a8bcaPins git:20260811.d9a8bca in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sd0xdev/sd0x-harness
- Path
skills/adr/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260811.d9a8bca, committed Aug 11, 2026
- First version recorded
- Aug 7, 2026
- Size
- 19,388 bytes
- Repository stars
- 194
- License
- MIT
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature>/adr-<NNN>-<title>.md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural approach was chosen, documenting a decision so it doesn't get re-litigated, marking a prior decision as superseded. Not for: feature-level technical design…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# ADR — Architecture Decision Record ## Trigger - Keywords: ADR, architecture decision record, decision record, record a decision, why did we choose, 架構決策, 決策紀錄 ## When NOT to Use | Scenario | Alternative | |----------|------------| | Feature-wide technical design (components, data flow) | `/tech-spec` | | Task progress / acceptance-criteria tracking | `/create-request` | | Bulk backfill of decisions already made in the past | Separate request — this skill writes one ADR per invocation, not a batch | ## Workflow ``` Phase 1: Resolve feature → shared feature-context resolution Phase 2: Compute number → scan root + archived/, numeric max + 1, zero-pad to 3 digits Phase 3: Gather content → Context / Decision / Status / Consequences / Alternatives Phase 4: Write ADR → fill references/template.md, write to docs/features/<key>/ Phase 4b: Superseded link → (only if this ADR supersedes an existing one) edit both files Phase 5: Report → path written, number assigned, links updated ``` ### Phase 1: Resolve Feature Reuse the shared cascade — do not re-derive it here: `@skills/create-request/references/feature-context-resolution.md` — the single copy since …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/adr@sha256:4bd76188f77527c6The line at the top of this page pins the label git:20260811.d9a8bca, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_o57toucsdlylt36r)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 7, 2026 and Aug 11, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.d9a8bca latest | 2026-08-11 | d9a8bca | 19,388 B | A | view · diff |
| git:20260807.187b0aa | 2026-08-07 | 187b0aa | 17,460 B | A | view |
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 (19388 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
sd0xdev/sd0x-harness · 194 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o57toucsdlylt36r GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/adr GET https://markdownregistry.com/api/v1/blob/4bd76188f77527c61d5f1d23b1fae9fb0639cf3a8021e804eb6e1ee18884b33f
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from sd0xdev/sd0x-harness
Every file in sd0xdev/sd0x-harness