architecture-decision-records SKILL.md skillA

architecture-decision-records from ronnasayd/aipp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add ronnasayd/aipp/architecture-decision-records@git:20261027.315f0f5

Pins git:20261027.315f0f5 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
ronnasayd/aipp
Path
skills/everything-claude-code/architecture-decision-records/SKILL.md
Versions recorded
2
Latest version
git:20261027.315f0f5, committed Oct 27, 2026
First version recorded
Jul 11, 2026
Size
7,182 bytes
Repository stars
3
License
none declared

Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.

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

# Architecture Decision Records

Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.

## When to Activate

- User explicitly says "let's record this decision" or "ADR this"
- User chooses between significant alternatives (framework, library, pattern, database, API design)
- User says "we decided to..." or "the reason we're doing X instead of Y is..."
- User asks "why did we choose X?" (read existing ADRs)
- During planning phases when architectural trade-offs are discussed

## ADR Format

Use the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development:

```markdown
# ADR-NNNN: [Decision Title]

**Date**: YYYY-MM-DD
**Status**: proposed | accepted | deprecated | superseded by ADR-NNNN
**Deciders**: [who was involved]

## Context

What is the issue that we're seeing that is motivating this decision or change?

[2-5 sentences describing the situation, constraints, and forces at play]

## Decision

What is the change that we're proposing and/or doing?
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dmlge3xpr2osxszn/263b20e81801aa5fa7e75eaec6c38345c0ac028ca0edbd67b1b9071c5fcbe11f.json

Then /plugin install architecture-decision-records@markdownregistry-dmlge3xpr2osxszn in Claude Code. It installs git:20261027.315f0f5, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add ronnasayd/aipp/architecture-decision-records@sha256:263b20e81801aa5f

The line at the top of this page pins the label git:20261027.315f0f5, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_dmlge3xpr2osxszn.svg)](https://markdownregistry.com/a/art_dmlge3xpr2osxszn)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in ronnasayd/aipp/architecture-decision-records since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of architecture-decision-records from somewhere else? Ask it: where did my architecture-decision-records come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Jul 11, 2026 and Oct 27, 2026, about one every 108 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261027.315f0f5 latest2026-10-27 315f0f5 7,182 BA view · diff
git:20260711.2886deb2026-07-11 2886deb 7,131 BA view

Copies

Copies in other repositories

2 files in 2 other repositories hold the exact bytes of one of this file's versions, each committed after this file had them: every one holds an older version.

A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (7182 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

GitHub

ronnasayd/aipp · 3 stars · license none declared · pushed 2026-11-18 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_dmlge3xpr2osxszn
GET https://markdownregistry.com/api/v1/resolve?ref=ronnasayd/aipp/architecture-decision-records
GET https://markdownregistry.com/api/v1/blob/263b20e81801aa5fa7e75eaec6c38345c0ac028ca0edbd67b1b9071c5fcbe11f

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 ronnasayd/aipp

AGENTS.md AGENTS.md file
ronnasayd/aipp · AGENTS.md
git:20261105.0bfe3dc · audit A · 3 stars
CLAUDE.md CLAUDE.md file
ronnasayd/aipp · CLAUDE.md
git:20260919.ef9a503 · audit A · 3 stars
AGENTS.md@claude/dev-mods/tool-history AGENTS.md file
ronnasayd/aipp · claude/dev-mods/tool-history/AGENTS.md
git:20261105.4ba4217 · audit A · 3 stars
discovery-process SKILL.md skill
ronnasayd/aipp · skills/Product-Manager-Skills/discovery-process/SKILL.md · Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path…
git:20261109.95e8e67 · audit A · 3 stars
prd-development SKILL.md skill
ronnasayd/aipp · skills/Product-Manager-Skills/prd-development/SKILL.md · Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes…
git:20261109.95e8e67 · audit A · 3 stars
user-story-mapping SKILL.md skill
ronnasayd/aipp · skills/Product-Manager-Skills/user-story-mapping/SKILL.md · Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow…
git:20261109.95e8e67 · audit A · 3 stars
user-story-splitting SKILL.md skill
ronnasayd/aipp · skills/Product-Manager-Skills/user-story-splitting/SKILL.md · Break a large story or epic into smaller deliverable stories using proven split patterns. Use when backlog items are…
git:20261109.95e8e67 · audit A · 3 stars
user-story SKILL.md skill
ronnasayd/aipp · skills/Product-Manager-Skills/user-story/SKILL.md · Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into…
git:20261109.95e8e67 · audit A · 3 stars
skill-inspector SKILL.md skill
ronnasayd/aipp · skills/SkillSpector/skill-inspector/SKILL.md · Review AI agent skills before installation using NVIDIA SkillSpector and source-aware semantic review. Use when asked…
git:20261027.315f0f5 · audit A · 3 stars
adversarial-dev SKILL.md skill
ronnasayd/aipp · skills/adversarial-dev/SKILL.md · Orchestrates a code task through two separate agents in an adversarial loop — an executor that implements and a strict…
v1.0.0 · audit A · 3 stars
agent-creator SKILL.md skill
ronnasayd/aipp · skills/agent-creator/SKILL.md · Create new specialist agents, modify and improve existing agents, and validate agent behavior. Use when users want to…
v1.0.0 · audit A · 3 stars
skill-judge SKILL.md skill
ronnasayd/aipp · skills/agent-toolkit/skill-judge/SKILL.md · Evaluate Agent Skill design quality against official specifications and best practices. Use when reviewing, auditing…
git:20260926.0cb2534 · audit A · 3 stars

Every file in ronnasayd/aipp

Other files named architecture-decision-records

architecture-decision-records SKILL.md skill
affaan-m/ecc · docs/ja-JP/skills/architecture-decision-records/SKILL.md · コーディングセッション中にアーキテクチャ決定を構造化ADRとして記録し、自動的に決定の瞬間を検出し、コンテキスト、検討された代替案、根拠を記録します。今後の開発者がコードベースの形成理由を理解するためのADRログを維持します。
git:20260517.ec9ace9 · audit A · 305,967 stars
architecture-decision-records SKILL.md skill
sickn33/agentic-awesome-skills · plugins/agentic-awesome-skills-claude/skills/architecture-decision-records/SKILL.md · Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the…
git:20260729.2d74b64 · audit A · 49,786 stars
architecture-decision-records SKILL.md skill
wshobson/agents · plugins/documentation-generation/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
git:20261017.0874a27 · audit A · 42,645 stars
architecture-decision-records SKILL.md skill
dicklesworthstone/pi_agent_rust · tests/ext_conformance/artifacts/agents-wshobson/documentation-generation/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
git:20260205.788be98 · audit A · 1,995 stars
architecture-decision-records SKILL.md skill
hashgraph-online/awesome-codex-plugins · plugins/Colin4k1024/tsp/skills/architecture-decision-records/SKILL.md · Capture architectural decisions made during Claude Code sessions as structured ADRs. Auto-detects decision moments…
git:20260512.6523792 · audit A · 1,584 stars
architecture-decision-records SKILL.md skill
francostino/opencode-skills-collection · bundled-skills/architecture-decision-records/SKILL.md · Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the…
git:20260730.90257ed · audit A · 92 stars
architecture-decision-records SKILL.md skill
rudycity/superagent · .agents/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
git:20260626.019dba9 · audit A · 71 stars
architecture-decision-records SKILL.md skill
aicodedecode/awesome-muse-skills · skills-imported/architecture-decision-records/SKILL.md · Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the…
git:20260927.806f3e1 · audit A · 62 stars

Browse by kind, by grade A, or by owner.