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

How does this skill improve team collaboration?

By documenting the 'why' behind decisions, it provides a historical record that helps new team members understand the system's evolution and prevents repetitive debates over previous choices.

What does Ecosystem E(t) mean in this skill?

E(t) represents the specific environment and constraints existing at the time of the decision, such as current team skills, infrastructure limitations, and regulatory requirements.

When should I use the design skill to create an ADR?

Use it for high-impact decisions like choosing cloud providers, programming languages, databases, authentication methods, or API styles.

Architecture Decision Designer

Name: Architecture Decision Designer
Author: foolishimp

byfoolishimp

Aprendizaje y Documentación

Generates comprehensive Architecture Decision Records (ADRs) that map technical choices to specific ecosystem constraints.

Acerca de

This skill streamlines the architectural documentation process by generating ADRs that move beyond simple choice-logging. It focuses on the reasoning behind decisions by explicitly acknowledging the 'Ecosystem E(t)'—including team capabilities, existing infrastructure, compliance requirements, and performance SLAs. By documenting decisions in the 'Given E(t), we chose X' format, it ensures that all strategic technical choices are anchored in reality, facilitating smoother onboarding, clear downstream constraints for developers, and preventing the re-litigation of past architectural choices.

Características Principales

Defines downstream constraints for implementation, runtime, and testing stages
Maintains sequential numbering and logical categorization for architectural history
Generates structured ADRs using the 'Given E(t), we chose X' pattern
Tracks decision status including Accepted, Rejected, Superseded, and Deprecated
Maps decisions to team capabilities, infrastructure, and compliance constraints
0 GitHub stars

Casos de Uso

Justifying framework choices based on current team expertise and project timelines
Documenting the rationale for selecting a specific cloud provider or database
Recording security architecture decisions to ensure alignment with compliance standards like PCI-DSS

Acerca de

Características Principales

Defines downstream constraints for implementation, runtime, and testing stages
Maintains sequential numbering and logical categorization for architectural history
Generates structured ADRs using the 'Given E(t), we chose X' pattern
Tracks decision status including Accepted, Rejected, Superseded, and Deprecated
Maps decisions to team capabilities, infrastructure, and compliance constraints
0 GitHub stars

Casos de Uso

Justifying framework choices based on current team expertise and project timelines
Documenting the rationale for selecting a specific cloud provider or database
Recording security architecture decisions to ensure alignment with compliance standards like PCI-DSS