architecture-decision-records — community architecture-decision-records, claude-code-onboarding, community, ide skills

v1.0.0

About this Skill

Ideal for Technical Agents requiring structured decision-making and knowledge management, particularly those utilizing Java 21/Spring Boot WebFlux, Angular, Flutter, PostgreSQL, and Firebase. This skill should be used when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes. It provides ADR templates and best practices.

kumaran-is kumaran-is
[3]
[2]
Updated: 2/24/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
51
Canonical Locale
en
Detected Body Locale
en

Ideal for Technical Agents requiring structured decision-making and knowledge management, particularly those utilizing Java 21/Spring Boot WebFlux, Angular, Flutter, PostgreSQL, and Firebase. This skill should be used when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes. It provides ADR templates and best practices.

Core Value

Empowers agents to capture and document significant technical decisions using standardized Architecture Decision Records (ADRs) formats, facilitating informed decision-making and collaboration across teams, with integrations supporting API design patterns and security architecture.

Ideal Agent Persona

Ideal for Technical Agents requiring structured decision-making and knowledge management, particularly those utilizing Java 21/Spring Boot WebFlux, Angular, Flutter, PostgreSQL, and Firebase.

Capabilities Granted for architecture-decision-records

Documenting new framework adoptions
Recording database technology choices
Standardizing API design patterns
Capturing security architecture decisions
Maintaining a knowledge base for technical decisions

! Prerequisites & Limits

  • Requires team onboarding and configuration
  • Limited to significant technical decisions, not suitable for minor version upgrades or routine maintenance
  • Dependent on agent's ability to identify and document key technical decisions

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is architecture-decision-records?

Ideal for Technical Agents requiring structured decision-making and knowledge management, particularly those utilizing Java 21/Spring Boot WebFlux, Angular, Flutter, PostgreSQL, and Firebase. This skill should be used when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes. It provides ADR templates and best practices.

How do I install architecture-decision-records?

Run the command: npx killer-skills add kumaran-is/claude-code-onboarding/architecture-decision-records. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for architecture-decision-records?

Key use cases include: Documenting new framework adoptions, Recording database technology choices, Standardizing API design patterns, Capturing security architecture decisions, Maintaining a knowledge base for technical decisions.

Which IDEs are compatible with architecture-decision-records?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for architecture-decision-records?

Requires team onboarding and configuration. Limited to significant technical decisions, not suitable for minor version upgrades or routine maintenance. Dependent on agent's ability to identify and document key technical decisions.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add kumaran-is/claude-code-onboarding/architecture-decision-records. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use architecture-decision-records immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

architecture-decision-records

Install architecture-decision-records, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before...

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Architecture Decision Records

Capture the context and rationale behind significant technical decisions using structured ADR formats.

When to Use This Skill

Write ADRSkip ADR
New framework adoptionMinor version upgrades
Database technology choiceBug fixes
API design patternsImplementation details
Security architectureRoutine maintenance
Integration patternsConfiguration changes

Quick Start

  1. Copy the template: cp docs/adr/template.md docs/adr/NNNN-your-title.md
  2. Fill in: Context, Decision Drivers, Options, Decision, Consequences
  3. PR for review (2+ senior engineers)
  4. Update docs/adr/README.md index after merge

Core Concepts

An Architecture Decision Record captures:

  • Context: Why we needed to make a decision
  • Decision: What we decided
  • Consequences: What happens as a result

ADR Lifecycle

Proposed --> Accepted --> Deprecated --> Superseded
                |
             Rejected

Read reference/adr-lifecycle.md for status transitions, deprecation patterns, and review checklists.

Process

1. Choose a Template

Pick the format that fits the decision's complexity:

Decision ComplexityTemplate
Simple tech selectionY-Statement (one paragraph)
Medium decisionLightweight ADR (0.5-1 page)
Significant architecture changeStandard MADR (1-2 pages)
Retiring a decisionDeprecation ADR
Major cross-team proposalRFC Style (2-4 pages)

Read reference/adr-templates.md for all template formats ready to copy-paste.

2. Write the ADR

  • Start with context -- explain the problem before the solution
  • List 2-3 real alternatives with honest pros/cons
  • State the decision clearly
  • Document both positive and negative consequences with specifics

3. Review and Approve

  • Submit as PR with 2+ senior engineer reviewers
  • Consult affected teams
  • Assess security, cost, and reversibility implications

4. Maintain

  • Update ADR index after acceptance
  • Create implementation tickets
  • Never edit accepted ADRs -- write new ones to supersede

Read reference/adr-examples.md for complete worked examples (PostgreSQL selection, TypeScript adoption, MongoDB deprecation, event sourcing RFC).

Minimal Template (Copy-Paste Starter)

markdown
1# ADR-NNNN: [Title] 2 3## Status 4Proposed | Accepted | Deprecated | Superseded by ADR-XXXX 5 6## Context 7[Why do we need to decide this? What's the problem?] 8 9## Decision 10We will [decision]. 11 12## Consequences 13- **Good**: [benefits] 14- **Bad**: [drawbacks] 15- **Mitigations**: [how we'll address the bad]

Common Mistakes

MistakeFix
Writing ADR after implementationWrite during design phase
Listing only one optionAlways include 2-3 real alternatives
Vague consequencesBe specific: "Adds ~200ms latency to checkout"
Editing accepted ADRsWrite new ADR that supersedes
No decision driversList explicit criteria with priorities
Missing rejected ADRsDocument rejected options too

Directory Structure

docs/adr/
  README.md           # Index of all ADRs
  template.md         # Team's ADR template
  0001-use-postgresql.md
  0002-caching-strategy.md

Reference Files

FileContents
reference/adr-templates.mdAll formats: MADR, lightweight, Y-statement, deprecation, RFC
reference/adr-examples.mdComplete worked examples for each format
reference/adr-lifecycle.mdStatus transitions, review checklists, automation with adr-tools

Resources

Error Handling

Conflicting ADRs: When a new decision contradicts an existing ADR, create a superseding ADR that explicitly references and deprecates the old one.

Missing context: If the decision rationale is unclear or incomplete, flag it and request clarification before recording.

Related Skills

Looking for an alternative to architecture-decision-records or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer