When should I use this Claude Code skill?

Use it whenever you make a strategic choice that is difficult to change later, such as selecting a database, choosing between microservices and monoliths, or picking an authentication strategy.

Can this skill help with compliance?

Yes, by documenting the rationale behind security and data decisions, it provides an audit trail that helps satisfy compliance requirements like PCI-DSS and HIPAA.

What is an ADR in software development?

An Architecture Decision Record (ADR) is a short text file that captures a significant architectural decision, the context in which it was made, and the consequences it has for the project's future.

Why does the skill document rejected alternatives?

Documenting rejected options prevents future 're-litigation' of the same decision by explaining exactly why those alternatives were deemed unsuitable at the time the decision was made.

How does the create-adrs skill handle ecosystem constraints?

The skill uses the 'E(t)' framework to ensure every decision acknowledges existing limitations—such as team experience, infrastructure, and compliance—rather than choosing solutions in a vacuum.

Architecture Decision Record (ADR) Architect

Name: Architecture Decision Record (ADR) Architect
Author: foolishimp

byfoolishimp

学習とドキュメンテーション

Document strategic technical decisions by mapping chosen solutions against specific ecosystem constraints and architectural trade-offs.

概要

This skill automates the creation of high-quality Architecture Decision Records (ADRs) that prioritize the 'why' behind technical choices. Unlike standard templates, it focuses on Ecosystem E(t) constraints—such as team expertise, existing infrastructure, and compliance requirements—to ensure decisions are grounded in practical reality. It generates structured documentation that covers rejected alternatives, downstream constraints, and long-term consequences, making it an essential tool for maintaining architectural integrity, preventing re-litigation of past choices, and streamlining developer onboarding.

主な機能

Comprehensive ecosystem constraint analysis including Team, Infra, and Compliance
Detailed documentation of rejected alternatives and specific technical trade-offs
0 GitHub stars
Context-aware decision logging using the 'Given E(t), we chose X' formula
Automatic derivation of downstream implementation and testing constraints
Standardized sequential numbering and categorization for organized architectural logs

ユースケース

Justifying specific technology selections based on current team skill sets and hiring constraints
Choosing between cloud providers, databases, or frameworks during project discovery
Documenting security-critical architectural decisions to satisfy PCI-DSS or SOC2 compliance audits

概要

主な機能

Comprehensive ecosystem constraint analysis including Team, Infra, and Compliance
Detailed documentation of rejected alternatives and specific technical trade-offs
0 GitHub stars
Context-aware decision logging using the 'Given E(t), we chose X' formula
Automatic derivation of downstream implementation and testing constraints
Standardized sequential numbering and categorization for organized architectural logs

ユースケース

Justifying specific technology selections based on current team skill sets and hiring constraints
Choosing between cloud providers, databases, or frameworks during project discovery
Documenting security-critical architectural decisions to satisfy PCI-DSS or SOC2 compliance audits