Architecture Decision Records Agent Skill

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

4k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill architecture-decision-records

What comes with it

11 353 bytes besides the instruction

sub-skills/1-what-is-an-adr.md

sub-skills/2-when-to-write-an-adr.md

sub-skills/3-adr-lifecycle.md

sub-skills/adr-index-readmemd.md

sub-skills/after-acceptance.md

sub-skills/automation-adr-tools.md

sub-skills/before-submission.md

sub-skills/directory-structure.md

sub-skills/donts.md

sub-skills/dos.md

sub-skills/during-review.md

sub-skills/event-store.md

sub-skills/negative.md

sub-skills/option-1-postgresql.md

sub-skills/option-2-mysql.md

sub-skills/option-3-mongodb.md

sub-skills/positive.md

sub-skills/projections.md

sub-skills/risks.md

sub-skills/technology.md

sub-skills/template-1-standard-adr-madr-format.md

sub-skills/template-2-lightweight-adr.md

sub-skills/template-3-y-statement-format.md

sub-skills/template-4-adr-for-deprecation.md

sub-skills/template-5-request-for-comments-rfc-style.md

The instruction itself

33 sections, as written by the author

Architecture Decision Records

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

Use this skill when

Making significant architectural decisions
Documenting technology choices
Recording design trade-offs
Onboarding new team members
Reviewing historical decisions
Establishing decision-making processes

Do not use this skill when

You only need to document small implementation details
The change is a minor patch or routine maintenance
There is no architectural decision to capture

Instructions

Capture the decision context, constraints, and drivers.
Document considered options with tradeoffs.
Record the decision, rationale, and consequences.
Link related ADRs and update status over time.

Core Concepts

🧠 Knowledge Modules (Fractal Skills)

1. 1. What is an ADR?

2. 2. When to Write an ADR

3. 3. ADR Lifecycle

4. Template 1: Standard ADR (MADR Format)

5. Option 1: PostgreSQL

6. Option 2: MySQL

7. Option 3: MongoDB

8. Positive

9. Negative

10. Risks

11. Template 2: Lightweight ADR

12. Template 3: Y-Statement Format

13. Template 4: ADR for Deprecation

14. Positive

15. Negative

16. Template 5: Request for Comments (RFC) Style

17. Event Store

18. Projections

19. Technology

20. Directory Structure

21. ADR Index (README.md)

22. Automation (adr-tools)

23. Before Submission

24. During Review

25. After Acceptance

26. Do's

27. Don'ts

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens

Domain Name Brainstormer

by frostant

×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts

Scientific Brainstorming

by christophacham

×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens

GitHub Project Management

by ComeOnOliver

×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/architecture-decision-records from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.