architectural-decision-records SKILL.md skillA
architectural-decision-records from intent-driven-dev/intent-driven-template is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add intent-driven-dev/intent-driven-template/architectural-decision-records@git:20260510.a8b8231Pins git:20260510.a8b8231 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- intent-driven-dev/intent-driven-template
- Path
.agents/skills/architectural-decision-records/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260510.a8b8231, committed May 10, 2026
- Size
- 4,077 bytes
- Repository stars
- 188
- License
- MIT
Use when documenting, drafting, reviewing, or updating architectural decisions, ADRs, decision logs, tradeoffs, rationale, consequences, alternatives, or architecture decision history.
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
# Architectural Decision Records ## Overview An Architectural Decision Record captures one architecturally significant decision, its rationale, tradeoffs, and consequences. Optimize for future readers reconstructing decision history. ## When to Use Use when creating, updating, reviewing, or explaining an ADR, architecture decision, decision log, tradeoff analysis, rationale, consequences, alternatives, or status. Do not use ADRs for transient implementation details, meeting notes, or insignificant decisions. If significance is unclear, ask what future maintainers will need to know. ## Workflow 1. Identify the single decision. Split multiple decisions into multiple ADRs. 2. Check `preferences.md` for `preferred-style`. 3. If `preferred-style: unset`, ask the user which style to use, then record it in `preferences.md` before drafting. 4. Use the matching file under `templates/`. 5. Capture known facts only: context, requirements, constraints, options, rationale, decision makers, consequences. 6. If facts are missing, mark them as `Unknown` or ask a focused question; do not invent context, options, or quality attributes. …
Read the whole file at its exact version.
How to install
mdr add intent-driven-dev/intent-driven-template/architectural-decision-records@sha256:7b1cae1dc52e19c2The line at the top of this page pins the label git:20260510.a8b8231, 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_7forjiyrcu3kcdx5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 10, 2026.
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 (4077 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
intent-driven-dev/intent-driven-template · 188 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7forjiyrcu3kcdx5 GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/architectural-decision-records GET https://markdownregistry.com/api/v1/blob/7b1cae1dc52e19c24957e98175c8172447a7afde10bef9fd75141dd1325ce69f
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 intent-driven-dev/intent-driven-template
Every file in intent-driven-dev/intent-driven-template