Agent skill · product strategy · rmyndharis
architecture-decision-records
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.
Why this skill is useful
Codifies a standard procedure for documenting architectural decisions that the AI could infer but doesn't have to guess.
What it needs
About 7k tokens when loaded. Last updated 2026-08-02. 1,255 stars on the source repository.
What this skill does
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 1. Capture the decision context, constraints, and drivers. 2. Document considered options with tradeoffs. 3. Record the decision, rationale, and consequences. 4. Link related ADRs and update status over time. Core Concepts 1. What is an ADR? An Architecture Decision Record captures: Context: Why we needed to make a decision Decision: What we decided Consequences: What happens as a result 2. When to Write an ADR Write ADR Skip ADR ----------- ---------- New framework adoption Minor version upgrades Database technology choice Bug fixes API design patterns Implementation details Security architecture Routine maintenance Integration patterns Configuration changes 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rmyndharis/architecture-decision-records